09-27-2008
|
|
|
|
Re: BSOD 101 Minidump
Hi,
Difficult to tell, as that is an unusual error. Best guess is that there is
some malware on the system interfering with proper operation of the explorer
shell. I'd do some formal scanning from safe mode, or better yet, a bootable
'nix or bartpe disk.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
"fuji_man" <fuji_man.3g9qgh@no-mx.forums.vistaheads.com> wrote in message
news:fuji_man.3g9qgh@no-mx.forums.vistaheads.com...
>
> I have try to read my minidump and fix my problem
>
> I started to see random 101 BSOD in the last few days.... nothing been
> added to the system (software) nor any hardware change... so I don't
> know what is the issues.
>
> Attached is my minidump, could someone tell me how to fix it?
>
> *********************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *********************************************
>
> 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: 00000031, Clock interrupt time out interval in nominal clock
> ticks.
> Arg2: 00000000, 0.
> Arg3: 803cd120, The PRCB address of the hung processor.
> Arg4: 00000001, 0.
>
> Debugging Details:
> ------------------
> BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> PROCESS_NAME: explorer.exe
>
> CURRENT_IRQL: 1c
>
> STACK_TEXT:
> 8039dac4 82708321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
> 8039daf8 8270802d 87405a1b 000000d1 8039dbb8 nt!KeUpdateRunTime+0xd5
> 8039daf8 82707cc0 87405a1b 000000d1 8039dbb8
> nt!KeUpdateSystemTime+0xed
> 8039db84 82656671 0000000e 82656712 806a1982 nt!KiIpiSendPacket+0xac
> 8039dbb8 806a1b3e 806a1982 8039dbd0 00040000 nt!KeIpiGenericCall+0x6e
>
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 8039dc08 806a226a 0000001f 806a184e 8039dc2c sptd+0x14b3e
> 8039dc38 8069c5e3 01000001 8f7dc238 8fe764a8 sptd+0x1526a
> 8039dc50 8069df6d 00000103 8f71e310 8691c190 sptd+0xf5e3
> 8039dc7c 806a08c4 8f7dc138 8039dcd4 8069d8ec sptd+0x10f6d
> 8039dcec 8270c053 8feb3030 8f7dc138 8f7dc138 sptd+0x138c4
> 8039dd04 8d854d78 8039dd3c 8d855082 8f7033d8 nt!IofCallDriver+0x63
> 8039dd0c 8d855082 8f7033d8 00000003 8f7033d8 ElbyCDFL+0xd78
> 8039dd3c 8270c053 8f7033d8 8f7dc138 8f71e310 ElbyCDFL+0x1082
> 8039dd54 8d85c3d8 8f71e310 8039dd84 8d85d37d nt!IofCallDriver+0x63
> 8039dd60 8d85d37d 8f7013f8 8f7dc138 833851f4 cdrbsdrv+0x13d8
> 8039dd84 8270c053 8f7013f8 8f7dc138 8f7dc138 cdrbsdrv+0x237d
> 8039dd9c 83378264 8feb4b70 8f71e2f0 8feb4ab8 nt!IofCallDriver+0x63
> 8039ddb0 8337845d 8feb4b70 8f71e308 00000000
> CLASSPNP!ClasspSendMediaStateIrp+0x2ec
> 8039ddc8 833782af 8feb4b70 8801410c 82784cc0
> CLASSPNP!ClassCheckMediaState+0x54
> 8039dde8 8268a598 8feb4ab8 00000000 8039de40
> CLASSPNP!ClasspTimerTick+0x41
> 8039de08 82706d00 82784ca0 02784c44 a7dfb701 nt!IopTimerDispatch+0x49
> 8039df28 827068c0 8039df70 82748902 8039df78
> nt!KiTimerListExpire+0x367
> 8039df88 82706483 00000000 00000000 004f9c07
> nt!KiTimerExpiration+0x22a
> 8039dff4 827049f5 a6bbad10 00000000 00000000 nt!KiRetireDpcList+0xba
> 8039dff8 a6bbad10 00000000 00000000 00000000
> nt!KiDispatchInterrupt+0x45
> 827049f5 00000000 0000001b 00c7850f bb830000 0xa6bbad10
>
> 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: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE
>
> BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE
>
> Followup: MachineOwner
> ---------
>
>
> --
> fuji_man
> Posted via http://www.vistaheads.com
>
|
Linear Mode
