BSOD stop 0x9f and 0x34

Kitefr · 19 Feb 2012

Hi,

Since i don't know what's that about and trying to find a solution, i found this website. So i need you help !

I brought a laptop 2 weeks ago and i got random BSOD 0x9f and 0x34. Two of each so far.

I collected all the data needed and zipped it !

Some more informations :
- Windows 7 Home Edition Prenium x64 and this is the original OS in this machine.
- If this help, the laptop is a Asus N53SM-SX117V 15,6 screen.
- It is a full retail version.

If you need more information, i will gladly provide them.

Thanks in advance for the help !

rowsi · 19 Feb 2012

I bought one ten days ago and had the same problem and could not start it, exchanged it with a new one on the 14/2 and had a BSOD today, but all is working. It is a problem with drivers or hardware, but after such a short time, surely best to chnage again....

Bienvenue, jai eu la meme chose avec deux asus et je me demande si je vais pas la rentree et acheter autre chose a la place.... desolee pour mon francais

writhziden · 19 Feb 2012

Code:


Loading Dump File [F:\Kingston\BSODDmpFiles\kitefr\Windows_NT6_BSOD_jcgriff2\021912-27658-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0320e000 PsLoadedModuleList = 0xfffff800`03453670
Debug session time: Sun Feb 19 07:44:34.531 2012 (GMT-7)
System Uptime: 0 days 3:57:37.926
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8012253060, fffff80000b9c3d8, fffffa8014ecd900}

Probably caused by : usbccgp.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8012253060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa8014ecd900, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8014ecd900

DEVICE_OBJECT: fffffa8012253060

DRIVER_OBJECT: fffffa80113611a0

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c0a

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff88005f40000 usbccgp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032f8cd2 to fffff8000328ac40

STACK_TEXT:  
fffff800`00b9c388 fffff800`032f8cd2 : 00000000`0000009f 00000000`00000003 fffffa80`12253060 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`032965fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c430 fffff800`03296496 : fffff800`03435f00 00000000`000df22b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0329637e : 00000021`3262fa66 fffff800`00b9cb18 00000000`000df22b fffff800`034037e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`03296167 : 00000007`1dda0bc1 00000007`000df22b 00000007`1dda0b0a 00000000`0000002b : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0328296a : fffff800`03400e80 fffff800`0340ecc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_usbccgp.sys

BUCKET_ID:  X64_0x9F_IMAGE_usbccgp.sys

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

Loading Dump File [F:\Kingston\BSODDmpFiles\kitefr\Windows_NT6_BSOD_jcgriff2\021812-19219-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03255000 PsLoadedModuleList = 0xfffff800`0349a670
Debug session time: Sat Feb 18 03:22:50.122 2012 (GMT-7)
System Uptime: 0 days 0:07:29.012
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {ab6, ffffffffc0000420, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29b31 )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000000ab6
Arg2: ffffffffc0000420
Arg3: 0000000000000000
Arg4: 0000000000000000

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


EXCEPTION_RECORD:  ffffffffc0000420 -- (.exr 0xffffffffc0000420)
Cannot read Exception record @ ffffffffc0000420

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x34

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000333c4e1 to fffff800032d1c40

STACK_TEXT:  
fffff880`03738968 fffff800`0333c4e1 : 00000000`00000034 00000000`00000ab6 ffffffff`c0000420 00000000`00000000 : nt!KeBugCheckEx
fffff880`03738970 fffff800`03316c1e : fffff880`033657f0 fffffa80`0db1fd40 fffffa80`0db1fe00 fffffa80`12f29590 : nt! ?? ::FNODOBFM::`string'+0x29b31
fffff880`037389b0 fffff800`033172fe : fffffa80`0db1fd40 fffffa80`0db1fd40 fffff880`03365180 fffffa80`0db1fe00 : nt!CcDeleteSharedCacheMap+0x36a
fffff880`03738a10 fffff800`03317938 : fffff880`00000000 fffff880`03738b18 fffffa80`0d253110 fffff800`034d38b8 : nt!CcWriteBehind+0x54e
fffff880`03738ac0 fffff800`032dc001 : fffffa80`0d0a73b0 fffff800`035c8901 fffff800`034d38c0 00000000`00000005 : nt!CcWorkerThread+0x1c8
fffff880`03738b70 fffff800`0356cfee : 00000000`00000000 fffffa80`0d133b60 00000000`00000080 fffffa80`0d082040 : nt!ExpWorkerThread+0x111
fffff880`03738c00 fffff800`032c35e6 : fffff880`03589180 fffffa80`0d133b60 fffff880`035940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03738c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+29b31
fffff800`0333c4e1 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+29b31

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+29b31

BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+29b31

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

Loading Dump File [F:\Kingston\BSODDmpFiles\kitefr\Windows_NT6_BSOD_jcgriff2\021412-20014-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03068000 PsLoadedModuleList = 0xfffff800`032ad670
Debug session time: Tue Feb 14 12:38:24.535 2012 (GMT-7)
System Uptime: 0 days 2:16:53.425
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800f918a10, fffff80000ba2748, fffffa8012e26a10}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800f918a10, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa8012e26a10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8012e26a10

