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: BOSD when doing nothing


30 Jan 2012   #1

windows 7 home 64 bit
 
 
BOSD when doing nothing

Hello forum

I built my system 4 months a go since then i'v been getting BSOD for no real reason most of the time whilst on the net or doing nothing. All so the system has been frezzing resulting in me turning of at the mains.

Things i have done are:

Run memtest86 for 5 passed
Prime95 for 30 hours no fails
Disassembled and checked everthing
Updated all drivers

System specs

Win 7 home premium 64-bit
I5 2500k
ASrock Z68 Extreme 4
Corsair XMS3 4GB
OCZ Modxstream pro 500w
Samsung spinpoint F3 1TB
Wester digital caviar blue 500gb

Any help would be much appreciated


My System SpecsSystem Spec
.

30 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:

Loading Dump File [K:\BSODDmpFiles\peteski29\Windows_NT6_BSOD_jcgriff2\013012-17425-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03057670
Debug session time: Mon Jan 30 11:48:18.246 2012 (GMT-7)
System Uptime: 0 days 0:34:38.448
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009ea180, 1}

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: fffff880009ea180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  ConduitHelper.

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0963ef08 fffff800`02ee68c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ea180 : nt!KeBugCheckEx
fffff880`0963ef10 fffff800`02e99497 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff880`0567459c : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0963efa0 fffff800`03405895 : fffff800`0342b460 fffff880`0963f150 fffff800`0342b460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0963f0a0 fffff800`02e8b173 : 00000000`6bc4af8a fffff800`03004e80 fffff800`03004e80 fffff780`00000320 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0963f0d0 fffff800`02ec5327 : fffff800`03004e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0963f260 fffff800`02ec4289 : 00000000`00000000 00000000`00000001 fffff880`009ea180 fffffa80`03cc95b0 : nt!KxFlushEntireTb+0x93
fffff880`0963f2a0 fffff800`02ee8820 : 00000000`00000001 fffff6fc`8060f318 00000000`00000001 ffffffff`ffffffff : nt!KeFlushTb+0x119
fffff880`0963f320 fffff800`02e9f4ff : fffff6fc`8060f318 fffff880`0963f3c0 fffff900`00000001 fffff880`03c44c00 : nt! ?? ::FNODOBFM::`string'+0xae02
fffff880`0963f360 fffff800`02eac75e : 00000000`00000001 fffff900`c1e63000 fffff880`0963f6c0 fffff6fc`8060f318 : nt!MiResolveDemandZeroFault+0x1ff
fffff880`0963f450 fffff800`02e9c9db : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x8ce
fffff880`0963f560 fffff800`02e8cd6e : 00000000`00000001 fffff900`c1e63000 00000000`00000000 fffff880`03c45e00 : nt!MmAccessFault+0xe1b
fffff880`0963f6c0 fffff800`02fbd406 : fffff880`03c45e00 00000000`00000067 00000000`00000021 fffff960`0017cece : nt!KiPageFault+0x16e
fffff880`0963f850 fffff960`00125978 : fffff900`00000000 00000000`00000000 00000000`6c777355 00000000`00000000 : nt!ExAllocatePoolWithTag+0x326
fffff880`0963f940 fffff960`0013ea62 : fffff900`c23374f0 fffff900`00000000 00000000`00000000 fffff900`c2337b18 : win32k!InternalRebuildHwndListForIMEClass+0x38
fffff880`0963f9b0 fffff960`00125689 : 00000000`00000000 fffff880`0963fb60 00000000`00000000 00000000`0298fd20 : win32k!BuildHwndList+0xb2
fffff880`0963f9e0 fffff800`02e8ded3 : fffffa80`0986ab60 00000000`00000000 00000000`0298e328 fffff880`0963fa88 : win32k!NtUserBuildHwndList+0x19d
fffff880`0963fa70 00000000`733eff9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0298e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x733eff9a


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
---------
See STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg for information on this error and how to determine the root cause. If you need further help. let us know.
My System SpecsSystem Spec
31 Jan 2012   #3

windows 7 home 64 bit
 
 

Thanks writhziden for your reply. I'v pretty much done all the things in the link apart from replacing parts (not a option) and i'v just updated the BIOS . So fingers crossed all will be good. Thanks agin and i'll let you know how it goes
My System SpecsSystem Spec
.


31 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Alright, if you have any more problems, list in a post what you were able to do, and then we can provide more troubleshooting steps. Best wishes your system is now stable.
My System SpecsSystem Spec
02 Feb 2012   #5

windows 7 home 64 bit
 
 
Still happening

Hi there writhziden happend again today. It seems to me all the BSOD'S run around the ntoskrnl.exe+7cc40 driver.
Any help is much appreciated


My System SpecsSystem Spec
02 Feb 2012   #6

Windows 7 Home Premium 64 Bit
 
 

ntoskrnl.exe is a system file, and is often blamed due to it being in use much of the time by the system and the system being unable to determine the actual cause of the crash.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\Kingston\BSODDmpFiles\peteski29\Windows_NT6_BSOD_jcgriff2\020212-16692-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`0308e670
Debug session time: Thu Feb  2 11:21:05.748 2012 (GMT-7)
System Uptime: 0 days 1:33:40.575
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f65180, 2}

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: fffff88002f65180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`07ed7e38 fffff800`02f1d8c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
fffff880`07ed7e40 fffff800`02ed0497 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`07ed7ed0 fffff800`02e0a895 : fffff800`02e30460 fffff880`07ed8080 fffff800`02e30460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`07ed7fd0 fffff800`02ec2173 : 00000000`443bb1c5 fffff800`0303be80 fffff800`02e30460 fffff880`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`07ed8000 fffff800`02efc313 : fffff800`0303be80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`07ed8190 fffff800`02efb289 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000003 : nt!KxFlushEntireTb+0x7f
fffff880`07ed81d0 fffff800`02f1f820 : 00000000`00000002 fffff680`0013e5b0 00000000`00000001 00000000`00017874 : nt!KeFlushTb+0x119
fffff880`07ed8250 fffff800`02ed64ff : fffff680`0013e5b0 fffff880`07ed8300 fffff700`01080000 fffffa80`040faec8 : nt! ?? ::FNODOBFM::`string'+0xae02
fffff880`07ed8290 fffff800`02ee375e : 00000000`00000000 00000000`27cb6000 fffff880`07ed85f0 fffff680`0013e5b0 : nt!MiResolveDemandZeroFault+0x1ff
fffff880`07ed8380 fffff800`02ed2f19 : fffff880`07ed8c00 ffffffff`ffffffff fffff880`00000000 f4636553`0303be80 : nt!MiDispatchFault+0x8ce
fffff880`07ed8490 fffff800`02ec3d6e : 00000000`00000000 00000000`27cb6000 fffff8a0`0ce57400 ffffffff`ffffffff : nt!MmAccessFault+0x359
fffff880`07ed85f0 fffff800`02ee22f8 : 00000000`00022041 fffff880`0564e3a0 ffffffff`ffffffff fffff800`02ff41de : nt!KiPageFault+0x16e
fffff880`07ed8780 fffff800`03330dcf : fffffa80`07e93b10 ffffffff`ffffff01 00000000`00000000 00000000`27caf000 : nt!MmProbeAndLockPages+0x118
fffff880`07ed8890 fffff880`041d1ad4 : 00000000`27caf000 fffff880`07ed8b18 fffffa80`05f54010 fffff800`00000001 : nt!MmRotatePhysicalView+0x32f
fffff880`07ed8ad0 fffff880`041c2811 : 00000000`c0f8c000 fffff8a0`0a4a1a90 00000000`c0f8c000 fffffa80`05f54010 : dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0x2d0
fffff880`07ed8b60 fffff880`041bbd78 : fffff8a0`0a4a1a90 fffff8a0`00000001 00000000`00000000 fffffa80`07ce9000 : dxgmms1!VIDMM_GLOBAL::SetupAllocationForCPUAccess+0x3e1
fffff880`07ed8c10 fffff880`041bb38f : fffff880`07ed8f68 00000000`000007ff fffff880`07ed8ee0 fffff880`07ed8f78 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x488
fffff880`07ed8d30 fffff880`041d5231 : 00000000`00000001 fffff880`041a70d4 fffffa80`07627910 fffffa80`07627910 : dxgmms1!VidMmiProcessSystemCommand+0x23
fffff880`07ed8d60 fffff880`041d43bc : fffff880`07ed8ec0 00000000`00000000 fffffa80`07982ec0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`07ed8d90 fffff880`041a677a : 00000000`00000000 fffffa80`07627910 fffffa80`07982ec0 fffffa80`07982ec0 : dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`07ed8dc0 fffff880`041d6927 : fffffa80`0794caf0 fffffa80`07983000 fffffa80`07982ec0 00000000`00000440 : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`07ed8e50 fffff880`041bb4b9 : fffffa80`00000001 fffffa80`07982010 fffffa80`07ce9000 fffff880`07ed8f68 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`07ed8ec0 fffff880`041bb8dc : fffff880`07ed8ff8 00000000`00000001 fffff880`07ed8ff8 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
fffff880`07ed8f30 fffff880`041b8b8e : fffffa80`07ce9000 fffffa80`041069f0 00000000`00000000 fffff800`02ff4fbd : dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x4c
fffff880`07ed8fa0 fffff880`0419e260 : fffffa80`07ce9000 00000000`00000001 00000000`00000000 fffff880`040ab07f : dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0xcfa
fffff880`07ed9070 fffff880`04107fa7 : 00000000`000ec4a0 fffffa80`0798e000 00000000`000ec4a0 fffff880`040aa07b : dxgmms1!VidMmBeginCPUAccess+0x28
fffff880`07ed90c0 fffff880`0410866e : fffff8a0`045409a0 fffff8a0`045409a0 fffff880`07ed92a0 00000155`00000000 : dxgkrnl!DXGDEVICE::Lock+0x287
fffff880`07ed9120 fffff960`001ff6f2 : 00000000`000ec4a0 fffff880`40000301 fffff800`000007db fffff8a0`0b81f000 : dxgkrnl!DxgkLock+0x22a
fffff880`07ed91f0 fffff800`02ec4ed3 : 00000000`00000001 00000000`1bfa0000 00000000`03af0d01 00000000`1bf86bb0 : win32k!NtGdiDdDDILock+0x12
fffff880`07ed9220 00000000`7581156a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ec478 fffff800`02ebd210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7581156a
fffff880`07ed9740 fffff900`c0609b10 : 00000000`000000a0 fffffa80`07e8daa0 fffff960`0013602e 00000000`00000000 : nt!KiCallUserMode
fffff880`07ed9748 00000000`000000a0 : fffffa80`07e8daa0 fffff960`0013602e 00000000`00000000 fffff880`07ed9c70 : 0xfffff900`c0609b10
fffff880`07ed9750 fffffa80`07e8daa0 : fffff960`0013602e 00000000`00000000 fffff880`07ed9c70 00000000`00000000 : 0xa0
fffff880`07ed9758 fffff960`0013602e : 00000000`00000000 fffff880`07ed9c70 00000000`00000000 00000000`ff6b6b6b : 0xfffffa80`07e8daa0
fffff880`07ed9760 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!FreeObject+0x4e


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
---------
Still STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg is what we are looking at.

Update the following drivers. The drivers may already be the latest, so if you cannot find an update, do not worry too much about it. You may want to install the drivers in compatibility mode for Vista if the newest are still prior to July 13, 2009. Drivers - Install Vista Drivers on Windows 7 may be a useful resource.
Code:
scmndisp	fffff880`01937000	fffff880`01941000	Wed Jan 17 00:48:03 2007 (45add4b3)	00008b81		scmndisp.sys
jswpslwfx	fffff880`0433e000	fffff880`0434b000	Thu May 15 04:28:50 2008 (482c1062)	00011e66		jswpslwfx.sys
FNETURPX	fffff880`03ea9000	fffff880`03eb2000	Fri Oct 03 20:27:02 2008 (48e6d476)	00010f39		FNETURPX.SYS
SCDEmu	fffff880`043a6000	fffff880`043bf000	Sun Mar 15 04:30:00 2009 (49bcd8a8)	0001b43b		SCDEmu.SYS
GEARAspiWDM	fffff880`0534f000	fffff880`0535c000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
scmndisp.sys
jswpslwfx.sys
FNETURPX.SYS
SCDEmu.SYS
GEARAspiWDM.sys
You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.
  1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
  2. Driver Search Methods provides driver manufacturers and links to their homepages.
There are a few methods for updating drivers.
  1. Installing and updating drivers in 7
  2. Driver Install - Add Hardware Wizard
  3. Driver Install - Device Manager

To fully re-install a driver, use the following steps.
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Find the device you are trying to uninstall by expanding the appropriate set of devices
  6. Right click the device
  7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer
  10. Install the latest driver for the device once Windows starts.

Alternatively:
  1. Login as an adminstrative user.
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer
  11. Install the latest driver for the device once Windows starts.
My System SpecsSystem Spec
02 Feb 2012   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

Have you looked into your PSU?

And you ran all three prime95 tests? No problems?


If swapping the PSU doesn't stop the crashes then your next step would be to RMA your CPU and see what that does


EDIT:
Code:
Event[129]:
  Log Name: System
  Source: k57nd60a
  Date: 2012-02-02T19:00:05.427
  Event ID: 4
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: peteski-PC
  Description: 
Broadcom NetLink (TM) Gigabit Ethernet: The network link is down.  Check to make sure the network cable is properly connected.
This error occurs very frequently in your system event logs. Are you unplugging your internet cable from the computer?


BSOD BUGCHECK SUMMARY
Code:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb  2 13:21:05.748 2012 (UTC - 5:00)
System Uptime: 0 days 1:33:40.575
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 30 13:48:18.246 2012 (UTC - 5:00)
System Uptime: 0 days 0:34:38.448
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  ConduitHelper.
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 18:46:43.906 2012 (UTC - 5:00)
System Uptime: 0 days 9:40:01.733
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  ConduitHelper.
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 27 19:11:51.680 2012 (UTC - 5:00)
System Uptime: 0 days 4:02:51.882
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  ConduitHelper.
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 27 15:07:35.068 2012 (UTC - 5:00)
System Uptime: 0 days 0:52:10.270
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  ConduitHelper.
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 27 12:32:45.970 2012 (UTC - 5:00)
System Uptime: 0 days 1:06:14.172
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 18 14:12:28.671 2012 (UTC - 5:00)
System Uptime: 0 days 2:04:20.498
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 16 14:58:09.814 2012 (UTC - 5:00)
System Uptime: 0 days 4:17:08.016
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 16:00:27.344 2012 (UTC - 5:00)
System Uptime: 0 days 6:45:01.992
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  TuneUpUtilitie
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 16:21:46.291 2012 (UTC - 5:00)
System Uptime: 0 days 2:44:41.493
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan  4 16:23:48.405 2012 (UTC - 5:00)
System Uptime: 0 days 3:22:49.232
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  SketchUp.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Dec 26 16:30:51.885 2011 (UTC - 5:00)
System Uptime: 0 days 8:06:15.712
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Dec  2 17:11:39.636 2011 (UTC - 5:00)
System Uptime: 0 days 0:13:45.463
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  SketchUp.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Dec  2 16:57:01.826 2011 (UTC - 5:00)
System Uptime: 0 days 0:32:30.028
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  SketchUp.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov 30 12:16:11.870 2011 (UTC - 5:00)
System Uptime: 0 days 0:28:07.072
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct 22 01:40:36.546 2011 (UTC - 5:00)
System Uptime: 0 days 0:20:05.373
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct 15 13:00:32.014 2011 (UTC - 5:00)
System Uptime: 0 days 3:54:18.842
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Oct 11 00:07:45.247 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:56.449
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct  8 10:46:13.160 2011 (UTC - 5:00)
System Uptime: 0 days 3:22:36.362
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
02 Feb 2012   #8

Windows 7 Professional x64
 
 

I, too, believe this is either firmware or hardware-related. Even though Prime95 didn't show any errors, you're best off just RMAing the CPU anyway.

Before you do, give this BIOS update a shot: ASRock > Products > Motherboard > Z68 Extreme4 > Download

Flash 1.70; it's a free and quick procedure that just might save you an RMA.

Code:
BIOS Version/Date    American Megatrends Inc. P1.60, 12/07/2011
My System SpecsSystem Spec
03 Feb 2012   #9

windows 7 home 64 bit
 
 

Hi guys i'v updated said drivers and BIOS except jswpslwfx.sys as there is no update. So fingers crossed all is good because i dont relly like the idea of sending things back.
Big thanks for the help and i'll let you know how it goes
My System SpecsSystem Spec
04 Feb 2012   #10

windows 7 home 64 bit
 
 

Hi guys happened again but today i borrowed some ram of my brother . So lets see how that goes
My System SpecsSystem Spec
Reply

 BOSD when doing nothing




Thread Tools



Similar help and support threads for2: BOSD when doing nothing
Thread Forum
BOSD again... BSOD Help and Support
BOSD help.. BSOD Help and Support
bosd plz help BSOD Help and Support
I'm having a lot of BOSD's BSOD Help and Support
Bosd (help) BSOD Help and Support
BOSD Help BSOD Help and Support
BOSD every 4-7 min 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 08:38 AM.
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