Quote: Originally Posted by Brink
Do you have an old PS/2 keyboard that you could use temporarily to see if you are able to run a SFC scan at boot with?
If not, then you could try doing a system restore
(at boot if needed) using a restore point (if available) dated before this issue to see if it may help before having to move on to more drastic measures.
I was able to launch the command prompt at boot but the SFC scan still returned the same error.
I doubt a system restore will be of much use. I had been having regular BSOD issues (at a rate of about 1 per 2 days) since I built this PC. After figuring out how to read my minidump files, I found that almost all were being caused by my Network driver
, which I have since updated, causing a drastic reduction in the rate of crashes.
The BSODs since always return one of the the following errors and usually occur during boot or very shortly after boot: PFN_LIST_CORRUPT, MEMORY_MANAGEMENT, DRIVER_IRQ_NOT_LESS_OR_EQUAL. I ran Memtest and the Windows Memory Diagnostic Tool but both came out clean. I also made sure that my RAM was receiving the proper voltage and that all of my drivers
were up to date.
Yesterday I tried to run Driver Verifier but it caused the PC to crash upon each boot attempt until the OS automatically forced a system restore to two days prior. I found that the crashes were being caused by a Daemon Tools driver and removed the application.
I then tried to run Driver Verifier again. This time the computer could boot to the Desktop but would then crash within 5 seconds of doing so, reporting an DRIVER_VERIFIER_IOMANAGER_VIOLATION (Hidclass.sys) error.
And that's basically where I am right now.