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: Another BSOD while Idle thread...


02 Sep 2010   #1

Windows 7 Home Premium x64
 
 
Another BSOD while Idle thread...

Windows 7 Home Premium x64
Full version
new i7, corsair ram, evga p55 based mobo
install age, 1 day


it only happens when sitting idle....

i noticed my report said i don't have AV software, but i'm running comodo


thanks for any help.... these bsods while sitting idle suck

My System SpecsSystem Spec
.

02 Sep 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Bailx View Post
Windows 7 Home Premium x64
Full version
new i7, corsair ram, evga p55 based mobo
install age, 1 day


it only happens when sitting idle....

i noticed my report said i don't have AV software, but i'm running comodo


thanks for any help.... these bsods while sitting idle suck
These crashes have three contributing causes. They are memory exceptions caused by a driver. You have two drivers that are absolutely knnow to cause them


To fix this I would update the older drivers listed below. Pay special attention the the dazzer driver which is over two years old


Second you have some sort of virtual cd emulation software that uses sptd.sys It MUST be removed., Things like daemon tools, alcohol, etc use it.

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 when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


Then since they were all memory exceptions you should test you memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.




Let us know if you need help


Ken
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\090110-10250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02854000 PsLoadedModuleList = 0xfffff800`02a91e50
Debug session time: Wed Sep  1 18:36:17.584 2010 (GMT-4)
System Uptime: 0 days 0:03:47.569
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002bb79b2, fffff88003369a48, fffff880033692b0}

Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002bb79b2, The address that the exception occurred at
Arg3: fffff88003369a48, Exception Record Address
Arg4: fffff880033692b0, Context Record Address

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!CmpDelayDerefKCBWorker+d6
fffff800`02bb79b2 4038ae380b0000  cmp     byte ptr [rsi+0B38h],bpl

EXCEPTION_RECORD:  fffff88003369a48 -- (.exr 0xfffff88003369a48)
ExceptionAddress: fffff80002bb79b2 (nt!CmpDelayDerefKCBWorker+0x00000000000000d6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880033692b0 -- (.cxr 0xfffff880033692b0)
rax=fffffa80048f0bb0 rbx=0000000000000000 rcx=fffff8a0041c56a8
rdx=0000000000000baf rsi=fbfff8a000c9e010 rdi=fffff8a0041c55d0
rip=fffff80002bb79b2 rsp=fffff88003369c80 rbp=0000000000000001
 r8=fffff8a008bfcd78  r9=00000000384af7e5 r10=fffff8a0041c5130
r11=fffffa80048f0b60 r12=fffff80002ac9ee0 r13=fffff80002ac9f40
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!CmpDelayDerefKCBWorker+0xd6:
fffff800`02bb79b2 4038ae380b0000  cmp     byte ptr [rsi+0B38h],bpl ds:002b:fbfff8a0`00c9eb48=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afc0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!CmpDelayDerefKCBWorker+d6
fffff800`02bb79b2 4038ae380b0000  cmp     byte ptr [rsi+0B38h],bpl

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff800028d1961 to fffff80002bb79b2

STACK_TEXT:  
fffff880`03369c80 fffff800`028d1961 : fffff800`02bb78dc fffff800`02a695f8 fffffa80`048f0b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xd6
fffff880`03369cb0 fffff800`02b68c06 : 01cb49cb`efd762d0 fffffa80`048f0b60 00000000`00000080 fffffa80`048da040 : nt!ExpWorkerThread+0x111
fffff880`03369d40 fffff800`028a2c26 : fffff880`03186180 fffffa80`048f0b60 fffff880`031910c0 01cb49cb`efd9c52a : nt!PspSystemThreadStartup+0x5a
fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`03369970 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpDelayDerefKCBWorker+d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880033692b0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDelayDerefKCBWorker+d6

BUCKET_ID:  X64_0x7E_nt!CmpDelayDerefKCBWorker+d6

Followup: MachineOwner
---------
Old drivers needing updateing
Code:
dadder.sys        fffff880`04bf7000    fffff880`04bfa180    0x00003180    0x46b1a4cf    8/2/2007 05:33:03                        
adfs.SYS        fffff880`03de5000    fffff880`03dfd000    0x00018000    0x490f2b4e    11/3/2008 12:48:14                        
yk62x64.sys        fffff880`04292000    fffff880`042f5000    0x00063000    0x49a2ba83    2/23/2009 11:02:27                        
3wareDrv.sys        fffff880`00fbd000    fffff880`00fe0000    0x00023000    0x49c98979    3/24/2009 21:31:37                        
spldr.sys        fffff880`0168b000    fffff880`01693000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
spsys.sys        fffff880`06a00000    fffff880`06a71000    0x00071000    0x4a085e7a    5/11/2009 13:20:58                        
GEARAspiWDM.sys        fffff880`04200000    fffff880`0420d000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`0109d000    fffff880`010a8000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
cmudaxp.sys        fffff880`04402000    fffff880`045f4000    0x001f2000    0x4a2e4854    6/9/2009 07:32:36                        
PxHlpa64.sys        fffff880`00ff4000    fffff880`00fffe00    0x0000be00    0x4a416253    6/23/2009 19:16:35
My System SpecsSystem Spec
02 Sep 2010   #3

Windows 7 Home Premium x64
 
 

thanks for the quick reply.... i actually ran memtest yesterday and got no errors

man, daemon tools? no way... i use that for tons of stuff... i have a lot of automated scripts for that program that i use all the time...

dadder seems to be my mouse.... i was intentionally using old firmware & drivers for my razer mouse, because the newest ones had this terrible lag problem...

but i guess it's time to ditch that....

thanks for the help, i'll try some things and post back results in a few days
My System SpecsSystem Spec
.


Reply

 Another BSOD while Idle thread...




Thread Tools



Similar help and support threads for2: Another BSOD while Idle thread...
Thread Forum
BSOD - Crashes while computer idle/not idle (Unpredictable) BSOD Help and Support
Another BSOD thread BSOD Help and Support
Yet Another BSOD Thread BSOD Help and Support
Another BSOD 3rd Thread BSOD Help and Support
Another BSOD Thread, yay! BSOD Help and Support
Yet another BSOD thread BSOD Help and Support
Yet another BSOD thread. 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 10:06 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