Blue Screen after sleep mode

mikey

New Member
#1
I am getting blue screens after I wake the computer out of sleep mode, it happens about 3-5 minutes after waking. It is a new custom build and it has been doing it since day one. I have took it back for warranty, but they couldn't find anything wrong and sent it back to me. My guess is they never used sleep mode.
The specs are
Intel core I7 920 cpu
Asus P6T SE motherboard
6 gb Kingston DDR3 ram
Nvidea Geforce 9800 video card
windows 7 64 bit os
850 watt power supply

Attached are some dump files
 


Attachments

#2
How old is your D-Link driver ?





CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not

received on a secondary processor in an
MP system within the allocated interval.

This indicates that the specified
processor is hung and not processing

interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt

time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of

the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:

CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: wirelesscm.exe

CURRENT_IRQL: d

STACK_TEXT:
fffff880`087d2fb8 fffff800`02c7a443 :

00000000`00000101 00000000`00000019

00000000`00000000 fffff880`02f64180 : nt!

KeBugCheckEx
fffff880`087d2fc0 fffff800`02cd65f7 :

00000000`00000000 fffff800`00000002

00000000`00002711 00000000`00000000 : nt!

?? ::FNODOBFM::`string'+0x4e3e
fffff880`087d3050 fffff800`02c1d895 :

fffff800`02c42460 fffff880`087d3200

fffff800`02c42460 fffff800`00000000 : nt!

KeUpdateSystemTime+0x377
fffff880`087d3150 fffff800`02cca3f3 :

00000000`4ecd2aa3 fffff800`02e46e80

00000002`00000019 fffff800`02cd3fef : hal!

HalpHpetClockInterrupt+0x8d
fffff880`087d3180 fffff800`02cdbe00 :

00000000`00000000 fffff880`00000001

00000000`00000000 fffff6fc`00000000 : nt!

KiInterruptDispatchNoLock+0x163
fffff880`087d3310 fffff800`02ce6061 :

fffff900`c2487000 00000000`00000002

00000000`00000001 fffff800`02d27da0 : nt!

KeFlushMultipleRangeTb+0x260
fffff880`087d33e0 fffff800`02cf90fb :

00000000`00000002 fffff880`087d3540

fffff900`c2487000 00000000`00000045 : nt!

MiFlushTbAsNeeded+0x1d1
fffff880`087d34f0 fffff800`02dfdceb :

00000000`00001490 00000000`00001490

00000000`00000021 00000000`00000001 : nt!

MiAllocatePagedPoolPages+0x4bb
fffff880`087d3610 fffff800`02ce0860 :

00000000`00001490 fffff880`05b63cc0

00000000`00000021 fffff900`c1ec6cd0 : nt!

MiAllocatePoolPages+0x8e2
fffff880`087d3760 fffff800`02e00bfe :

00000000`00000000 fffff900`c2487000

00000000`00000020 fffff880`05b63cc0 : nt!

ExpAllocateBigPool+0xb0
fffff880`087d3850 fffff960`001228ed :

00000000`00000000 00000000`00000000

00000000`00000000 00000000`00000000 : nt!

ExAllocatePoolWithTag+0x82e
fffff880`087d3940 fffff960`00123e0f :

fffff880`087d3a00 fffff880`087d3ae0

00000000`00000000 00000000`00000001 :

win32k!AllocateObject+0xdd
fffff880`087d3980 fffff960`000fb48c :

fffff900`00000000 00000000`00000000

00000000`00000000 00000000`00000000 :

win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`087d3a70 fffff960`000fb006 :

00000011`00000045 00000000`00000011

00000000`01080030 00000000`00000045 :

win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`087d3b40 fffff800`02ccd153 :

fffffa80`0874ca30 fffff880`087d3ca0

00000000`00000000 fffff900`c00bf010 :

win32k!GreCreateCompatibleBitmap+0x26e
fffff880`087d3c20 00000000`73bb2dd9 :

00000000`00000000 00000000`00000000

00000000`00000000 00000000`00000000 : nt!

KiSystemServiceCopyEnd+0x13
00000000`0253f0f8 00000000`00000000 :

00000000`00000000 00000000`00000000

00000000`00000000 00000000`00000000 :

0x73bb2dd9


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID:

X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_

INCONCLUSIVE

BUCKET_ID:

X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_

INCONCLUSIVE


---------

 


mikey

New Member
#3
I am not using a d link
 


mikey

New Member
#4
Did you mean the wireless internet adapter D-Link.
 


#5
Most likely I did:

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


BUGCHECK_STR:

CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wirelesscm.exe
 


mikey

New Member
#6
I'm using an Atheros wireless device and the driver is up to date.
 


Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.