Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD errors ntoskrnl.exe and wdf01000.sys

08 Dec 2011   #1

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
.

08 Dec 2011   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

No DMP files included in upload please try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:


Quote:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
My System SpecsSystem Spec
08 Dec 2011   #3

Windows 7 Professional 64bit
 
 

Here it is Attachment 187426
Was unsure if I need to zip whole folder.
My System SpecsSystem Spec
.


08 Dec 2011   #4
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Please do all of the below...

Asacpi.sys

The pre 2009 version of this driver is a known bsod cause.
Quote:
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).


NEXT >
These crashes were caused by memory corruption. 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.
Quote:
*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.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
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/Windows 7 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.
Driver Verifier - Enable and Disable


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


THEN >
Note.
Your Avast also badly needs updating..
Please do so immediately.
My System SpecsSystem Spec
09 Dec 2011   #5

Windows 7 Professional 64bit
 
 

Thanks, I will let you know how it goes.
My System SpecsSystem Spec
09 Dec 2011   #6
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Will await results with interest.
Good luck!
My System SpecsSystem Spec
04 Sep 2012   #7

Windows 7 Ultimate x64
 
 

Hi, i need some help... having the same error...
My System SpecsSystem Spec
Reply

 Random BSOD errors ntoskrnl.exe and wdf01000.sys




Thread Tools



Similar help and support threads for2: Random BSOD errors ntoskrnl.exe and wdf01000.sys
Thread Forum
Solved BSOD While Idle - wdf01000.sys ntoskrnl.exe BSOD Help and Support
Solved Random BSOD's, mainly ntoskrnl.exe but also other errors. BSOD Help and Support
Random BSOD caused by ntoskrnl.exe and Wdf01000.sys BSOD Help and Support
4+ BSOD/day playing TERA/FFXI [ntoskrnl.exe, rdpbus.sys, Wdf01000.sys] BSOD Help and Support
Random BSOD, Wdf01000.sys and ntoskrnl.exe seem to be causing them. BSOD Help and Support
BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors BSOD Help and Support
BSOD in random moments, ntoskrnl.exe, different errors BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:40 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33