Random BSODs, error 0x0000001e, 0x00000124 and 0x0000000a

[Jacklkw]

My self built computer has been producing bsods at random times since I reinstalled Windows last month. I generally ignore them and restart until the last one which happened in the middle of a gaming session. I noticed that two of the bsods I had were similar and most of them point to ntoskrnl.exe. Here is the results from the program WhoCrashed:

On Sun 11/12/2011 1:58:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121111-12105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 11/12/2011 1:58:25 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 9/12/2011 6:43:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120911-20888-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 5/12/2011 7:23:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120611-13930-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFF80002ED76CB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Any help in this matter is appreciated.

 

[zigzag3143]

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users


Also your version of asacpi.sys is a known cause of BSOD's

Asacpi.sys

The pre 2009 version of this driver is a known bsod cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).

 

[Jacklkw]

zigzag3143,

Thanks for your reply. I have run memtest86 for 6 passes without any errors. I am currently waiting for Driver Verifier to produce the BSOD. Will keep you posted.

 

[zigzag3143]

zigzag3143,

Thanks for your reply. I have run memtest86 for 6 passes without any errors. I am currently waiting for Driver Verifier to produce the BSOD. Will keep you posted.

Good luck

 

[Jacklkw]

No BSOD

I allowed my computer to run continuously as long as I was able to. I also played a few of my games to see whether they were causing the BSODs. It turn out that this whole time the computer did not BSOD at all but there were a few minor problems as follows in my event log during this time:

Event 3, Kernal-EventTracing
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

Event 72, SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

These were actually quite frequent even when Driver Verifier wasn't running. My event log was filled with similar errors that occur at least once a week. However I noticed that one of my games, Microsoft Flight Simulator X seems to crash many times during the loading stage. Here are the following errors:

Event 1000, Application Error
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: HsSrv.dll, version: 1.0.10.917, time stamp: 0x4c930239
Exception code: 0xc0000005
Fault offset: 0x00010bae
Faulting process id: 0x4fc
Faulting application start time: 0x01ccb964b47ef833
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\SysWOW64\HsSrv.dll
Report Id: f43a8c9c-2562-11e1-a391-90e6baa607e7

Event 1000, Application Error
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: atc.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x0002b657
Faulting process id: 0x810
Faulting application start time: 0x01ccb94acb6147a9
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
Report Id: ea614b85-2557-11e1-a391-90e6baa607e7

These errors were actually also quite frequent even when I wasn't running Driver Verifier. I had also updated the ATK0110 Driver and see if that helps.

 

[zigzag3143]

I allowed my computer to run continuously as long as I was able to. I also played a few of my games to see whether they were causing the BSODs. It turn out that this whole time the computer did not BSOD at all but there were a few minor problems as follows in my event log during this time:

Event 3, Kernal-EventTracing
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

Event 72, SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

These were actually quite frequent even when Driver Verifier wasn't running. My event log was filled with similar errors that occur at least once a week. However I noticed that one of my games, Microsoft Flight Simulator X seems to crash many times during the loading stage. Here are the following errors:

Event 1000, Application Error
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: HsSrv.dll, version: 1.0.10.917, time stamp: 0x4c930239
Exception code: 0xc0000005
Fault offset: 0x00010bae
Faulting process id: 0x4fc
Faulting application start time: 0x01ccb964b47ef833
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\SysWOW64\HsSrv.dll
Report Id: f43a8c9c-2562-11e1-a391-90e6baa607e7

Event 1000, Application Error
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: atc.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x0002b657
Faulting process id: 0x810
Faulting application start time: 0x01ccb94acb6147a9
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
Report Id: ea614b85-2557-11e1-a391-90e6baa607e7

These errors were actually also quite frequent even when I wasn't running Driver Verifier. I had also updated the ATK0110 Driver and see if that helps.

As indicated earlier

The above paramter indicates a memory exception (memory corruption) run the tests to find out what, and why.

 

[Jacklkw]

Run which test? I already ran memtest86+ for 6 passes and didn't get a single error.

 

[zigzag3143]

Run which test? I already ran memtest86+ for 6 passes and didn't get a single error.

Driver verifier. None of the previous dmps had verifier enabled

 

[Jacklkw]

