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 Stop 0x000000F9

19 May 2012   #1

Windows 7 Pro x64
BSOD Stop 0x000000F9

I was having issues on my computer so I reinstalled my OS on my SSD. Installed all the required drivers but just had another BSOD. I tried putting the computer to sleep, returned 10 minutes later to see that it restarted due to this BSOD. It looks like it might have to do with the cdrom because I also noticed that it fails to start sometimes. I wanted to check with the experts first before I go ahead and replace it.

Here's the Debugger Dump File check:

Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [E:\Users\Nathan\Desktop\051912-44085-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`03b04c32?
Symbol search path is:
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03049670
Debug session time: Sat May 19 20:17:13.062 2012 (UTC - 4:00)
System Uptime: 0 days 7:22:42.420
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
TRIAGER: Could not open triage file : F:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : F:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8009d6f660, fffff80000b9c510}

Implicit thread is now fffffa80`09d6f660
TRIAGER: Could not open triage file : F:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : cdrom.sys ( cdrom!DeviceSendRequestSynchronously+c9 )

Followup: MachineOwner

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

A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8009d6f660, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510, nt!TRIAGE_9F_PNP on Win7

Debugging Details:

Implicit thread is now fffffa80`09d6f660
TRIAGER: Could not open triage file : F:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2


FAULTING_THREAD:  fffffa8009d6f660






LOCK_ADDRESS:  fffff8000307fb80 -- (!locks fffff8000307fb80)

Resource @ nt!PiEngineLock (0xfffff8000307fb80)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

	Lock address  : 0xfffff8000307fb80
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002e79c12 to fffff80002e8708a

fffff880`033bca10 fffff800`02e79c12 : fffffa80`09d6f660 fffffa80`09d6f660 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`033bcb50 fffff800`02e8af9f : fffff880`033bcf40 fffff880`01107e16 00000000`00000000 fffffa80`0b2e3620 : nt!KiCommitThreadWait+0x1d2
fffff880`033bcbe0 fffff880`00e9c13a : fffffa80`0c551000 fffff880`00000000 fffffa80`0ca99600 fffffa80`09d18100 : nt!KeWaitForSingleObject+0x19f
fffff880`033bcc80 fffff880`00eb159f : fffffa80`0e9f1da0 00000000`00000000 fffff880`00000000 fffff880`02f5a5d5 : Wdf01000!FxIoTarget::SubmitSync+0x2c2
fffff880`033bcd30 fffff880`02f6ee95 : fffffa80`00000020 fffffa80`0e9f1da0 fffffa80`0ca99640 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`033bcd80 fffff880`02f6f2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`033bcf40 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`033bcde0 fffff880`02f6df04 : 0000057f`f1a8fe48 fffff880`033bcf40 fffffa80`0cf6cdb0 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`033bcf10 fffff880`02f6c825 : fffffa80`00000001 fffffa80`0e570520 fffff880`02f643b8 0000057f`f1a8fe48 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`033bcfe0 fffff880`00f069d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00f0f620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`033bd020 fffff880`00f0694e : fffffa80`0d9da180 00000000`0000000c fffff880`00f0f620 fffff880`00f0f600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`033bd050 fffff880`00efab9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f0f620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`033bd0c0 fffff880`00efa6eb : 00000000`00000312 00000000`00000000 fffff880`00f0f600 ffffdfc5`5e71f740 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`033bd0f0 fffff880`00efa38e : fffffa80`0e9708d0 00000000`00000040 fffff880`00f0f3e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`033bd220 fffff880`00efa06c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`0e9708d0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`033bd290 fffff880`00f07b5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`033bd320 fffff880`00f07abb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`02e94f7c : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`033bd350 fffff880`00f03950 : fffffa80`0e9708d0 00000000`00000001 00000000`00000000 fffff880`00f0bff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`033bd3d0 fffff880`00f03372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`0d9c8130 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`033bd440 fffff880`00effa45 : 00000000`00000000 fffffa80`0d9c8130 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`033bd4d0 fffff880`00eff841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`02e3da00 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`033bd510 fffff880`00eff4fe : fffffa80`0e9708d0 fffff880`033bd640 00000000`00000004 fffff880`00f0e390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`033bd580 fffff880`00eff201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0e9708d0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`033bd5f0 fffff880`00ef6d9c : 00000000`00000000 fffffa80`0e9708d0 fffff880`033bd8e0 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`033bd680 fffff880`00ef5dd6 : fffffa80`0b11be70 fffff880`033bd8e0 00000000`00000000 fffffa80`0e9708d0 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`033bd6b0 fffff880`00ec5245 : fffffa80`0dd62010 fffffa80`0dd62010 fffffa80`0d9c8130 fffff800`02f7b510 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`033bd720 fffff880`00ec514b : 00000000`00000003 fffffa80`0dd62010 fffff880`033bd8e0 fffffa80`0d9c8130 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`033bd750 fffff800`0323a02e : fffffa80`0dd62010 fffff880`033bd8e0 fffffa80`0d9c8130 fffff880`009ec180 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`033bd790 fffff800`02f71ead : fffffa80`0c551050 fffff880`033bd8e0 fffff800`02f7b510 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`033bd7d0 fffff800`032494c7 : 00000000`ffffffff fffffa80`0e1bd490 fffffa80`0e1bd490 fffffa80`0e1bd638 : nt!PnpStartDevice+0x11d
fffff880`033bd890 fffff800`03249614 : fffffa80`0e1bd490 fffffa80`0e1b004a fffffa80`0e1bd490 00000000`00000001 : nt!PnpStartDeviceNode+0x2a7
fffff880`033bd920 fffff800`0326cd46 : fffffa80`0e1bd490 fffffa80`0e1bd490 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`033bd950 fffff800`0326d137 : fffffa80`0e1bd490 00000000`00000000 00000000`00000001 fffff800`030e95d4 : nt!PipProcessDevNodeTree+0x296
fffff880`033bdbc0 fffff800`02f7df03 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiRestartDevice+0xc7
fffff880`033bdc10 fffff800`02e8d851 : fffff800`02f7dbf0 fffff800`03176601 fffffa80`09d6f600 00000000`00000000 : nt!PnpDeviceActionWorker+0x313
fffff880`033bdcb0 fffff800`0311ae6a : 00000000`00000000 fffffa80`09d6f660 00000000`00000080 fffffa80`09d47040 : nt!ExpWorkerThread+0x111
fffff880`033bdd40 fffff800`02e74f06 : fffff880`03164180 fffffa80`09d6f660 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdd80 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bcd90 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  .thread 0xfffffa8009d6f660 ; kb

fffff880`02f6ee95 488b0da490ffff  mov     rcx,qword ptr [cdrom!WdfDriverGlobals (fffff880`02f67f40)]


SYMBOL_NAME:  cdrom!DeviceSendRequestSynchronously+c9

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  cdrom.sys


FAILURE_BUCKET_ID:  X64_0x9F_4_cdrom!DeviceSendRequestSynchronously+c9

BUCKET_ID:  X64_0x9F_4_cdrom!DeviceSendRequestSynchronously+c9

Followup: MachineOwner
Attached is the actual Dump File.
Thank you!

My System SpecsSystem Spec
19 May 2012   #2

Win 8 Release candidate 8400

It is related to a driver timing out and yes it is on the CDROM, perhaps hardware not a driver. Run a system file check to verify the OS file

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
My System SpecsSystem Spec

 BSOD Stop 0x000000F9

Thread Tools

Similar help and support threads
Thread Forum
BSOD random 0x000000f9
uploading my dmp file.. pls help this BSOD really bugs me thanks..
BSOD Help and Support
BSOD randomly STOP: 0x0000003B & STOP: 0X00000024
Hello i have had 2 BSOD's or more recently. I dont know why, i only saw 2 of them, but ive had around 3 - 4, the other 1 - 2 were seen by family members but they just turned the pc off and back on... anyhow here are some pictures ...
BSOD Help and Support
BSOD STOP: 0x3B atikmdag.sys/STOP: 0x7E dxgmms1.sys
Guys I'm at a loss I'm getting BSOD's all the time I really don't know what to do with it, and I'm not computer heavy so. If someone here could help me that would be appreciated. I've included a Dxdiag file with the rest.
BSOD Help and Support
BSOD stop 0x000000F9 again
Hello, I just had another BSOD for the first time in a long time... I'm surprised to see that it's the same error (STOP 0x000000F9) as before and I did the exact same thing that solved it before. I just want to make sure that there isn't anything else wrong. My most recent hardware upgrade...
BSOD Help and Support
BSOD stop 0x000000F9
Hello everybody, Thread title supposed to be 0x0000009F (not F9) I'm having a BSOD after installing new hardware to my computer, but I cannot figure out what's exactly wrong. I recently just bought two new WD hard drives to replace two of my old ones. I used Acronis to clone both hard...
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 16:13.
Twitter Facebook Google+