View Single Post
08 Dec 2011  
cneoryu

Windows 7 Professional 64bit
 
 
Random BSOD errors ntoskrnl.exe and wdf01000.sys

Will randomly BSOD when playing a game to working in microsoft word. When it crashed today took a long time to get back into Windows.

My Specs:

computer name: CORY-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589074432 total
VM: 2147352576, free: 1937952768

On Thu 12/8/2011 6:56:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-33571-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 Thu 12/8/2011 6:56:13 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x405CD)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Attachment 187417

Please help!
My System SpecsSystem Spec