Cannot solve BSOD, tried clean dump, what next?

[sineadie]

Can start my system in safe mode, but even after attempting a clean boot, normal start up leads me to a BSOD.

Pretty sure this was caused by an infection of somekind, because of which I had restarted my system to attempt to remove in safe mode and am now getting this BSOD and cannot find the problem? :

Errors: 0x0000008E (0xC0000005, 0x9974D5EB, 0x8D464A60, 0x00000000)

win32k.sys - Address 9974D5EB base at 996D0000

Thanks

Sinead

 

[Route44]

For the time being let's approach this from a different angle. 0x8E errors, though sometimes can be caused by bad drivers, are almost always caused by faulty hardware and are a good indicator of corrupted memory. So...

We suggest you run memtest on your RAM.

See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: https://www.techspot.com/vb/topic62524.html


* Get back to us with the results.

 

[sineadie]

I'm not sure whether or not this is significant, but thought I should mention it before spending ages on a memtest - I can run another installation of the same OS on a different partition absolutely fine, would this not be similarly affected if it was a hardware problem?

Thanks

 

[Route44]

Then possibly either the partition's OS is corrupt or the harddrive itself has physical issues.

Run a full harddrive diagnostics on that harddrive. As for memtest many people start it before goingto bed and check it the next day.