BSOD at random on a regular basis

smokedmike · 24 Mar 2012

Hi guys! I've done a little research into my computer and other people who've purchased the same model and also similar errors to mine. I've tried a number of different things and I just cannot figure it out myself so I figured I'd come to the experts. :)

Completely random, no one program or action causes it. I've tried switching pretty much every program I use on a regular basis (one at a time) to something else just to test if that may be the cause. Like.. Firefox to Chrome, Flash FXP to FileZilla etc. etc...

Anyway, I get the BSOD and have to turn my monitor off and pull the power cord from my tower to get the computer running again and it's really a pain! It doesn't happen every day but it seems to happen a lot more than I'd like to deal with.

Attaching a zip with the requested information in it. If you can offer any help I'd give you a big e-hug.

Posting the error report as well, not sure if the program included it in the zip I'm attaching, but just in case it didn't!

Thanks for your time~!

-=System Specs=-
System Manufacturer/Model Number
HP Pavilion Magnesium Grey Edition p6540yPC
OS
Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
CPU
AMD Phenom(tm) II X4 830 Processor
Motherboard
FOXCONN 2A92
Memory
8.00 GB
Graphics Card(s)
ATI Radeon HD 4200
Sound Card
Realtek High Definition Audio
Screen Resolution
1600 x 900 x 32 bits (4294967296 colors) @ 60 Hz
Hard Drives
(1) Seagate ST31000528AS SCSI Disk Device (2) Generic- Compact Flash USB Device (3) Generic- MS/MS-Pro USB Device (4) Generic- SD/MMC USB Device (5) Generic- SM/xD-Picture USB Device

-=Report=-
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFF88002FD5180
BCP4: 0000000000000003
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\032412-40248-01.dmp
C:\Users\Mike\AppData\Local\Temp\WER-540949-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

writhziden · 24 Mar 2012

Security Software (this is just to check that you have security software and it is working properly; nothing needs to be done with this at this time):

Code:

avgam.exe	c:\program files (x86)\avg\avg10\avgam.exe	2912	8	200	1380	3/24/2012 10:30 AM	10.0.0.1295	732.84 KB (750,432 bytes)	2/8/2011 4:32 AM
avgcsrva.exe	c:\program files (x86)\avg\avg10\avgcsrva.exe	3936	8	200	1380	3/24/2012 10:30 AM	10.0.0.1355	506.84 KB (519,008 bytes)	3/28/2011 3:00 AM
avgcsrva.exe	c:\program files (x86)\avg\avg10\avgcsrva.exe	4572	8	200	1380	3/24/2012 10:39 AM	10.0.0.1355	506.84 KB (519,008 bytes)	3/28/2011 3:00 AM
avgemca.exe	c:\program files (x86)\avg\avg10\avgemca.exe	2988	8	200	1380	3/24/2012 10:30 AM	10.0.0.1352	1.61 MB (1,687,904 bytes)	3/16/2011 4:05 PM
avgfws.exe	c:\program files (x86)\avg\avg10\avgfws.exe	1824	8	200	1380	3/24/2012 10:30 AM	10.0.0.1350	2.58 MB (2,708,024 bytes)	3/9/2011 6:24 PM
avgnsa.exe	c:\program files (x86)\avg\avg10\avgnsa.exe	2936	8	200	1380	3/24/2012 10:30 AM	10.0.0.1409	1.73 MB (1,817,440 bytes)	9/9/2011 3:10 AM
avgtray.exe	c:\program files (x86)\avg\avg10\avgtray.exe	4216	8	200	1380	3/24/2012 10:38 AM	10.0.0.1420	2.23 MB (2,339,168 bytes)	1/17/2012 8:03 PM
avgwdsvc.exe	c:\program files (x86)\avg\avg10\avgwdsvc.exe	1892	8	200	1380	3/24/2012 10:30 AM	10.0.0.1295	263.20 KB (269,520 bytes)	2/8/2011 4:33 AM
avgidsagent.exe	c:\program files (x86)\avg\avg10\identity protection\agent\bin\avgidsagent.exe	2496	8	200	1380	3/24/2012 10:30 AM	10.1.0.1424	7.05 MB (7,391,072 bytes)	1/31/2012 3:02 PM
avgidsmonitor.exe	c:\program files (x86)\avg\avg10\identity protection\agent\bin\avgidsmonitor.exe	4820	8	200	1380	3/24/2012 10:38 AM	10.1.0.1297	1.10 MB (1,148,256 bytes)	2/10/2011 6:55 AM

Possible out of date drivers:

Code:

ahcix64s	fffff880`01600000	fffff880`01650000	Tue Mar 17 00:38:19 2009 (49bf455b)	00038ade		ahcix64s.sys
dump_ahcix64s	fffff880`0993a000	fffff880`0998a000	Tue Mar 17 00:38:19 2009 (49bf455b)	00038ade		dump_ahcix64s.sys

ahcix64s.sys
dump_ahcix64s.sys
These are for your RAID controller and should be updated.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\smokedmike\Windows_NT6_BSOD_jcgriff2\032412-40248-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c57650
Debug session time: Sat Mar 24 08:28:27.878 2012 (UTC - 6:00)
System Uptime: 0 days 0:49:15.096
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002fd5180, 3}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd5180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`009a9768 fffff800`02ae6b39 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd5180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`02a99907 : fffff800`00000000 fffff800`00000003 00000000`00002710 00000000`00000011 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`009a9800 fffff800`03005895 : fffff800`0302b460 fffff880`009a99b0 fffff800`0302b460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`02a8c273 : 00000000`7bd1217d fffff800`02c04e80 fffff800`02c04e80 fffffa80`07a53060 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`02ac577d : fffff800`02c04e80 fffffa80`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`02a94c1c : 00000000`00000000 fffff880`009a9bf8 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x79
fffff880`009a9b00 fffff800`02a56819 : 00000000`000000a2 00000000`00000000 fffffa80`0339efd0 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`02a57067 : 00000000`00113400 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`02d29f7a : fffffa80`0670d5b0 00000000`00000080 fffffa80`0670db30 fffff800`02a809b9 : nt!MmZeroPageThread+0x83a
fffff880`009a9d40 fffff800`02a809c6 : fffff800`02c04e80 fffffa80`0670d5b0 fffff800`02c12cc0 3a413b04`8a411474 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

Start with STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg and let us know if you need any additional help after going through the steps in that thread.

ChrisKlein · 05 Jun 2012

BSOD are often, if not mostly, related to Timeout Detection and Recovery issues.
Very annoying and a known issue since Win Vista yet Nvidia,Ati and Microsoft failed completely to adress this issue to solve it once and for all.
This article sheds some light on the thing.
Timeout Detection and Recovery (TDR)

In short version: Graphics driver has to sent a ping every so seconds to OS. If it fails for whatever reason the OS shuts down to prevent damage to OS cause it thinks a critical error occured.