ntoskrnl.exe/ntkrnlmp.exe BSOD Whilst Gaming (0xC000001D)

Jaykee · 13 Jul 2013

Hi guys :)

Recently I've had a ton of blue screens on my PC, finally figured out what the problem was for those BSOD's and they aren't happening anymore. But today after playing Battlefield 3 for about 30minutes I came across a new BSOD (info below) and I suppose I need to get some help off the experts here at SevenForums!

Here is my minidump (attached) and some info from WhoCrashed:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 13/07/2013 10:03:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071313-24055-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800030EBBC4, 0xFFFFF8800A5E65F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.

On Sat 13/07/2013 10:03:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800030EBBC4, 0xFFFFF8800A5E65F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

Thanks for any help, will be greatly appreciated!
Jayke.

Jaykee · 13 Jul 2013

Just a heads up, Ive already done these to see if I could see any problems myself:

Ran Memtest86 for over an hour no problems
Ran WD Data Lifeguard tests with no problems

They werent done for this exact BSOD, but were done this morning for other BSOD's which are now fixed!

Arc · 13 Jul 2013

Is your issue over? If not, I can say that the single crash dump you uploaded is a crash during gaming, BF3.

You are overclocked.

Code:

CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2508

If an overclocked system is crashing, it is must to stop overclocking at first. 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)

Display driver is failing.

Code:

fffff880`0a5e6618  fffff880`0fee0a11*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xbda11

And it is old.

Code:

fffff880`0fe23000 fffff880`10b17000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Oct 02 23:51:13 2012 (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Install the latest WHQL only.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 320.49 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

The network driver is failing, too.

Code:

fffff880`0a5e6178  fffff880`10b45132Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x2e132

And the driver is even more old.

Code:

fffff880`10b17000 fffff880`10b50000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri May 22 20:22:30 2009 (4A16BC2E)
    CheckSum:         00041606
    ImageSize:        00039000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek.

The system is old. So we should check the heat, too. 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.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe. And, let us know about the wattage of the PSU.

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

Let us know the results.

And, next time, post it following the Blue Screen of Death (BSOD) Posting Instructions and upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

____________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff800030ebbc4, fffff8800a5e65f0, 0}

Probably caused by : hardware ( nt!KiSystemServiceHandler+7c )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff800030ebbc4, Address of the instruction which caused the bugcheck
Arg3: fffff8800a5e65f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!IopCompleteRequest+4c4
fffff800`030ebbc4 004c8b74        add     byte ptr [rbx+rcx*4+74h],cl

CONTEXT:  fffff8800a5e65f0 -- (.cxr 0xfffff8800a5e65f0)
rax=fffffa8003d65760 rbx=fffffa800484c240 rcx=0000000000000000
rdx=0000000000000342 rsi=0000000000000000 rdi=fffffa80067b9970
rip=fffff800030ebbc4 rsp=fffff8800a5e6fc0 rbp=0000000000000000
 r8=0000000000000002  r9=fffffa8003d65700 r10=0000000003d65700
r11=0000000000000000 r12=0000000000000001 r13=0000000000000000
r14=fffff88002fd3180 r15=fffffa8003d65be0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IopCompleteRequest+0x4c4:
fffff800`030ebbc4 004c8b74        add     byte ptr [rbx+rcx*4+74h],cl ds:002b:fffffa80`0484c2b4=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  bf3.exe

CURRENT_IRQL:  2

IRP_ADDRESS:  ffffffffffffff88

MISALIGNED_IP: 
nt!IopCompleteRequest+4c4
fffff800`030ebbc4 004c8b74        add     byte ptr [rbx+rcx*4+74h],cl

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800030ebbc4

