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: ntoskrnl.exe problem

23 Jun 2013   #1
Flory Robert

window7
 
 
ntoskrnl.exe problem

my laptop Is showing bluescreen and I guess there is some problem with this file ntoskrnl.exe please help


My System SpecsSystem Spec
.
23 Jun 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

My System SpecsSystem Spec
23 Jun 2013   #3
Flory Robert

window7
 
 

here is the folder after the instructions I followed
My System SpecsSystem Spec
.

23 Jun 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes free of errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89c58b4ec, b3b7465eeed6f2ae, fffff80000b96bb0, 6}

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt_fffff80000b95000+1bb0 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89c58b4ec, Reserved
Arg2: b3b7465eeed6f2ae, Reserved
Arg3: fffff80000b96bb0, Failure type dependent information
Arg4: 0000000000000006, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:
------------------


FAULTING_IP: 
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`033a85d8 00000000`00000000 : 00000000`00000109 a3a039d8`9c58b4ec b3b7465e`eed6f2ae fffff800`00b96bb0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_NAME:  nt_fffff80000b95000+1bb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt_fffff80000b95000

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5149a99c

FAILURE_BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0

BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0

Followup: MachineOwner
---------
My System SpecsSystem Spec
24 Jun 2013   #5
Flory Robert

window7
 
 

after enabling the driver verifier my laptop is getting hung but its not displaying any bluescreen
My System SpecsSystem Spec
24 Jun 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Have you took the memtest? If not, disable DV now and go for it.
My System SpecsSystem Spec
26 Jun 2013   #7
Flory Robert

window7
 
 

"If Memtest does not automatically boot, go into the BIOS and change the CD drive or USB drive to be the first to boot." what does exactly means? how am I supposed to do it?
My System SpecsSystem Spec
26 Jun 2013   #8
Flory Robert

window7
 
 

this is the bluescreen that has appeared again
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 109
BCP1: A3A039D89EBA46F0
BCP2: B3B7465EF13884B2
BCP3: FFFFF80000B96BB0
BCP4: 0000000000000006
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\062613-19156-01.dmp
C:\Users\HP\AppData\Local\Temp\WER-76643-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My System SpecsSystem Spec
26 Jun 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

My System SpecsSystem Spec
27 Jun 2013   #10
Flory Robert

window7
 
 

It has not detected any errors
My System SpecsSystem Spec
Reply

 ntoskrnl.exe problem




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
DRIVER_POWER_STATE_FAILURE ntoskrnl.exe problem?
My laptop has been experiencing blue screen of death shutdowns frequently when I leave it by itself for a while, I checked my drivers and they are all up to date, I also scanned it using antivirus and there was no virus found. What could be the problem? I've attached the dump file can you please...
BSOD Help and Support
HIDCLASS.SYS & ntoskrnl.exe Problem's
Hi, i'm using Windows 7 Ultimate x64 and updated Service Pack 1 its like to crash when i'm playing game or just to listen music by winamp application ( sometimes it also happen when i just browsing with google chrome ) i've already re-install the OS, but i got the same thing:cry: this is my...
BSOD Help and Support
ntoskrnl.exe problem?
My computer always need start over twice that can enter the OS. sometime will show the ERROR like "dump of physical memory" or "memory crash". I don't know how to solve this problem. Help plz.
BSOD Help and Support
ntoskrnl.exe Problem
X64 Windows 7 often crashes with blue screen, and error ntoskrnl.exe minidump attached:cry: http://www.google.it/images/cleardot.gif
BSOD Help and Support
Problem ntoskrnl.exe
Windows 7 x 64 frequently reboots with blue screen and gives me error This Was Likely Caused By The Following module: ntoskrnl.exe Bugcheck code: 0xA (0xFFFFF88112BFFA80, 0x2, 0x0, 0xFFFFF80002C7F640) Error: IRQL_NOT_LESS_OR_EQUAL Dump File: C: \ Windows \ Minidump \ 041,710 to 17,316-01.dmp...
Drivers
Win 7 Bluescreen ntoskrnl.exe problem
Hello, I have this non stop problem with my new NW21MF Vaio. I start, first comes a bluescreen or Winows message that Winexplorer found a problem and shout down. I run the dump reader and every bluescreen is following (more then 50 times already): ADDITIONAL_DEBUG_TEXT: Use...
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 07:36.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App