Ok, I will continue running Driver Verifier for as long as I possibly can or until a BSOD happens. Will keep you posted, thanks for your help.

 

[Jacklkw]

Ok, I got a system crash and a BSOD today which was caused by Briver Verifier. The computer crashed while I was leaving my computer on overnight and when I woke up to use it the screen was on but blank and the system was unresponsive. Later when I rebooted after a Windows Update, my computer BSOD this time. This time Windows strangely saved the dump into memory.dmp which was 130 mb in size after compression so I am unable to upload it. If necessary you can show me how to open the file and read its contents so that I could post it here. I have already checked to make sure that save dump file was back to minidump in control panel. Here is the description from the program WhoCrashed:

On Thu 15/12/2011 1:14:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121511-16114-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC4 (0x37, 0x0, 0x0, 0xFFFFFA800B7946F8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver tried to acquire a resource, but APCs are not disabled. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 15/12/2011 1:14:06 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mdfsysnt.sys (MDFSYSNT+0x48F17)
Bugcheck code: 0xC4 (0x37, 0x0, 0x0, 0xFFFFFA800B7946F8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\mdfsysnt.sys
product: Mediafour MacDrive
company: Mediafour Corporation
description: MacDrive file system driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver tried to acquire a resource, but APCs are not disabled. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mdfsysnt.sys (MacDrive file system driver, Mediafour Corporation).
Google query: mdfsysnt.sys Mediafour Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

 

[peiljj]

I have the same problem. I had a long response typed out and mine PC crashed. LOL
I'll post back here when I get more time, probably tomorrow night or this weekend.
Jeff

 

[zigzag3143]

I have the same problem. I had a long response typed out and mine PC crashed. LOL
I'll post back here when I get more time, probably tomorrow night or this weekend.
Jeff

Jeff we still need the DMPs.

I do notice a Zone Alarm file you should remove ZAP.

 

[Jacklkw]

Got another few BSODs today. It became so frequent that I decided to disable Driver Verifier. Here are the Minidump files as per requested. Thanks for your help zigzag3143.

 

[zigzag3143]

Got another few BSODs today. It became so frequent that I decided to disable Driver Verifier. Here are the Minidump files as per requested. Thanks for your help zigzag3143.

Driver verified and Related to MDFSYSNT.SYS MacDrive Partition Manager from Mediafour Corporation.

Would have been nice if you told us so we could help you efficiently.

 

[Jacklkw]

Upon checking the results from the program WhoCrashed, I did notice out of the numerous BSODs I had only one of them was related to mdfsysnt.sys. Most of the rest are related to ntoskrnl.exe. Any idea what it is because it is causing most of my BSODs. I did notice though that recently, every time I turn off my computer I got a BSOD related to ntoskrnl.exe. By the way, what should I do about mdfsysnt.sys? I need MacDrive because I have two mac formatted hard drives in my system.

 

[zigzag3143]

Upon checking the results from the program WhoCrashed, I did notice out of the numerous BSODs I had only one of them was related to mdfsysnt.sys. Most of the rest are related to ntoskrnl.exe. Any idea what it is because it is causing most of my BSODs. I did notice though that recently, every time I turn off my computer I got a BSOD related to ntoskrnl.exe. By the way, what should I do about mdfsysnt.sys? I need MacDrive because I have two mac formatted hard drives in my system.

Who crashed is often incorrect.

Cant be ntoskrnl.exe or the computer would have much more problems.


STILL Related to MDFSYSNT.SYS MacDrive Partition Manager from Mediafour Corporation. I am sure that this isnt the only app that can read a Mac drive.

 

[Jacklkw]

MacDrive is the best application out there that can read mac drives. Whats more I bought the program. What else can I do?

 

[zigzag3143]

MacDrive is the best application out there that can read mac drives. Whats more I bought the program. What else can I do?

You have three options. Live with the BSOD's, find another app for that, or remove it.

BSOD's are cuased by combinations of drivers and you have one set of them that causes it to crash. You might have success wiwth a clean win 7 re-install but then you would probably re-install the other drivers that would make this crash again.

 

[Jacklkw]

Ok, I uninstalled MacDrive completely. Just when I thought things were back to normal again, my computer BSOD again while I was in the middle of playing a game. What else is there that is unsolved?