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 ntoskrnl.exe 0x000000d1 HELP!! (Playing Crysis2)


28 Apr 2012   #1

Windows 7 Ultimate x64
 
 
BSOD ntoskrnl.exe 0x000000d1 HELP!! (Playing Crysis2)

Hi,

I've been getting alot of BSOD's, Mainly when playing Crysis2 (within 2-3 minutes of playing).
I also recently got one trying to do a Computer rating (Windows experience Index)

Prior to this I was getting BSOD's after installing drivers for my USB wireless adaptor - (Netgear n600), so I changed to a Linksys PCI adapter which I thought solved the issue.....but now the blue screens are back!

BlueScreenView shows that ntoskrnl.exe seems to be the problem?...I ain't got a clue so any help is appreciated!


Windows 7 Ultimate x64 bit (retail) SP1

- What is the age of system (hardware)? - New (had PC 1 week)
- What is the age of OS installation - 1 week

Manufacturer: GIGABYTE
Processor: AMD A6-3500 APU with Radeon HD graphics 2.10GHz
RAM: 8GB
Asus Radeon 6670 installed

My System SpecsSystem Spec
.

29 Apr 2012   #2

Windows 7 Ultimate x64
 
 

Anyone?

I've ran memtest86 with no errors not sure what else to do!?
My System SpecsSystem Spec
30 Apr 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Problematic Software:
Code:
Start Menu\Programs\Uniblue\PowerSuite	Public:Start Menu\Programs\Uniblue\PowerSuite	Public

Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public

Start Menu\Programs\AMD VISION Engine Control Center	Public:Start Menu\Programs\AMD VISION Engine Control Center	Public
For PowerSuite: Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs. Also, automated driver update utilities often find driver updates to hardware that is similar to but not exactly the same as the hardware being updated. This can lead to conflicts and blue screen crashes.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7. If you need driver updates, please post a thread in Drivers - Windows 7 Forums


Gigabyte Easy Tune 6 is known to cause problems in Windows 7. I would recommend removing it.


AMD Vision Engine Control Center sometimes overclocks the graphics card without the user's knowledge. Check the settings for it and make sure there is no overclocking being done. Remove it and install only your device drivers for your display card if possible.


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


