BSODs with different .sys files

[Andrew060]

Hey all, I've recently put together a new build and I keep getting BSODs at different times. Sometimes the build will be fine for days then it will crash, or it will crash as soon as I turn it on.


I've updated MotherBoard and Graphics drivers. I've tried different working RAM and a different GPU. I downloaded BlueScreenView and it seems that every BSOD has been caused by ntoskrnl.exe, with different .sys files with each BSOD.


I booted the computer into SafeMode with Networking and it didn't crash for 3 days. So that leads me to believe that it may be a driver that's being loaded upon boot up.

I turned on Driver Verifier for the most recent .dmp file in the uploaded batch. Ive turned it off since then.

I've run Memtest86 and got no errors. I let it do 3 passes.

I've run CPU stress tests and my CPU stays at 55c.

I've run a virus scan with various programs, none of them have picked up anything.

I appreciate any and all help

 

[ICIT2LOL]

Hello and welcome Andrew mate first up you need to run memtest for at least8 passes anything less is not good enough. I f errors do not come up before 8 then it is a good idea to let two more passes run - overnight while the machine is not in use is good time to do this.


MEMTEST

The memtest you will need to make a bootable disk / stick andset the BIOS to boot from the optical or USB and it will take a fair time torun- some leave it overnight. http://www.memtest.org/

But one thing is very important you must let the test run for at least 8 passes any less and thefindings are no good. Now if errors come up straight away then you can stop it- see my pics. Now if there are errors and you have more than one stick of RAMin then you will need to test each stick ie remove the sticks and replace stick1 in slot 1 and test no errors do the same in slot 2 with stick 1 no errorsthen repeat the process with stick 2 - that will show up the faulty stick - theother thing is it could be a faulty slot but most unusual.
It is a very lengthy and tedious process but worth it if you have.

Lets do this before anything else

 

[Andrew060]

I shall run 10 tests now

 

[ICIT2LOL]

Let us know as soon as it is done mate

 

[Andrew060]

Its done 3 passes so far, the clock is at 26 hours past. This may take awhile

 

[ICIT2LOL]

Hmm Andrew mate has it been running for 26 hours?? Because that seems like an inordinate amount of time for even a large amount of RAM you have installed by the way you have not got down how much RAM you have in that machine so do you have a lot of RAM / lot of sticks etc ??

 

[Andrew060]

Well this looks bad.

 

[Andrew060]

I have 2x8GB sticks

 

[ICIT2LOL]

Yes mate not good at all.

Now you need to pin down which of the sticks (or all) are throwing the errors and to do that s going to take some time.
All I can suggest is to test stick #1 in slot #1 no errors then stick #2 in slot #1 then - no errors then stick #1 in slot #2 and then stick #2 in slot #2 and so forth until you have winkled out the bad of those two sticks. Now having said that it takes time - if the errors are coming up reasonably quickly then it may not take a long time.

The other issue just maybe that the sticks test with no faults in slot #1 and in that case it will point the finger at slot #2 as being the culprit . A possibly though - not definite it would be unusual for it to be the board at fault - unless it has had a rough life or a surge for example.

I think the stocks or one of them is pulling up short and requires replacing.