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 0x000000c9 (0x000000000000023e, 0xfffff88001907360, 0xfffff98009c

04 Dec 2013   #1
xiamaiani

windows 7 ult X64
 
 
BSOD 0x000000c9 (0x000000000000023e, 0xfffff88001907360, 0xfffff98009c

Hello,
the last few days i got BSOD's and did some research then i found this site:
Crashes possibly bad memory? Win7Pro X64
I follow the verifier options and this was the error i got, i hope you can help me

Code:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea66d0
Debug session time: Wed Dec 4 12:07:50.264 2013 (UTC - 5:00)
System Uptime: 0 days 0:00:12.403
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88001907360, The address in the driver's code where the error was detected.
Arg3: fffff98009c96ee0, IRP address.
Arg4: 0000000000000000, Status code.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23e

FAULTING_IP: 
dtsoftbus01+1360
fffff880`01907360 4053 push rbx

FOLLOWUP_IP: 
dtsoftbus01+1360
fffff880`01907360 4053 push rbx

IRP_ADDRESS: fffff98009c96ee0

DEVICE_OBJECT: fffffa8009034060

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LOCK_ADDRESS: fffff80002edcbe0 -- (!locks fffff80002edcbe0)

Resource @ nt!PiEngineLock (0xfffff80002edcbe0) 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

PNP_TRIAGE: 
    Lock address : 0xfffff80002edcbe0
    Thread Count : 0
    Thread address: 0x0000000000000000
    Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff800031654ec to fffff80002cd8bc0

STACK_TEXT: 
fffff880`031e0778 fffff800`031654ec : 00000000`000000c9 00000000`0000023e fffff880`01907360 fffff980`09c96ee0 : nt!KeBugCheckEx
fffff880`031e0780 fffff800`0316f58a : fffff800`03163b00 fffff880`01907360 fffff980`09c96ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031e07c0 fffff800`0317045e : 00000000`0000023e 00000000`00000000 fffff980`09c96ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031e0810 fffff800`0317b82f : fffffa80`09505670 fffffa80`092dc720 fffffa80`092dc7d8 fffff880`0190b228 : nt!VfErrorReport6+0x6e
fffff880`031e08e0 fffff800`0317bc73 : fffffa80`092dc720 00000000`00000002 fffffa80`09034060 fffff880`01907430 : nt!IovpCallDriver2+0x13f
fffff880`031e0940 fffff800`03181d3e : fffff980`09c96ee0 fffff980`09c96ee0 00000000`00000002 fffffa80`09034060 : nt!VfAfterCallDriver+0x353
fffff880`031e0990 fffff880`00e6b617 : fffff880`00efad20 fffff880`031e0a60 00000000`00000025 fffffa80`092dc720 : nt!IovCallDriver+0x57e
fffff880`031e09f0 fffff880`00e6bec5 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`092f7a40 : Wdf01000!FxIoTarget::SubmitSync+0x24b
fffff880`031e0aa0 fffff880`01967e95 : fffffa80`00000020 fffffa80`092f7a40 fffffa80`092e47c0 fffffa80`092f58c0 : Wdf01000!imp_WdfRequestSend+0x2d1
fffff880`031e0b30 fffff880`019682f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`031e0cf0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`031e0b90 fffff880`01966f04 : 0000057f`f6d1cfd8 fffff880`031e0cf0 fffffa80`092f5910 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`031e0cc0 fffff880`01965825 : fffffa80`00000002 fffffa80`092e32d0 fffff880`0195d3b8 0000057f`f6d1cfd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`031e0d90 fffff880`00e994a8 : 00000000`00000000 00000000`00000010 00000000`0000000c fffff880`00efb0c0 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`031e0dd0 fffff880`00e85926 : fffffa80`092e3890 00000000`0000000c fffff880`00efb0c0 00000000`00000002 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`031e0e00 fffff880`00e8d463 : 00000000`00000000 00000000`00000000 fffff880`031e0fa0 fffff880`00efb0c0 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`031e0e70 fffff880`00e7b0f8 : 00000000`00000312 fffff880`031e0fa0 00000000`ffff7fff fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`031e0ea0 fffff880`00e7ada6 : fffff880`00efae80 fffffa80`092e3c98 fffffa80`092e3ae0 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`031e1000 fffff880`00e7b627 : 00000000`00000000 fffff880`031e10e0 fffffa80`092e3c80 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`031e1070 fffff880`00e931be : 00000000`00000000 00000000`00000501 00000000`00000501 fffff800`0316d1de : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`031e1110 fffff880`00e7d5d5 : 00000000`00000501 fffff880`031e11b0 00000000`00000500 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`031e1140 fffff880`00e77853 : fffffa80`092e3d48 fffffa80`092e3d50 fffffa80`092e3ae0 fffffa80`092e3d48 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c9
fffff880`031e11e0 fffff880`00e7ba01 : 00000000`00000000 fffff880`031e12c0 fffffa80`092e3d38 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3df
fffff880`031e1250 fffff880`00e8dd59 : 00000000`00000000 fffffa80`092e4d50 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
fffff880`031e12f0 fffff880`00e8cdf5 : 00000000`00000101 00000000`00000108 00000000`00000108 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`031e1330 fffff880`00e8cac6 : 00000000`00000002 fffffa80`092e3c08 fffffa80`092e3ae0 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
fffff880`031e13d0 fffff880`00e8c879 : 00000000`00000000 fffff880`031e14b0 fffffa80`092e3bf0 fffffa80`092e3ae0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`031e1440 fffff880`00e8db66 : 00000000`00000000 fffffa80`092e3ae0 fffffa80`092f1a10 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
fffff880`031e14e0 fffff880`00e675d7 : fffffa80`08af0880 fffff880`031e1560 00000000`00000000 fffffa80`094ef1c8 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
fffff880`031e1510 fffff880`00e6679a : fffff980`09c80e50 00000000`00000051 fffff980`09c80e50 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
fffff880`031e1570 fffff880`00e66866 : fffff980`09c80e50 00000000`00000002 fffffa80`092e4d50 fffffa80`092e4d50 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`031e15b0 fffff800`03181d26 : fffff980`09c80e50 00000000`00000002 fffffa80`092e4d50 fffffa80`092e4d50 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`031e15f0 fffff800`0309518e : fffff980`09c80e50 fffffa80`092f2870 fffffa80`092e4d50 fffffa80`092e62d0 : nt!IovCallDriver+0x566
fffff880`031e1650 fffff800`02dcf7ad : fffffa80`09034060 fffffa80`092f2870 fffff800`02dd8ed0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031e1690 fffff800`030a4506 : fffff800`02edc9a0 fffffa80`092e2830 fffffa80`092f2870 fffffa80`092e29d8 : nt!PnpStartDevice+0x11d
fffff880`031e1750 fffff800`030a47a4 : fffffa80`092e2830 fffffa80`06d6002a fffffa80`06d66380 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`031e17e0 fffff800`030c7eb6 : fffffa80`092e2830 fffffa80`06d66380 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`031e1810 fffff800`030c836c : fffff800`02eda500 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296
fffff880`031e1a80 fffff800`02ddb802 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`031e1ad0 fffff800`02ce2261 : fffff800`02ddb500 fffff800`02fcf101 fffffa80`06d4bb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`031e1b70 fffff800`02f752ea : 00000000`00000000 fffffa80`06d4bb50 00000000`00000080 fffffa80`06d26040 : nt!ExpWorkerThread+0x111
fffff880`031e1c00 fffff800`02cc98e6 : fffff880`02fe6180 fffffa80`06d4bb50 fffff880`02ff1040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031e1c40 00000000`00000000 : fffff880`031e2000 fffff880`031dc000 fffff880`031e0ba0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

SYMBOL_NAME: dtsoftbus01+1360

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME: dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 51c2adcb

FAILURE_BUCKET_ID: X64_0xc9_23e_dtsoftbus01+1360

BUCKET_ID: X64_0xc9_23e_dtsoftbus01+1360

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



My System SpecsSystem Spec
.
04 Dec 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi xiamaiani.

This crash dump indicates that Daemon Tools caused this BSOD with verifier on. From your post:
Code:
STACK_COMMAND:  .bugcheck ; kb
 
SYMBOL_NAME:  dtsoftbus01+1360
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: dtsoftbus01
 
IMAGE_NAME:  dtsoftbus01.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  51c2adcb
 
FAILURE_BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1360
 
BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1360
 
Followup: MachineOwner
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools 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.
Then Disable driver verifier and let the computer run normally. If the BSODs occur again, post it following the Blue Screen of Death (BSOD) Posting Instructions.
My System SpecsSystem Spec
04 Dec 2013   #3
Brink

64-bit Windows 10 Pro
 
 

Hello xiamaiani, and welcome to Seven Forums.

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by afterwards to further help.
My System SpecsSystem Spec
.

05 Dec 2013   #4
xiamaiani

windows 7 ult X64
 
 

hello and thank you for answering so fast ,
i uninstalled daemon tools but now i got a different BSOD,

Code:
Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e5d6d0
Debug session time: Thu Dec  5 13:38:41.307 2013 (UTC - 5:00)
System Uptime: 0 days 2:02:36.446
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1e_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8800305b788 -- (.exr 0xfffff8800305b788)
ExceptionAddress: fffff80002c9b0c5 (nt!KiSecondaryClockInterrupt+0x00000000000002b5)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8800305b830 -- (.trap 0xfffff8800305b830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002ff1040 rbx=0000000000000000 rcx=0000000000000000
rdx=0000192c00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c9b0c5 rsp=fffff8800305b9c0 rbp=fffff8800305ba40
 r8=0000000000002ec0  r9=0000000000000000 r10=0000000000009e50
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiSecondaryClockInterrupt+0x2b5:
fffff800`02c9b0c5 4c8b4dd0        mov     r9,qword ptr [rbp-30h] ss:0018:fffff880`0305ba10=000000024723f68a
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c875be to fffff80002c8fb90

STACK_TEXT:  
fffff880`0305a868 fffff800`02c875be : 00000000`00000000 fffffa80`08063050 fffff880`0305afe0 fffff800`02cbaa90 : nt!KeBugCheck
fffff880`0305a870 fffff800`02cba75d : fffff800`02e9e0ec fffff800`02ddca80 fffff800`02c1a000 fffff880`0305b788 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0305a8a0 fffff800`02cb9535 : fffff800`02ddf038 fffff880`0305a918 fffff880`0305b788 fffff800`02c1a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0305a8d0 fffff800`02cca4c1 : fffff880`0305b788 fffff880`0305afe0 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff880`0305afb0 fffff800`02c8f242 : fffff880`0305b788 00000000`00000000 fffff880`0305b830 fffff880`02fe6180 : nt!KiDispatchException+0x135
fffff880`0305b650 fffff800`02c8d39f : fffff880`0305b830 00000000`00000000 fffffa80`07f3a000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0305b830 fffff800`02c9b0c5 : 00000000`00000000 fffff880`0305ba40 fffff880`02fe6180 00000000`00000001 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0305b9c0 fffff880`03ecd7f2 : fffff800`02c98709 00000000`00381199 fffffa80`086f5258 fffff880`02ff1040 : nt!KiSecondaryClockInterrupt+0x2b5
fffff880`0305bb58 fffff800`02c98709 : 00000000`00381199 fffffa80`086f5258 fffff880`02ff1040 00000000`00000001 : amdppm!C1Halt+0x2
fffff880`0305bb60 fffff800`02c8789c : fffff880`02fe6180 fffff880`00000000 00000000`00000000 fffff880`11ddf770 : nt!PoIdle+0x52a
fffff880`0305bc40 00000000`00000000 : fffff880`0305c000 fffff880`03056000 fffff880`0305bc00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+2
fffff880`03ecd7f2 c3              ret

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  amdppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1e_0_amdppm!C1Halt+2

BUCKET_ID:  X64_0x1e_0_amdppm!C1Halt+2

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


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links

Show DivLoaded Module List

Show DivRaw Stack Contents

Show DivDump Header Information

Show DivStrings
is my AMD driver causing this BSOD?

thanks in advance,
Tim Smits
My System SpecsSystem Spec
06 Dec 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If you get a BSOD and you want to report it, you have to post it following the Blue Screen of Death (BSOD) Posting Instructions. No meaningful suggestion can be provided without checking the data.
My System SpecsSystem Spec
Reply

 BSOD 0x000000c9 (0x000000000000023e, 0xfffff88001907360, 0xfffff98009c




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD 0x000000C9 On Bootup
I've had my PC for two years, and had one issue with BSODs before, but that was related to an issue with my RAM clock rate. Now my PC BSODs on boot up with a 0x000000C9 error code, but no associated text description. I cannot boot the PC into safe mode to access the dump files either. I will attach...
BSOD Help and Support
BSOD error 0x000000c9
Hi all, Attached dump files zipped folder. I have been experiencing this BSOD 1 time, and the other BSOD (0x1000007E) 2 times. I am currently running on Windows 7 Professional, 64-bit. Any other relevant information I will be gladly able to provide, let me know. Kindly assist. Thank you...
BSOD Help and Support
Getting lots of BSOD errors(0x000000d6,0x000000c9 and other)
This all started happening last night, I would constantly get a prompt saying that some program has stopped responding and to close it. As soon as I close it, few minutes later it happens again. Only thing is that it was not really a program, it was just gibberish.exe. I even tried to look at...
BSOD Help and Support
BSOD Few times a day 0x000000c9 (dumps inside)
Hello all, First time posting here so let me know if I'm doing anything wrong. So I have been having BSOD pretty regularly after a recent erase and install of Windows 7. At first it started off my keyboard would stop responding and I would have to restart my computer. The thing about that...
BSOD Help and Support
BSOD volmgr.sys, error 0x000000C9
Hi all, Attached is the SF zipped folder. I have been experiencing BSODs. I am currently running on Windows 7 Professional, 32-bit. Any other relevant information I will be gladly able to provide, let me know. Kindly assist. Thank you all in advance.
BSOD Help and Support
BSOD on start up, cannot access safe mode, 0x000000c9
Hi, I have not made any software chages that im aware of last time i was on my laptop. However now when i turn it on as normal and once i get to the windows screen and the windows sign has appeared it waits a second and then i get the blue screen. Then when i reboot and try to start in safemode by...
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 09:34.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App