DEVICE_OBJECT: fffffa8010346040

DRIVER_OBJECT: fffffa801021bd30

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e82d6a1

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff8800f4a0000 nvlddmkm

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003152cd2 to fffff800030e4c40

STACK_TEXT:  
fffff800`00ba26f8 fffff800`03152cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0f918a10 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`030f05fc : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00ba27a0 fffff800`030f0496 : fffff800`0328ff00 00000000`000808a2 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`030f037e : 00000013`1f954aab fffff800`00ba2e88 00000000`000808a2 fffff800`0325e6c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`030f0167 : fffff800`0325aec1 fffffa80`000808a2 00000000`00000000 00000000`000000a2 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`030e7765 : 00000000`00000000 fffffa80`0de20680 00000000`00000000 fffff880`04889588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`030e757c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`039088d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x9F_IMAGE_nvlddmkm.sys

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

USB related; a device would not enter a power state (either turn off or turn on) when the system requested that it do so. This can be due to a USB device plugged into the USB ports preventing them from entering a power state, or it could the ports themselves have protected themselves from a power surge.
Points to not having enough memory in the machine or there being a problem with the memory within the machine.
nVidia driver for the graphics card failed to change the power state of the graphics card (either turn it off or turn it on) when the system requested that it do so. This can be due to the driver needing to be updated, the driver being corrupted, or the card itself having problems.

Proceed through the following steps. Test stability after each step, and if the system crashes again, proceed to the next step.

If you are overclocking any hardware, please stop.
Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
For the USB crash, use the USB Driver - General Fix for Problems
For the USB crash, reset your BIOS hardware/software connections and the USB power setting with the following steps.
1. Shut down and turn off the computer.
2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds. This closes the circuit and ensures all power from components is drained to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory.
4. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall.
5. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back your results.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
For your nVidia graphics card related power state crash... Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
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
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. 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
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

Kitefr · 22 Feb 2012

Thanks a lot for the answer. It's seems i fixed the usb devices. No new BSoD so far.
But i still need to check the memory and i have 16 Go of memory so the problem is not having not enough.
And for the nvidia driver, mine seems to not exist currently.
I have a Nvidia Geforce GT 630M but can't find it on the nvidia website. So i will just wait for now.

Thank you very much anyway :)

writhziden · 22 Feb 2012

You will not find graphics drivers for a dedicated graphics card within a laptop through nVidia, unfortunately. The only reliable place to obtain graphics card drivers for a laptop is through the laptop manufacturer's support site for your model. Companies set the graphics cards up for different power management within laptops, so they are specially designed for the specific laptop model.

rowsi · 22 Feb 2012

use asus live update for the viseo driver, worked for me anyway.

Bonne chance

Kitefr · 22 Feb 2012

Thanks ^^
@rowsi : the asus live update don't find anything to update... how do i just ask for a detection on the video driver ?

rowsi · 22 Feb 2012

Kitefr said:

Thanks ^^
@rowsi : the asus live update don't find anything to update... how do i just ask for a detection on the video driver ?

I used "Driver sweeper" recommended from here to remove all traces of nvdia and then went to the ASUS site and downloaded, installed and no problems so far. Driver Sweeper was recommended from this site.

Kitefr · 22 Feb 2012

Well i done that but i can't reinstall it, the setup program keep saying that this is not the right one for my computer. But i downloaded it from asus website with the reference of my computer so now, i'm stuck... can't do nothing...

rowsi · 22 Feb 2012

Kitefr said:

Well i done that but i can't reinstall it, the setup program keep saying that this is not the right one for my computer. But i downloaded it from asus website with the reference of my computer so now, i'm stuck... can't do nothing...

A vrai dire je fait deux fois avant que ca marche, mais ca marche, courage

I had to do it twice before it worked, I am rather disapointed that after one week of ownership I have had to spend multiple hours on this computer, never had that before... This is my 5th laptop