hal.dll and Blue Screen in Windows XP Home
Posted: 23 Sep 2009, 16:49
I posted this in Windows XP General on Aug. 26, 09. Today, I could not locate
it. Isn't it weird? So I re-post it again.
Hello Microsoft Support,
Starting from Feb. 4, 2009 I have been having Blue Screen from time to time,
about once or twice a month and sometimes none in a month. They were 0x50 and
0x8E.
I replaced the video card on Feb. 17 because I recall the 0x8E blue screen
referred to video card. Since then I only have 0x50 left to deal with.
I learned to use Verifier.exe lately. However, it causes a new blue screen
0xD6. This blue screen is consistent. It happens all the time unlike 0x50
that happens from time to time.
I set up Verifier.exe to verify all but Deadlock detection (because I have
Norton Antivirus) and I select ALL and ONLY Microsoft drivers. Then I enable
Boot Logging upon restart. I compare the log with a log produced by a
successful start and found that the logging stops at hal.dll. The only entry
in the log file upon this Blue Screen is ntoskrnl.exe.
As a cross reference, I set up Verifier.exe the same way but to select ALL
BUT Microsoft drivers. Then I enable Boot Logging upon restart. There's no
blue screen!
So I conclude that one of the Microsoft drivers causes Blue Screen 0xD6.
Most likely hal.dll because that?
it. Isn't it weird? So I re-post it again.
Hello Microsoft Support,
Starting from Feb. 4, 2009 I have been having Blue Screen from time to time,
about once or twice a month and sometimes none in a month. They were 0x50 and
0x8E.
I replaced the video card on Feb. 17 because I recall the 0x8E blue screen
referred to video card. Since then I only have 0x50 left to deal with.
I learned to use Verifier.exe lately. However, it causes a new blue screen
0xD6. This blue screen is consistent. It happens all the time unlike 0x50
that happens from time to time.
I set up Verifier.exe to verify all but Deadlock detection (because I have
Norton Antivirus) and I select ALL and ONLY Microsoft drivers. Then I enable
Boot Logging upon restart. I compare the log with a log produced by a
successful start and found that the logging stops at hal.dll. The only entry
in the log file upon this Blue Screen is ntoskrnl.exe.
As a cross reference, I set up Verifier.exe the same way but to select ALL
BUT Microsoft drivers. Then I enable Boot Logging upon restart. There's no
blue screen!
So I conclude that one of the Microsoft drivers causes Blue Screen 0xD6.
Most likely hal.dll because that?
)