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: BSOD most related to ntoskrnl.exe

27 May 2013   #1
Thewho

Windows 7 Ultimate x64
 
 
BSOD most related to ntoskrnl.exe

Hi there, this is my first time posting here.
I've been having these random BSOD lately, most on when playing Battlefield 3,
updated the drivers to the newest already, but still getting the BSODs.
Used bluescreenview and it pointed out that the most was caused by ntoskrnl.exe.
I really have no idea to solve this, and getting about five BSODs per day is pretty anoying.
Attached the SF Diagnostic Tool report, hoping to get some help.


My System SpecsSystem Spec
.
27 May 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The situation appears to be critical. Six BSODs today, with six different Bugcheck code. Depending on the situation, I think it is better to proceed slow and step by step.

What is most important information that you have SPTD installed, and as usual it is crashing.
Code:
fffff880`0aaea458  fffff880`01113adcUnable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
 sptd+0xb4adc
Keeping SPTD present in the system, no troubleshooting is meaningful.
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
  • Double click to open it.
  • Click this button only:
  • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Next, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
Your C drive is substantially filled up? Copy the documents to the other partitions which is having enough free space.

Let us know the situation after doing these three. Depending on the situation we will decide our next steps.
______________________________________________________________________________________
BSOD ANALYSIS:
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004220cee, fffff880077ea568, fffff880077e9dc0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )

Followup: MachineOwner
------------------------------------------------------------------------------------------------
BugCheck A, {fffff38006bfb778, 2, 1, fffff8000473bc8f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff88001b8fdaa, fffff880039b6b60, 0}

