G
Guest
Dell D600 M Laptop
512 MB RAM
1.7 GHz Centrino
BugCheck 50, {ff909000, 0, 804e422b, 0}
I have been fighting a stop 0x50 error for several months now. Dell has
replaced motherboard, memory, processor, and HD. 2 other people in my area
with the exact same configuration have the same problem, and it started
happening for all of us around March. I went to SP2 to hopefully fix this,
but it didn't help and possibly made it worse. I am in SP1 right now.
I have multiple mini and kernel dump files. The first set was prior to
turning on the verifier. It shows a random mem address in upper memory, but
always the same source address which shows up in the NT kernel itself
804e422b.
Turning on the verifier switched all of the blue screens to 0xC4_090
errors instead. I used SiSoft Sandra to exercise the system, and got
consistent failures during the HD test with verifier on. I could not even
run that test without crashinng.
The first post-verifier dump identified SAVRT.SYS, so I disabled all
Symantec Antivirus services (9.0 Corporate) and processes and tried again.
Next, it reported a fault back in ntoskrnl.exe. I backed out one of the
following hotfixes to put NTOSKRNL.EXE back prior to March 2005
(890859,826939, 885835). These hotfixes werre pushed down by a corporate
auto-update tool, which I suspect is the reason why this started happening
all of a sudden.
With an October 2004 version of NTOSKRNL.EXE resinstalled, I ran the
SiSoft disk test twice in a row with no problems. I don't have enough run
time to prove this 100%, but if this fixes it then I can't upgrade to SP2 or
accept further security updates on these three Dell systems.
Dell is trying to troubleshoot this, as is our IT department. But, we
clearly need Microsoft's help in taking it to the next level. WinDBG is
helpful, but I am a novice in using it. I am a firmware programmer by trade,
but am not skilled in Windows kernel troubleshooting.
I can forward whichever dumps and logs you want.
Regards,
Ron Garnett
512 MB RAM
1.7 GHz Centrino
BugCheck 50, {ff909000, 0, 804e422b, 0}
I have been fighting a stop 0x50 error for several months now. Dell has
replaced motherboard, memory, processor, and HD. 2 other people in my area
with the exact same configuration have the same problem, and it started
happening for all of us around March. I went to SP2 to hopefully fix this,
but it didn't help and possibly made it worse. I am in SP1 right now.
I have multiple mini and kernel dump files. The first set was prior to
turning on the verifier. It shows a random mem address in upper memory, but
always the same source address which shows up in the NT kernel itself
804e422b.
Turning on the verifier switched all of the blue screens to 0xC4_090
errors instead. I used SiSoft Sandra to exercise the system, and got
consistent failures during the HD test with verifier on. I could not even
run that test without crashinng.
The first post-verifier dump identified SAVRT.SYS, so I disabled all
Symantec Antivirus services (9.0 Corporate) and processes and tried again.
Next, it reported a fault back in ntoskrnl.exe. I backed out one of the
following hotfixes to put NTOSKRNL.EXE back prior to March 2005
(890859,826939, 885835). These hotfixes werre pushed down by a corporate
auto-update tool, which I suspect is the reason why this started happening
all of a sudden.
With an October 2004 version of NTOSKRNL.EXE resinstalled, I ran the
SiSoft disk test twice in a row with no problems. I don't have enough run
time to prove this 100%, but if this fixes it then I can't upgrade to SP2 or
accept further security updates on these three Dell systems.
Dell is trying to troubleshoot this, as is our IT department. But, we
clearly need Microsoft's help in taking it to the next level. WinDBG is
helpful, but I am a novice in using it. I am a firmware programmer by trade,
but am not skilled in Windows kernel troubleshooting.
I can forward whichever dumps and logs you want.
Regards,
Ron Garnett