
Quote: Originally Posted by
pluekiller
Sorry I'm not sure where my attachment went...
These were Related to
JME.sys NDIS 5.x Driver from JMicron Technology Corp..
I would remove it.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051911-21465-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`03763500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02017000 PsLoadedModuleList = 0xfffff800`0225c650
Debug session time: Wed May 18 23:53:46.826 2011 (GMT-4)
System Uptime: 0 days 13:07:56.716
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8004d1da10, fffff80003763518, fffffa800d66bc10}
*** WARNING: Unable to verify timestamp for JME.sys
*** ERROR: Module load completed but symbols could not be loaded for JME.sys
Probably caused by : JME.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: fffffa8004d1da10, Physical Device Object of the stack
Arg3: fffff80003763518, Functional Device Object of the stack
Arg4: fffffa800d66bc10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800d66bc10
DEVICE_OBJECT: fffffa80073e3050
DRIVER_OBJECT: fffffa80071037e0
IMAGE_NAME: JME.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b85edfd
MODULE_NAME: JME
FAULTING_MODULE: fffff880036e0000 JME
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800021039c2 to fffff80002096d00
STACK_TEXT:
fffff800`037634c8 fffff800`021039c2 : 00000000`0000009f 00000000`00000003 fffffa80`04d1da10 fffff800`03763518 : nt!KeBugCheckEx
fffff800`037634d0 fffff800`020a2652 : fffff800`03763600 fffff800`03763600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`03763570 fffff800`020a24f6 : fffffa80`0bed7640 fffffa80`0bed7640 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`037635e0 fffff800`020a23de : 0000006e`131e7072 fffff800`03763c58 00000000`002e3e0b fffff800`0220c3e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`03763c30 fffff800`020a21c7 : 00000019`bc072cc2 00000019`002e3e0b 00000019`bc072cd0 00000000`0000000b : nt!KiTimerExpiration+0x1be
fffff800`03763cd0 fffff800`0208ea2a : fffff800`02209e80 fffff800`02217cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`03763d80 00000000`00000000 : fffff800`03764000 fffff800`0375e000 fffff800`03763d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_JME.sys
BUCKET_ID: X64_0x9F_IMAGE_JME.sys
Followup: MachineOwner
---------
ALSO :::::Important
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller
DuplexSecure - Downloads
when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.
MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor