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: All kinds of BSOD caused by ntoskrnl.exe

08 May 2015   #1
Schmoerff

Windows 7 enterprise x64
 
 
All kinds of BSOD caused by ntoskrnl.exe

Goodevening people,

I have been getting a lot of bluescreens the last week.
Only today, i've had:
- Three IRQL_NOT_LESS_OR_EQUAL screens, two caused by ntoskrnl.exe, the last one caused by avast.
- Two SYSTEM_SERVICE_EXCEPTION screens, all caused by ntoskrnl.exe
- One ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY screen, also caused by ntoskrnl.exe
- One IRQL_GT_ZERO_AT_SYSTEM_SERVICE screen, also cause by ntoskrnl.exe

I'm using Windows 7 Enterprise SP.

The latest .dmp file contained the following:

Code:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Maarten\Desktop\050815-9906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8f890
Debug session time: Fri May  8 21:58:19.352 2015 (UTC + 2:00)
System Uptime: 0 days 0:02:39.164
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....

************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ab4945, fffff8800b21fa90, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+6a945 )

Followup: MachineOwner
---------
Somehow, since the crashes started, my wifi connection has gotten severely worse. I don't know if this is a related problem or something else entirely.
I hope someone could assist me, i've already replaced Avast with Security Essentials.
Regards,


My System SpecsSystem Spec
.
10 May 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Various different BSODs are there, within a short time span. Which indicates to some sort of memory issue.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. We have to do some further things depending on it.
My System SpecsSystem Spec
15 Jun 2015   #3
Schmoerff

Windows 7 enterprise x64
 
 

I have since then switched my RAM-sticks to slots 2 and 4 (from 1 and 3) and haven't had any issues for the past month. A couple of days ago, i started crashing again. I had about ten crashes within two hours. These crashes were only during intensive gaming. I also noticed my wifi connection was terrible (350 ms latency, while normally, it tends to be around 15).
I have run memtest86 twice, for four and twelve consecutive passes respectively, and haven't had any errors.
My System SpecsSystem Spec
.

15 Jun 2015   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by Schmoerff View Post
I have run memtest86 twice, for four and twelve consecutive passes respectively, and haven't had any errors.
You need to run memtest86+, not memtest86 which is an inferior program with a deceptively similar name.

And it would be the best if you can take a camera snap of the memtest86+ screen before closing memtest86+ and let us see the image.
My System SpecsSystem Spec
15 Jun 2015   #5
Schmoerff

Windows 7 enterprise x64
 
 

I will run memtest86+ tonight. Thanks!
My System SpecsSystem Spec
15 Jun 2015   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Dont forget to click an image after passes are completed. That image may be informative.
My System SpecsSystem Spec
15 Jun 2015   #7
Schmoerff

Windows 7 enterprise x64
 
 

Well, the first errors came in within 5 minutes. Attached is a photo i took. Please Note: the test is still on its first pass and running, as of the moment of taking this picture. If the photo is not attached, my apologies. Im trying to upload this picture from my mobile phone. If nog uploaded, i will upload the image as soon as the computer has run its 8+ passes in the morning.
My System SpecsSystem Spec
15 Jun 2015   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Stop testing now. A single error is enough.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
It is a motherboard issue. The particular slot is bad.

If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.
My System SpecsSystem Spec
15 Jun 2015   #9
Schmoerff

Windows 7 enterprise x64
 
 

I am testing with one stick now. Is this error always going to show up on test 5 on the first pass? Or does it need to do at least 8 passes if it doesnt error?

Edit: thanks for the quick response, by the way :-)
My System SpecsSystem Spec
15 Jun 2015   #10
ACaetta

Windows 7 64 bit
 
 

Arc, would you have any time to help me? I left a post for a BOSD last Saturday night and have not heard from anyone. Derek asked for info but after I left the info he asked for I have never heard anything more. Now my post seems to be lost and forgotten. Don't know what I am supposed to do. I am new here.
My System SpecsSystem Spec
Reply

 All kinds of BSOD caused by ntoskrnl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD caused by driver (ntoskrnl.exe) /adress (ntoskrnl.exe+72a40)
Got my first blue screen of death tonight, had 2 firefox opened one watching youtube video another browsing internet. After bsod it restarted i login but just black screen with cursor, ctrl alt delete worked so i shut my computer down. Boot up normally after, check my minidump file, bsod cause...
BSOD Help and Support
BSOD at least once a day caused by ntoskrnl.exe
Hello, Lately I have been getting the BSOD a fair bit. At first it was about once a couple of weeks, then it started increasing. I did a full format of the HDD in an effort to stop it, it didn't work. It just started occurring more often. I've tried updating all of the drivers, didn't work. I've...
BSOD Help and Support
BSOD caused by ntoskrnl.exe
I was having BSOD issues with windows 8, so I decided to just go back to 7 (since I wasn't liking 8 that much anyway.) I did a fresh install yesterday, and it's still crashing. I've attached the zip file as instructed, and if you need anything else, please let me know! Windows 7 Professional...
BSOD Help and Support
Please Help I get all my BSoD's are caused by ntoskrnl What can I do?
I will attach a example but what can I do delete it?
BSOD Help and Support
BSOD caused by ntoskrnl.exe
I can not put my computer into sleep or hibernate. If I do, I get a BSOD. I reinstalled and installed the nvidia driver, tested it, and was able to sleep/hibernate. Then I updated and get a BSOD. I'm pretty sure it is a Windows update error. I did google searches and really didn't find anything...
BSOD Help and Support
BSOD being caused by ntoskrnl.exe
Hey guys; I searched these forums for other posts; and generally people just suggested repairing windows. When i try an repair my windows 7 (Ultimate 64bit) it tells me it cannot upgrade my system to 32bit, and yes i have been clicking x64 when i choose my system type. Ill dump the...
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 15:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App