Loading Dump File [D:\Kingston\BSODDmpFiles\GreenyLG\Windows_NT6_BSOD_jcgriff2\042812-20108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`03292670
Debug session time: Sat Apr 28 15:29:10.174 2012 (UTC - 6:00)
System Uptime: 0 days 1:42:41.766
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800030df0bb, fffff88003ca9c70, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

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

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

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!IopCompleteRequest+5eb
fffff800`030df0bb 41f604247f      test    byte ptr [r12],7Fh

CONTEXT:  fffff88003ca9c70 -- (.cxr 0xfffff88003ca9c70)
rax=0000000000000000 rbx=fffffa800b41b010 rcx=fffff900c01ccd98
rdx=fffffa800b16d3e1 rsi=0000000000000000 rdi=fffffa800947ea50
rip=fffff800030df0bb rsp=fffff88003caa650 rbp=0000000000000000
 r8=fffffa800b16d3e0  r9=0000000000000000 r10=fffff88002f64fa0
r11=fffffa800b468580 r12=0000000000000200 r13=0000000000000000
r14=fffffa8009469060 r15=fffff88003caac20
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!IopCompleteRequest+0x5eb:
fffff800`030df0bb 41f604247f      test    byte ptr [r12],7Fh ds:002b:00000000`00000200=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800030df0bb

STACK_TEXT:  
fffff880`03ca93a8 fffff800`030c91e9 : 00000000`0000003b 00000000`c0000005 fffff800`030df0bb fffff880`03ca9c70 : nt!KeBugCheckEx
fffff880`03ca93b0 fffff800`030c8b3c : 00000000`00000000 00000000`00000000 fffff800`032d31dc fffff800`030cef4c : nt!KiBugCheckDispatch+0x69
fffff880`03ca94f0 fffff800`030f54fd : fffff960`0030b314 fffff960`002d6580 fffff960`00020000 fffff880`03caa418 : nt!KiSystemServiceHandler+0x7c
fffff880`03ca9530 fffff800`030f42d5 : fffff800`03214788 fffff880`03ca95a8 fffff880`03caa418 fffff800`0304d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03ca9560 fffff800`03105361 : fffff880`03caa418 fffff880`03ca9c70 fffff880`00000000 fffffa80`0947ea50 : nt!RtlDispatchException+0x415
fffff880`03ca9c40 fffff800`030c92c2 : fffff880`03caa418 fffffa80`0b41b010 fffff880`03caa4c0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`03caa2e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

Followup: MachineOwner
---------
The above crash typically indicates graphics card problems. It may be related to the software I mentioned above. Proceed with the steps I laid out for the problematic software and let us know how the system responds.
My System SpecsSystem Spec
.


30 Apr 2012   #4

Windows 7 Ultimate x64
 
 

Many thanks for the reply
I have followed your steps and un-installed the troublesome programes. I unistalled the AMD Vision Engine Control Center and installed the device driver only, and updated to the latest drivers from the ASUS website.
However BSOD's are still happing and driving me mad. I've attached the latest dump info
My System SpecsSystem Spec
30 Apr 2012   #5

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
Not Available	PCI\VEN_1022&DEV_780B&SUBSYS_43851458&REV_13\3&2B8E0B4B&0&A0	The drivers for this device are not installed.
This appears to be an ATI driver. It may be the AODDriver that I recommended you remove (the driver that provides overclocking), so ignore this for now.


Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\GreenyLG\Windows_NT6_BSOD_jcgriff2_2\043012-25396-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032aa650
Debug session time: Mon Apr 30 13:09:29.319 2012 (UTC - 6:00)
System Uptime: 0 days 1:48:38.911
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000236510, cb2000004090186f, fffff68000236110}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000236510
Arg3: cb2000004090186f
Arg4: fffff68000236110

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  '

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000308ac56 to fffff800030e2c80

STACK_TEXT:  
fffff880`0a6fef18 fffff800`0308ac56 : 00000000`0000001a 00000000`00000403 fffff680`00236510 cb200000`4090186f : nt!KeBugCheckEx
fffff880`0a6fef20 fffff800`03114017 : 00000000`00000000 fffff680`00236ff8 fffffa80`0839db30 00000000`00080000 : nt! ?? ::FNODOBFM::`string'+0x3266c
fffff880`0a6ff0d0 fffff800`030cf4bf : fffffa80`00000000 00000000`46f3ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0a6ff290 fffff800`030e1f13 : ffffffff`ffffffff fffff8a0`0be5b428 fffff8a0`0be5b450 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0a6ff390 fffff800`030de4d0 : fffff880`03f614b2 fffff8a0`017b2860 fffffa80`0839db30 fffffa80`070499c0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a6ff528 fffff880`03f614b2 : fffff8a0`017b2860 fffffa80`0839db30 fffffa80`070499c0 fffff8a0`0be5b420 : nt!KiServiceLinkage
fffff880`0a6ff530 fffff880`03f4cb5a : fffff8a0`494e494d fffff8a0`0b69eab0 00000000`00000001 fffff880`048f573c : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0a6ff560 fffff880`03f47523 : fffffa80`082ed370 00000000`00000001 fffff8a0`017b2860 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0a6ff610 fffff880`03f2decc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0a6ff6e0 fffff880`03e6fccc : 00000000`00000000 fffff8a0`01090000 fffff8a0`01090000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0a6ff710 fffff880`03e6f65f : fffff8a0`01090000 fffff8a0`01091300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0a6ff800 fffff880`03e6f8e1 : fffff8a0`01090000 fffff8a0`01090000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0a6ff850 fffff880`03e7379c : fffff8a0`0be48800 fffff880`0a6ffca0 00000000`00000000 fffff880`03e3a3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0a6ff8a0 fffff880`03e75e57 : fffff8a0`01090000 fffff880`0a6ff9b0 fffffa80`0707ce01 fffff880`03e3b001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0a6ff930 fffff960`0026f642 : 00000000`fff65000 fffffa80`06f14830 00000000`00000020 00000000`752a6168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0a6ffbf0 fffff800`030e1f13 : fffffa80`06f14830 fffff880`0a6ffca0 00000000`fff65000 fffffa80`06c3e450 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0a6ffc20 00000000`752c141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`103fe7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752c141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`03f614b2 488b0e          mov     rcx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID:  X64_0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

Followup: MachineOwner
---------
The above crash implicates DirectX/your graphics card or the drivers.
  • Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

    Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
    1. Download the drivers you want for your display card(s)
    2. Click Start Menu
    3. Click Control Panel
    4. Click Uninstall a program
    5. For NVIDIA:
      • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
      • Restart your computer
      • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
      • If any remain of the above, uninstall one at a time
      • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
    6. For AMD:
      • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
      • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
        1. Click Start Menu
        2. Right Click My Computer/Computer
        3. Click Manage
        4. Click Device Manager from the list on the left
        5. Expand Display adapters
        6. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK

          Alternatively:
          1. Login as an adminstrative user
          2. Click Start Menu
          3. Click Control Panel
          4. Click Hardware and Sound
          5. Click Device Manager (the last link under Devices and Printers)
          6. Expand Display adapters
          7. Do the following for each adapter (in case you have multiple display cards)
            • Right click the adapter
            • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
            • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      • Restart your computer after uninstalling drivers for all display cards
      • Install the driver you selected for the display cards once Windows starts


Some of your logs indicate some hard disk errors.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.
My System SpecsSystem Spec
Reply

 BSOD ntoskrnl.exe 0x000000d1 HELP!! (Playing Crysis2)




Thread Tools



Similar help and support threads for2: BSOD ntoskrnl.exe 0x000000d1 HELP!! (Playing Crysis2)
Thread Forum
bsod when playing anything 0X000000d1 BSOD Help and Support
BSOD 5-10 Times a Day, 0x000000d1 ntoskrnl.exe? BSOD Help and Support
BSOD while playing LoL 0x000000d1 with log BSOD Help and Support
Bsod playing MWO 0x0000001a or 0x000000d1 and 0x0000003b BSOD Help and Support
BSOD while playing most games, error 0x000000d1 BSOD Help and Support
BSOD, tcpip.sys, ntoskrnl.exe, 0x000000D1, 0x0000003B BSOD Help and Support
ntoskrnl.exe BSOD 0x000000d1 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 03:46 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