STACK_TEXT:  
fffff880`0a5e5d28 fffff800`030cbde9 : 00000000`0000003b 00000000`c000001d fffff800`030ebbc4 fffff880`0a5e65f0 : nt!KeBugCheckEx
fffff880`0a5e5d30 fffff800`030cb73c : fffff880`0a5e6d88 fffff880`0a5e65f0 00000000`00000000 fffff800`030fa820 : nt!KiBugCheckDispatch+0x69
fffff880`0a5e5e70 fffff800`030f1fad : fffff800`032efc00 fffff800`0322d0d4 fffff800`0305d000 fffff880`0a5e6d88 : nt!KiSystemServiceHandler+0x7c
fffff880`0a5e5eb0 fffff800`030f9620 : fffff800`0321c118 fffff880`0a5e5f28 fffff880`0a5e6d88 fffff800`0305d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a5e5ee0 fffff800`031066cf : fffff880`0a5e6d88 fffff880`0a5e65f0 fffff880`00000000 fffffa80`067b9970 : nt!RtlDispatchException+0x410
fffff880`0a5e65c0 fffff800`030cbec2 : fffff880`0a5e6d88 fffffa80`0484c240 fffff880`0a5e6e30 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`0a5e6c50 fffff800`030ca01f : fffff880`0a5e6e30 fffff880`0a5e6e02 00000000`00000000 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a5e6e30 fffff800`030ebbc4 : 00000000`00000000 fffffa80`0484c240 00000000`00000000 00000000`ffffff00 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0a5e6fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x4c4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`030cb73c b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Jaykee · 13 Jul 2013

Hi there thanks for the great reply.

I think the overclock is due to AMDs SpeedStep Technology because I'm not actually overclocked everything is stock in my machine.
I cleared the CMOS just to be sure.

I've now updated the nVidia driver, didn't actually realise that it was outdated, only installed it today! (Got the GTX650 this morning)

My Network Driver seems to be up to date according to the drivers that I downloaded from the site you gave, so I'm not too sure about that...

My Temps go up to a steady 65*C when under full load for both the CPU and GPU. Other temps are much lower. So I know personally thats nothing to worry about.

By the PSU Calculator I'm using 311w, Im using a 600/750W Modular Power Supply so that is fine I believe.

Im sorry about the post not being perfect. I tried to make it as good as I could after reading that post!

I will go ahead now and test my system to see if I get any more BSOD's, hopefully not! But I will report back.

Thanks!
Jayke.

Jaykee · 13 Jul 2013

So I went to test my computer after making the changes and whilst playing Battlefield 3 again I had another BSOD, which was caused by the USBPORT.SYS. Then whilst writing that on the forum I had another BSOD, from dxgmms1.sys or something similar. I've attached the minidumps below....

Any ideas would be greatly appreciated

Edit: Would you recommend me to reinstall Windows again? Windows 7 or 8?

x BlueRobot · 13 Jul 2013

BSOD Analysis:

Code:

BugCheck D1, {1, 2, 1, fffff8800188d5c2}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_IsrDpc+2c6 )

It seems that an illegal page fault has occurred within thread, a device driver has requested that data which is not present within the available non-paged pool, be paged into memory from the hard-disk, however, this is not a valid option since the scheduler is turned off at dispatch/DPC level (IRQL Level 2), therefore threads can't be scheduled to wait.

Code:

TRAP_FRAME:  fffff88002f92d10 -- (.trap 0xfffff88002f92d10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800568bce0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800188d5c2 rsp=fffff88002f92ea0 rbp=fffffa800567a050
 r8=fffffa800567a1a0  r9=0000000000000000 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr ac po cy
USBPORT!USBPORT_IsrDpc+0x2c6:
fffff880`0188d5c2 4103c6          add     eax,r14d

Code:

2: kd> k
Child-SP          RetAddr           Call Site
fffff880`02f92bc8 fffff800`030b7de9 nt!KeBugCheckEx
fffff880`02f92bd0 fffff800`030b6a60 nt!KiBugCheckDispatch+0x69
fffff880`02f92d10 fffff880`0188d5c2 nt!KiPageFault+0x260 <-- Illegal Page Fault 
fffff880`02f92ea0 fffff800`030c3f7c USBPORT!USBPORT_IsrDpc+0x2c6
fffff880`02f92f00 fffff800`030bea05 nt!KiRetireDpcList+0x1bc <-- Empty DPC queue
fffff880`02f92fb0 fffff800`030be81c nt!KyRetireDpcList+0x5
fffff880`0a28cba0 00000000`00000000 nt!KiDispatchInterruptContinue

--------------------------------------------------------------------------

Have you run Furmark yet?

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Jaykee · 13 Jul 2013

Hi there thanks for the reply. I have run Furmark and left it running for about 10-15mins with no problems. And no I hadnt enabled Driver Verifier. I will enable it now and report back when/if I get another BSOD. Thanks for the heads up! :)

x BlueRobot · 13 Jul 2013

Furmark will need to be running for least a hour, and use Driver Verifier first.

Jaykee · 14 Jul 2013

Okay, I will do that then later on, will report back! Thanks!

Jaykee · 14 Jul 2013

Okay so I ran Driver Verifier and basically my computer was unbearable, couldn't actually do anything, it was like complete meltdown. Had 10fps in bf3 and super slow internet etc. So I went ahead and reinstalled onto Windows 8, being inquisitive(right word?) I installed CPU-Z and after looking at everything, I noticed that my RAM was running at the totally wrong timings + voltage (they were set to auto/default in the bios, hence why I never checked that).

So anyway, this is just an update to say where I'm at. In windows 8 I had a few ntfs.sys bsods and the sort. But I think this may well be the cause of this mayhem. Fingers crossed, will keep you guys updated!