BSOD A device driver attempting to corrupt the system has been caught.

ScrumpyDorito · 14 Dec 2011

writhziden said:

ScrumpyDorito said:

Right thats all done, clean clean clean for sure this time. I forgot to driver sweeper the other reinstall previously.

Hopefully that will solve it. :)

I wish heres another one! Its never ending!

writhziden · 14 Dec 2011

Alright, try each of the following (one at a time for 24 hours each, or until a BSOD occurs):

Task 1. Shut down and turn off your computer. Unplug the power cord from the wall/surge protector. Disconnect all unneeded devices from your computer (usb, firewire, flash cards, etc.); leave only your mouse, keyboard, and monitor connected.

Task 2. Open an elevated command prompt (Start Menu->All Programs->Accessories->Right click command prompt->Run as administrator) and type chkdsk /r c: (and/or chkdsk /r d:, chkdsk /r e:, etc. for all drives that have system or program files on them).

Task 3. Shut down and turn off the computer. Unplug the power cord from the wall/surge protector. Hold down the power button for 30 seconds to drain all residual power in the system. Open up your case. Remove all components from the motherboard (completely remove memory, graphics card, etc.). Replace necessary components first (graphics card, at least one memory module). Run for 24 hours or until next BSOD. Replace all other components one at a time with a 24 hour interval in between (or until next BSOD) to determine which is causing the problem.

ScrumpyDorito · 23 Dec 2011

Yo I got a new one, but the first time it wasnt a blue screen. I was playing star wars the old republic, and the computer just restarted. No BSOD no warnings nothing. So I rebooted and it cma eup with a system driver has over run is stack based buffer? Or something like that. Im going to upload that BSOD.

writhziden · 23 Dec 2011

ScrumpyDorito said:

Yo I got a new one, but the first time it wasnt a blue screen. I was playing star wars the old republic, and the computer just restarted. No BSOD no warnings nothing. So I rebooted and it cma eup with a system driver has over run is stack based buffer? Or something like that. Im going to upload that BSOD.

Which of the above steps have you tried?

ScrumpyDorito · 24 Dec 2011

I did them all, ran on all damn basic for a day, then with my sound card, then with my video card, then with all 5g of my ram. Also tried running it on two diff HDDs

writhziden · 24 Dec 2011

Did all of the steps still cause blue screen errors, or was there a piece of hardware added that started them again? It could still be RAM related. You've already run Memtest86+ and I believe you found no errors after getting rid of the one bad module, correct? Recommend running the extended version of Diagnosing memory problems on your computer

ScrumpyDorito · 26 Dec 2011

There were no blue screen errors from any of the hardware :S, the last thing I added was my graphics card. The blue screen I linked in the last post was very very new and worrying. Im going to try ordering new, better quality RAM and see if that helps.

ScrumpyDorito · 28 Dec 2011

Ive had enough of my computer blue screening, its not my RAM, its not my GPU, its not any faulty motherboards slots. The file that is causing all these damn issue is ntfoskrnl.sys being corrupted. I need to know how to fix THAT because THAT is whats causing these blasted errors!

writhziden · 28 Dec 2011

ScrumpyDorito said:

Ive had enough of my computer blue screening, its not my RAM, its not my GPU, its not any faulty motherboards slots. The file that is causing all these damn issue is ntfoskrnl.sys being corrupted. I need to know how to fix THAT because THAT is whats causing these blasted errors!

If that file is corrupted (which I highly doubt as it is usually pointed to for blue screen errors when in fact it is a device driver or program at fault) then SFC /SCANNOW Command - System File Checker would fix it.

The reason ntoskrnl.exe is often pointed to is it is a main system file that is used by so many different processes. The blue screen picks it since it is unable to determine the actual fault. If you want to find the fault, you may have to run Verifier on one non-Microsoft driver at a time until one of them causes a fault more often than the others, or on startup. That will tell you which driver is causing issues.

ScrumpyDorito · 28 Dec 2011

writhziden said:

ScrumpyDorito said:

Ive had enough of my computer blue screening, its not my RAM, its not my GPU, its not any faulty motherboards slots. The file that is causing all these damn issue is ntfoskrnl.sys being corrupted. I need to know how to fix THAT because THAT is whats causing these blasted errors!

If that file is corrupted (which I highly doubt as it is usually pointed to for blue screen errors when in fact it is a device driver or program at fault) then SFC /SCANNOW Command - System File Checker would fix it.

The reason ntoskrnl.exe is often pointed to is it is a main system file that is used by so many different processes. The blue screen picks it since it is unable to determine the actual fault. If you want to find the fault, you may have to run Verifier on one non-Microsoft driver at a time until one of them causes a fault more often than the others, or on startup. That will tell you which driver is causing issues.

Im just starting to lose all hope now, Im going to try and run the verifier on each driver that isnt microsoft related and see what will happen. Now for the verifier, Im not 100% sure how it works. Will it force a blue screen on ANY driver I verify? Or will it only bluescreen the computer if the driver is corrupt.