System crashed

[90312]

This is the cause from the dump.

[HeatherVela]

How do I fix that driver? What is it for? Thank you for the information - I feel like I am getting somewhere now!!!

[GregiBoy]

I suspect that it is another driver interacting with it....

ntoskrnl.exe (and ntkrnlpa.exe on systems with Physical Address Extension support) is the kernel image for the family of Microsoft Windows NT operating systems. It provides the Kernel and Executive layers of the Windows NT kernel space, and is responsible for various system services such as hardware virtualization, process and memory management, etc., thus making it a fundamental part of the system. It contains the Cache Manager, the Executive, the Kernel, the Security Reference Monitor, the Memory Manager, and the Scheduler, among other things

[90312]

Short answer: I don’t know. That driver is the kernel driver and part of the system, unlikely to be corrupt. You can run command prompt as administrator and type: “sfc /scannow” that is the system file checker to see if there is a problem with any of the protected system files. I tend to agree with GregiBoy that there is probably a conflict, something else is residing at the memory address.

[Blazkowicz]

You can try to remove the driver GEARAspiWDM.sys.

[signals]

I removed it some time ago with no ill effects except some whining from iTunes, which can be ignored.

[HeatherVela]

New minidump file - still not working.

[HeatherVela]

Just ran the sfc/scannow and it found no intergrity issues.

[HeatherVela]

Don't find that driver anywhere

[90312]

Check in C:\windows\system32 but do not delete ntoskrnl.exe, you must have that one.

[maineman]

FYI:

http://www.sevenforums.com/crashes-debugging/23643-ntoskrnl-exe-bsod.html

HTH