Random ntoskrnl.exe BSOD during anything non-intensive.

WingsofWar · 14 Aug 2013

Started out as a random once in a while BSOD that was reporting ntoskrnl.exe, after a while the random BSOD became more frequent. Mainly when doing work on photoshop or writing a document on word. I initially though it was a hardware issue, so i went through GPU CPU and Memory stress tests through Fulmark, prime95 and Memtest86 with no errors and temps still under 50c under load for 10-25min as reported on HWmonitor and GPU-Z.

My frustration got to the point where i just did a fresh installed windows, and im now getting the same random BSOD that cycles through ntoskrnl.exe or ntfs.sys.

Windows 7 Ultimate x64
ASUS M4N78 Pro
AMD Phenom II x6 1045T
4.5g DDR2 Ram
Geforce GT630
Corsair 700AC PSU

I usually don't do this, so i'm turning to you guys for help.

-Josh

Northernsoul55 · 14 Aug 2013

Hi,

From your logs:

Code:

 
******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8005e7f8f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)

Your logs are showing a STOP 0x124. Before delving into StOP 124 remedies,
I noticed your AV is causing issues:

Code:

 
Faulting Driver: aswMonFlt.sys
Refers to: avast! File System Minifilter Driver

I would suggest uninstalling AVAST:

avast! Uninstall Utility | Download aswClear for avast! Removal

As an alternative, please download and install:

Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability
compared to other antiviruses/internet security software.

Note

Once downloaded, update and run a full system scan

Now see if the system is stable, if not and the same issues occur, then please follow:

https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Cheers

Dave

WingsofWar · 14 Aug 2013

thanks Dave for the quick response, iv uninstalled avast and Daemon Tools just in case. I pray that its just programs causing issues and not hardware.

Northernsoul55 · 14 Aug 2013

Hi,

Good work :)

Just use the computer as normal and see if it crashes now?

If you crash again post up a new log.

cheers

Dave

WingsofWar · 15 Aug 2013

So i BSODed again reporting ntoskrnl.exe yet again, since iv deleted Avast the frequency of BSODs have gone down in other applications like word, chrome. But i still get BSOD when doing image editing on Photoshop and lightroom. I was hoping to finish my homework and project tonight, but i guess that is not going to happen.

Attached new logs in zip

Northernsoul55 · 15 Aug 2013

Hi,

Did you use the AVAST removal tool to uninstall?
As it seems there are left over drivers, which will need removed:

aswRvrt.sys
aswVmm.sys

To remove:
Navigate to C:\Windows\system32\drivers
and locate both drivers, right click and delete, reboot the machine.

Scan the system for possible virus infection:

https://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

http://support.kaspersky.com/5350?vs=s88446#s88446

Cheers

Dave

WingsofWar · 15 Aug 2013

Northernsoul55 said:

Hi,

Did you use the AVAST removal tool to uninstall?
As it seems there are left over drivers, which will need removed:

aswRvrt.sys
aswVmm.sys

To remove:
Navigate to C:\Windows\system32\drivers
and locate both drivers, right click and delete, reboot the machine.

Scan the system for possible virus infection:

https://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

http://support.kaspersky.com/5350?vs=s88446#s88446

Cheers

Dave

Hmmm weird, i used the Avast removal tool as recommended. I went into the system32 folder and saw only aswVmm.sys as a .SUM file (aswVmm.sys.SUM) and nothing else related to Avast.

Also Virus checking comes back not infected for any malicious software.

Northernsoul55 · 15 Aug 2013

Hi,

Either re-run the Avast removal tool (bear in mind to choose the correct AVAST version
you had installed)

Or try Driver Fusion to remove the left over drivers:

Download and install:

Driver Fusion.
Reboot the computer in

Advanced Boot Options, safe mode.
Search Driver Fusion in your start menu, and if it says "free version of Driver Fusion cannot remove all the elements" then stop and exit program.

cheers

Dave

WingsofWar · 16 Aug 2013

Iv used the driver fusion and got rid of the Avast drivers. I was able to do homework and photoshop for the longest period of time since this issue first started.

I went and started steam, and then bam, screen froze-up BSOD ntoskrnl.exe again. and now steam wont load up anything anymore.

Northernsoul55 · 17 Aug 2013

Hi,
Well removing AVAST was worth a try, but your latest crash shows
a Stop 0x124, which is usually hardware related.

Code:

 
******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8005e758f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)

As Stop 0x124 minidumps contain very little practical information, it is therefore
necessary to approach the problem as a case of hardware in an unknown state of
distress.

I would also advise to follow this guide:

https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

If you are overclocking STOP. Return to the default settings at least for now.

Stress Tests:
You should perform a stress test on the CPU/hardware to help determine whether a hardware
issue exists:

Hardware - Stress Test With Prime95:

Hardware - Stress Test With Prime95
CPU - Stress Test Using IntelBurnTest:

CPU - Stress Test Using IntelBurnTest
Video Card - Stress Test with Furmark:

Video Card - Stress Test with Furmark

Monitor temperature of the system during the tests with

HWMonitor

Memory Testing:

Also run memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Tip
Run these tests overnight

The goal is to test all the RAM sticks and all the motherboard slots.

Hard drive Diagnostic Tests:

http://carrona.org/hddiag.html

Post back any results/observations

cheers
Dave