Probably caused by : afd.sys ( afd!AfdBReceive+10a )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 1, {741c2e09, 0, f700, fffff8800a877b60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 1E, {ffffffffc0000005, fffff800047be9bc, 0, ffffffffffffffff}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
-------------------------------------------------------------------------------------------------
BugCheck 50, {fffff1a000004700, 1, fffff800049dfe3d, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+884a )

Followup: MachineOwner
---------
My System SpecsSystem Spec
28 May 2013   #3
Thewho

Windows 7 Ultimate x64
 
 

Thanks for the reply.
I followed the three steps above and had one BSOD so far.
Attached the data bellow, will update if there's more.
My System SpecsSystem Spec
.

28 May 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It is crashed with the latest version of display driver.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

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.

Let us know the results.
_______________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd98007288288, 1, fffff8800578cff3, 7}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd98007288288, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800578cff3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004903100
GetUlongFromAddress: unable to read from fffff800049031c0
 ffffd98007288288 Nonpaged pool

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0578cff3 48894108        mov     qword ptr [rcx+8],rax

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880075e3600 -- (.trap 0xfffff880075e3600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800746d630 rbx=0000000000000000 rcx=ffffd98007288280
rdx=fffff8a00af74640 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800578cff3 rsp=fffff880075e3790 rbp=0000000000000000
 r8=fffffa8006bfb7b0  r9=0000000000000001 r10=0000000000000000
r11=fffffa8008e8e3f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3:
fffff880`0578cff3 48894108        mov     qword ptr [rcx+8],rax ds:ffffd980`07288288=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000474852b to fffff800046cbc00

STACK_TEXT:  
fffff880`075e3498 fffff800`0474852b : 00000000`00000050 ffffd980`07288288 00000000`00000001 fffff880`075e3600 : nt!KeBugCheckEx
fffff880`075e34a0 fffff800`046c9d2e : 00000000`00000001 ffffd980`07288288 00000000`00000000 fffff8a0`10b4fac0 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`075e3600 fffff880`0578cff3 : fffff8a0`0b2a1410 fffffa80`06bfd680 fffffa80`08e8d000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`075e3790 fffff880`0578a8af : 00000000`00000000 fffffa80`06afd3f8 00000000`000000bd fffffa80`06e93bf0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa3
fffff880`075e37d0 fffff880`057a465d : 00000000`00000000 fffff8a0`0d7c6790 fffffa80`00000000 fffffa80`096ee2b0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`075e39a0 fffff880`057a4398 : fffff880`04569f40 fffff880`057a3d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`075e3b90 fffff880`057a3e96 : 00000000`00000000 fffffa80`06d2a990 00000000`00000080 fffffa80`08db2010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`075e3bc0 fffff800`04969ede : 00000000`022cdd37 fffffa80`08b23b50 fffffa80`066e2b30 fffffa80`08b23b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`075e3c00 fffff800`046bc906 : fffff880`04565180 fffffa80`08b23b50 fffff880`0456ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`075e3c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
fffff880`0578cff3 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3

Followup: MachineOwner
---------
My System SpecsSystem Spec
29 May 2013   #5
Thewho

Windows 7 Ultimate x64
 
 

So I set the BIOS to default, and had a BSOD on startup,
tried to let windows repair it, and tried to restore the system but both failed.
Then I googled it and found out the problem was the harddisk mode,
changed ACHI to IDE, then I was able to boot again.

But the problem is the system restore actually worked, and the system was set back to date 5/27.
So I lost the dumpfiles after 5/27, and the settings went back.

I followed the steps above again, and here are the new results:

I am not overclocking, and the BIOS are set to default now.

Speccy:


Furmark:
I tested twice, couldn't find the screenshot file location at the first time, so used PrtScn on second attempt.
The temperature gets stable around 75°C.


Memtest:
Memtest passed at 100%.


No BSODs so far, will update if so.
My System SpecsSystem Spec
29 May 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

All seems good.

Now free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
For any further issue, let us know.


BTW, you had storage controller was set to IDE mode earlier, that I found in your original post.
Code:
名稱    Intel(R) 7 Series/C216 Chipset Family 2 port Serial ATA Storage Controller - 1E08
製造廠商    Intel
驅動程式    c:\windows\system32\drivers\intelide.sys (6.1.7600.16385, 16.56 KB (16,960 個位元組), 2009/7/14 上午 07:19)
That was the IDE mode storage driver in use.
My System SpecsSystem Spec
29 May 2013   #7
Thewho

Windows 7 Ultimate x64
 
 

Just got 2 BSODs.
My System SpecsSystem Spec
29 May 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Scan the system for possible virus infection with the following programs.
Update Intel(R) USB 3.0 Driver from https://downloadcenter.intel.com/default.aspx

Update vmicro USB PC Camers driver from the manufacturer's site.

And, Disable USB Selective Suspend.
USB Selective Suspend - Turn On or Off

Also have a look at USB Driver - General Fix for Problems.
My System SpecsSystem Spec
29 May 2013   #9
TimPonken

Windows 7 Home Premium 64bit
 
 

Hehe. I'm having the same issue with ntoskrnl.exe in my thread. Though no idea how to fix it..
My System SpecsSystem Spec
29 May 2013   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by TimPonken View Post
Hehe. I'm having the same issue with ntoskrnl.exe in my thread. Though no idea how to fix it..
Do what Koolkat77 and Golden suggested. They have idea.
My System SpecsSystem Spec
Reply

 BSOD most related to ntoskrnl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while downloading it seems, related to ntoskrnl.exe (probably)
Built this comptuer for friend Crashed "hard" as he put it Brand new computer Fresh windows install Thought it was the hdd, but got it replaced and still crashes. His specs Intel Core i5-3470, PowerColor Radeon HD 7850, Rosewill BlackHawk - Ricky - SpyPossum's Saved Part List - PCPartPicker...
BSOD Help and Support
BSOD while downloading it seems, related to ntoskrnl.exe
Built this comptuer for friend Crashed twice Brand new computer Fresh windows install Thought it was the hdd, but got it replaced and still crashes. His specs Intel Core i5-3470, PowerColor Radeon HD 7850, Rosewill BlackHawk - Ricky - SpyPossum's Saved Part List - PCPartPicker Help would be...
BSOD Help and Support
Recurring Ntoskrnl.exe Related BSOD
Over the course of a few months I've been getting BSODs randomly and they have all been related to the process "Ntoskrnl.exe". If I recall, I get the BSOD whenever I have been downloading something from the internet. I've attached the SF_DD_MM_YYYY.zip file to this post. Any help or a...
BSOD Help and Support
BSOD mostly related to NTOSKRNL.exe
Hello everyone on the forums, i have been experiencing quite a bit of trouble with my system recently. It has been crashing a lot sometimes with BSoDs and sometimes without it. When it crashes without BSoDs my screen goes all fuzzy like there is some graphics distortion or something and i will have...
BSOD Help and Support
BSOD related with ntoskrnl.exe
Hi, I'm having problems with my PC, and it's driving me crazy. It ramdomly goes on blue screens. I used a program named BlueScreenView, it says the causing of that BSODs is a file named ntoskrnel.exe. I also runned MemTest with no errors reported. I don't know what to do, i send to you an...
BSOD Help and Support
BSOD related with ntoskrnl.exe
I just installed windows 7 64-bit on my new computer and everytime I'd do something like install avast anti-virus or add gadgets too quickly, i'd get these blue screens. I used BlueScreenView to see what the problem was, and the most common problem driver is this ntoskrnl.exe I'm pretty sure...
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 11:24.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App