Soldato
- Joined
- 3 Jun 2005
- Posts
- 3,332
- Location
- The South
Hi all,
Wondering if anyone can shed any light on this issue i'm having - About a month or so ago, my system (specs in sig, RAID-0 array for OS) randomly blue screened, didn't think much of it at the time, after google'ing the error code (can't remember what the error was) returned nothing.
A week later it did it again, blue screened and the system restarted, except this time the BSOD took out the Bios - it completely cleared it (does the Abit IP35 Pro have a Bios safety mechanism?)! A little concerned i did a full memtest, which showed the ram (4x 1GB Crucial Balistix 5400) being completely ok, scandisk'd/checkdisk'd/HD Tune error scan'd all of the drives and OS raid array, again returned nothing. Even used SeaTools on the Raid drives (2x ST3160815AS) and that stated that both drives were ok.
Then a few days ago the system crashed with a 'NTLRD is corrupted' error, rebooted the system it worked fine until now, when the system just blue screened whilst opening Flash MX 2004 and the Bios wiped itself.
XP64s event viewer shows the following error -
and
Now i'm completely baffled. I'm assuming it's most likely the ram, as in majority of the cases (apart from the NTLRD errors) i've been using opera or MatLab or Photoshop or Flash etc, although i've done a Prime test maxing out the ram usage (to 4GB) and it didn't causes any problems.
I've taken ram out, reseated it, haven't test it with each stick but i can't seem to replicate the errors.
So, has anyone got a clue what it could be?
All voltages look stable and well within the 5% limits. Temperatures are 21-31c idle & 30-40c under load - so i don't think it's that.
So like i say, i'm completely stumped
p.s - i tried setting the Ballistix's timing back to 3-3-3-12 1T but at 1.9v it caused the NTLRD error, resetting the bios and the system booted (although i did have them running at 3-3-3-12 at 1.8v before these crashes began). Currently, the timings are 5-3-3-15 2T at 1.8v.
Wondering if anyone can shed any light on this issue i'm having - About a month or so ago, my system (specs in sig, RAID-0 array for OS) randomly blue screened, didn't think much of it at the time, after google'ing the error code (can't remember what the error was) returned nothing.
A week later it did it again, blue screened and the system restarted, except this time the BSOD took out the Bios - it completely cleared it (does the Abit IP35 Pro have a Bios safety mechanism?)! A little concerned i did a full memtest, which showed the ram (4x 1GB Crucial Balistix 5400) being completely ok, scandisk'd/checkdisk'd/HD Tune error scan'd all of the drives and OS raid array, again returned nothing. Even used SeaTools on the Raid drives (2x ST3160815AS) and that stated that both drives were ok.
Then a few days ago the system crashed with a 'NTLRD is corrupted' error, rebooted the system it worked fine until now, when the system just blue screened whilst opening Flash MX 2004 and the Bios wiped itself.
XP64s event viewer shows the following error -
Code:
Error code 0000000000000109, parameter1 a3a03a388fafb735, parameter2 b3b746bee22c72e9, parameter3 fffff800013235c4, parameter4 0000000000000001.and
Code:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{555F3418-D99E-4E51-800A-6E89CFD8B1D7}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19). This security permission can be modified using the Component Services administrative tool.Now i'm completely baffled. I'm assuming it's most likely the ram, as in majority of the cases (apart from the NTLRD errors) i've been using opera or MatLab or Photoshop or Flash etc, although i've done a Prime test maxing out the ram usage (to 4GB) and it didn't causes any problems.
I've taken ram out, reseated it, haven't test it with each stick but i can't seem to replicate the errors.
So, has anyone got a clue what it could be?
All voltages look stable and well within the 5% limits. Temperatures are 21-31c idle & 30-40c under load - so i don't think it's that.
So like i say, i'm completely stumped
p.s - i tried setting the Ballistix's timing back to 3-3-3-12 1T but at 1.9v it caused the NTLRD error, resetting the bios and the system booted (although i did have them running at 3-3-3-12 at 1.8v before these crashes began). Currently, the timings are 5-3-3-15 2T at 1.8v.
