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? ntoskrnl.exe

12 Sep 2010   #1

Windows 7 Ultimate 32bit
 
 
Random bsod? ntoskrnl.exe

Hello, I'm new to the this community. I've come because I'm having random bsod's I've tried even reformatting to no avail.

I'm running Win 7 Ultimate 32bit Retail.

I've ran the system repair on the win 7 disk but it hasn't helped.

I've attached four minidumps(I've renamed the .txt because it wouldn't let me upload .dmp's). I'll be very happy if someone can give me a clue to what's going on.

It seems to be ntoskrnl.exe. Which I've heard might have to do with the keyboard so I swapped it, but it didn't help.

I've ran WhosCrashing and I have this info:

On Thu 9/9/2010 4:52:42 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x48A27975, 0x2, 0x1, 0x82C03839)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\090910-17656-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 9/9/2010 4:46:07 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xD020, 0x2, 0x0, 0x82891AEF)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\090910-19093-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 9/9/2010 4:16:31 AM your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0x8292D4A3)
Error: DRIVER_CORRUPTED_EXPOOL
Dump file: C:\Windows\Minidump\090910-21140-01.dmp
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 9/12/2010 12:53:57 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xF4221B58, 0x0, 0x828C711D, 0x2)
Error: Unknown
Dump file: C:\Windows\Minidump\091210-23859-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 9/12/2010 10:23:18 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1000000A (0x248318B1, 0x2, 0x1, 0x8280E839)
Error: Unknown
Dump file: C:\Windows\Minidump\091210-23343-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 9/12/2010 11:43:23 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0x97EB7838, 0x97EB7410, 0x82883CF8)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\091210-16375-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 9/11/2010 6:44:44 PM your computer crashed
This was likely caused by the following module: fileinfo.sys
Bugcheck code: 0x10000050 (0xD2154546, 0x0, 0x8289BA9A, 0x2)
Error: Unknown
Dump file: C:\Windows\Minidump\091110-15187-01.dmp
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


My System SpecsSystem Spec
.

14 Sep 2010   #2
Microsoft MVP

 
 

If you upload dump files, please zip them up. They take less space and are easy for us to handle.

Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
Quote:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://<a href="http://www.carrona.o... Reference</a> ).
Please pay particular attention to any dated 2008 or earlier:
Code:
e100b325.sys Fri Nov 16 13:53:32 2007 - Intel(R) PRO/100 Adapter NDIS 5.1 driver - http://www.carrona.org/dvrref.html#e100b325.sys
OMAWGU.sys   Tue Jan 02 21:16:28 2007 - Belkin My Essential  G USB Adapter - http://www.carrona.org/dvrref.html#OMAWGU.sys
smwdm.sys    Mon Mar 28 10:19:36 2005 - SoundMAX Integrated Digital Audio driver - http://www.carrona.org/dvrref.html#smwdm.sys
Some comments would seem appropriate here:
- the audio and network components are older devices, so I'd wonder about the compatibility of your motherboard with Windows 7. It's important to use Windows 7 drivers if they are available. The use of Vista or earlier drivers is apt to have issues with older hardware - so I'd recommend a new mobo because of that.
- the wireless USB adapter is known to have issues with Windows 7. You MUST use Windows 7 drivers with this device as other drivers are known to have issues. Additionally, you'll have less problems and greater connectivity if you switch over to a wireless card installed inside of your case (the antenna hangs out the back) that is Windows 7 compatible.

BSOD BUGCHECK SUMMARY
Code:

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 19:20:09.099 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:28.021
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck A, {90ba4a40, 2, 1, 82818839}
Probably caused by : ntkrnlmp.exe ( nt!Kei386EoiHelper+29d3 )
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 22:40:55.781 2010 (UTC - 4:00)
System Uptime: 0 days 0:17:40.703
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck C5, {4, 2, 1, 8292d4a3}
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : tcpip.sys ( tcpip+8df26 )
BUGCHECK_STR:  0xC5_2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 00:45:11.180 2010 (UTC - 4:00)
System Uptime: 0 days 0:29:05.102
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck A, {d020, 2, 0, 82891aef}
Probably caused by : ntkrnlmp.exe ( nt!ExfAcquirePushLockExclusive+8aa )
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 00:50:35.622 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:50.543
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
BugCheck A, {48a27975, 2, 1, 82c03839}
Probably caused by : ntkrnlmp.exe ( nt!Kei386EoiHelper+29d3 )
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 
My System SpecsSystem Spec
14 Sep 2010   #3
Microsoft MVP

 
 

If the above stuff doesn't help, please run Driver Verifier according to these instructions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
.


Reply

 Random bsod? ntoskrnl.exe




Thread Tools



Similar help and support threads for2: Random bsod? ntoskrnl.exe
Thread Forum
Solved BSOD very random ntoskrnl.exe BSOD Help and Support
Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0 BSOD Help and Support
Solved Random BSOD in ntoskrnl.exe BSOD Help and Support
Solved Random BSOD's by ntoskrnl.exe BSOD Help and Support
Random BSOD--ntoskrnl.exe BSOD Help and Support
Random BSOD ntoskrnl.exe BSOD Help and Support
ntoskrnl.exe, random bsod's 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 09:47 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