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

[ScrumpyDorito]

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]

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]

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]

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]

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]

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]

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]

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]

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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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]

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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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.

 

[writhziden]

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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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.

Verifier intentionally puts the computer in situations that will cause a driver to fail if that driver is incompatible/corrupted and needs to be updated/replaced/have the hardware replaced. The hardware replacement is usually due to hardware not being supported anymore by the manufacturer, not typically because the hardware is bad, although bad hardware can cause issues, as well. We'll deal with that when we get there.

Just test each driver with Verifier, and any that seem suspect, let us know. Good drivers/good hardware should not cause any issues for a very long time (~36 hours). Bad drivers will blue screen within an hour or two, and very bad drivers can blue screen on startup or within 30 seconds of login when the services start.

Edit: recommend posting your dmp files anytime you get a blue screen with Verifier running. That way, we can determine whether the blue screen was indeed related to the verified driver.

 

[ScrumpyDorito]

Ok Im going to try all the drivers, Im going to write them done and ticks what failed horribly and what didnt. Ill get back to you soon.

 

[ScrumpyDorito]

Ok Im going to try all the drivers, Im going to write them done and ticks what failed horribly and what didnt. Ill get back to you soon.

Now my computer is just restarting randomly, without any errors ( that I can see ) it reminds me of once time my mums comp was overheating and just restarting. I checked the temps on the MB for the processor and after restarts its a stable 30c. How do I check for the errors?

also Im still in the process of driver verifiering all the drivers that arent microsoft.

 

[writhziden]

Ok Im going to try all the drivers, Im going to write them done and ticks what failed horribly and what didnt. Ill get back to you soon.

Now my computer is just restarting randomly, without any errors ( that I can see ) it reminds me of once time my mums comp was overheating and just restarting. I checked the temps on the MB for the processor and after restarts its a stable 30c. How do I check for the errors?

also Im still in the process of driver verifiering all the drivers that arent microsoft.

Could be overheating, and it could be malware. Do the following steps one at a time and post back your results after each.

1. Check temperatures of all major components using HWiNFO64 Download and start it in sensor mode only. Create a log and upload it on here after a restart occurs. You may have to upload it as a zip file of the .csv file.
2. Get the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not use the trial) and intall it and get updates. Start in http://www.sevenforums.com/tutorials/69585-safe-mode.html and run a full scan.
3. Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software and start in http://www.sevenforums.com/tutorials/69585-safe-mode.html. Unzip the rescue file and let it run in safe mode.
4. Run the Fakerean removal tool (make sure to save and close any open windows as it restarts the computer without much warning).

 

[ScrumpyDorito]

Ok Im going to try all the drivers, Im going to write them done and ticks what failed horribly and what didnt. Ill get back to you soon.

Now my computer is just restarting randomly, without any errors ( that I can see ) it reminds me of once time my mums comp was overheating and just restarting. I checked the temps on the MB for the processor and after restarts its a stable 30c. How do I check for the errors?

also Im still in the process of driver verifiering all the drivers that arent microsoft.

Could be overheating, and it could be malware. Do the following steps one at a time and post back your results after each.

1. Check temperatures of all major components using HWiNFO64 Download and start it in sensor mode only. Create a log and upload it on here after a restart occurs. You may have to upload it as a zip file of the .csv file.
2. Get the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not use the trial) and intall it and get updates. Start in http://www.sevenforums.com/tutorials/69585-safe-mode.html and run a full scan.
3. Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software and start in http://www.sevenforums.com/tutorials/69585-safe-mode.html. Unzip the rescue file and let it run in safe mode.
4. Run the Fakerean removal tool (make sure to save and close any open windows as it restarts the computer without much warning).

Ive done all the scans and my computer came back clean. I have been running ESET smart security and thats pretty good protection.

Im going to run the TEMP program and run Star Wars the old republic, it usually does it when Im playing that. Ill upload the CPU temps on the next restart

Edit 1: Currently IDLE my "Current" Temp is 51.0C, my Min is 49.5C, and my max is 52C. This is sitting idle.

 

[ScrumpyDorito]

I give up, 100% give up, I can handle the stress of being in a game or working on something and blows up.

Its pretty much a brand...new....build and out of the box. No one can fix it without taking it off of my hands for £100. Im getting a new one.

 

[writhziden]

I give up, 100% give up, I can handle the stress of being in a game or working on something and blows up.

Its pretty much a brand...new....build and out of the box. No one can fix it without taking it off of my hands for £100. Im getting a new one.

What were the temperatures when it crashed this past time? Do you have the CSV file for us to take a look at?

 

[ScrumpyDorito]

Here it is

 

[writhziden]

Here it is

...(Nevermind, these changed units)...

CPU 0		CPU		Motherboard
45.0 °C		44.0 °C		29.0 °C
45.0 °C		44.0 °C		29.0 °C
44.8 °C		44.0 °C		29.0 °C
114.8 °F	111.2 °F	84.2 °F
112.1 °F	111.2 °F	84.2 °F
111.2 °F	111.2 °F	84.2 °F
111.2 °F	109.4 °F	84.2 °F
113.2 °F	109.4 °F	84.2 °F
111.7 °F	109.4 °F	84.2 °F
117.3 °F	109.4 °F	84.2 °F
116.2 °F	109.4 °F	84.2 °F

...(Nevermind, these changed units)...

SAMSUNG HD103SJ [S246J9FZB02225]		GPU Temperature		
33.0 °C							39.0 °C
33.0 °C							39.0 °C
91.4 °F							104.0 °F
91.4 °F							102.2 °F
91.4 °F							102.2 °F
91.4 °F							102.2 °F
91.4 °F							104.0 °F
91.4 °F							102.2 °F
91.4 °F							102.2 °F
91.4 °F							104.0 °F

Did you change the units before the crash, or did you stop logging after changing units?

 

[ScrumpyDorito]

Changed.....units? Im not sure what that is.