WEIRD Problem, Daily BSOD.

untold21 · 21 Jan 2011

So, I have this iPower I won in an ubisoft contest, ever since I remember, I have the most weird problem you can think of. So, every single time I start my PC, Im fine for 15 minutes then sound starts stuttering and skipping, 2 minutes later my network card goes disabled and then I get a BSOD with something about clock interval and secondary processor and some 0x00(lots of zeros)101. Thing is, after I restart, problem is gone until the next time I shut my computer down, I have searched a lot and I have already switched my PSU, tried disabling onboard audio, full windows reinstall, etc. But nothing works, so Im writing here to see if anyone has anything that could help.

Using Win7 x64, Have PC for like 1 year, this Windows install has like 2/3 weeks, was OEM Vista but I upgraded.

untold21 · 21 Jan 2011

Uploaded info that the sticky thread asks for, however I dont know if those dumps are correct, Im so fed up with it that I just press the shutdown button when the blue screen appears.

fimble · 21 Jan 2011

Hi untold21,

One of these drivers is specifically mentioned in your dump file, as well as usb drivers. Your usb drivers are up to date

Amfltx64.sys Mon Oct 15 04:37:21 2007
Amusbx64.sys Wed Feb 13 08:20:14 2008 A4Tech X-705FS Mouse Driver

If you cannot update the drivers uninstall the software, try another mouse.

AVG is known to be a cause of BSOD's on some Win 7 systems so it may be advisable to uninstall it. Download the correct AVG Remover for your system. Download Microsoft Security Essentials as its replacement. Re-boot to Safe Mode. In Safe Mode run the AVG Remover tool. Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled!

Outdated driver:

Rt64win7.sys Thu Feb 26 09:04:13 2009 Realtek LAN RTL811

Post back with updated info as and when.

untold21 · 22 Jan 2011

I have ordered a new mouse from Logitech (G9x), will remove the current one's driver and use windows default while it doesnt arrive, I will remove AVG and try to reproduce the BSOD again.

PS: Any tips on how to be sure I removed the faulty mouse driver?

fimble · 22 Jan 2011

The easiest way is to rename them.

Create a Restore Point, GoTo C:\Windows\System32\Drivers, locate the driver(s) files and rename them from .sys to .old.
Reboot and the drivers will not load. This also breaks the software or hardware these drivers are associated with.

untold21 · 22 Jan 2011

fimble said:

The easiest way is to rename them.

Create a Restore Point, GoTo C:\Windows\System32\Drivers, locate the driver(s) files and rename them from .sys to .old.
Reboot and the drivers will not load. This also breaks the software or hardware these drivers are associated with.

I uninstalled the software and took ownership of all its .sys files and deleted them, that ok too right?

fimble · 22 Jan 2011

Yeah, thats good.

untold21 · 22 Jan 2011

I crashed again before restarting my system after removing the mouse drivers and updating the network ones.

Uploaded the dump.

fimble · 22 Jan 2011

Your last dump file has a stop 101 error.

See: Win 7 A Clock Interrupt... BSOD (101 Error)

When you say:

I crashed again before restarting my system after removing the mouse drivers and updating the network ones.

I take it you mean, you uninstalled and updated, then it crashed before rebooting?

Did you reboot OK?

Code:

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


Loading Dump File [D:\ DOWNLOADS\ DUMPS\untold21\Windows_NT6_BSOD_jcgriff2\012211-32027-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\XSymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`0343ee50
Debug session time: Sat Jan 22 15:30:21.066 2011 (UTC + 0:00)
System Uptime: 0 days 5:38:01.034
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88003113180, 6}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003113180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`00b9ca28 fffff800`0321f453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03113180 : 0xfffff800`03271740
fffff800`00b9ca30 00000000`00000101 : 00000000`00000019 00000000`00000000 fffff880`03113180 00000000`00000006 : 0xfffff800`0321f453
fffff800`00b9ca38 00000000`00000019 : 00000000`00000000 fffff880`03113180 00000000`00000006 fffff880`044af35e : 0x101
fffff800`00b9ca40 00000000`00000000 : fffff880`03113180 00000000`00000006 fffff880`044af35e 00000006`00000000 : 0x19


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner

untold21 · 22 Jan 2011

fimble said:

Your last dump file has a stop 101 error.

See: Win 7 A Clock Interrupt... BSOD (101 Error)

When you say:

I crashed again before restarting my system after removing the mouse drivers and updating the network ones.

I take it you mean, you uninstalled and updated, then it crashed before rebooting?

Did you reboot OK?

Code:

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


Loading Dump File [D:\ DOWNLOADS\ DUMPS\untold21\Windows_NT6_BSOD_jcgriff2\012211-32027-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\XSymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`0343ee50
Debug session time: Sat Jan 22 15:30:21.066 2011 (UTC + 0:00)
System Uptime: 0 days 5:38:01.034
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88003113180, 6}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003113180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`00b9ca28 fffff800`0321f453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03113180 : 0xfffff800`03271740
fffff800`00b9ca30 00000000`00000101 : 00000000`00000019 00000000`00000000 fffff880`03113180 00000000`00000006 : 0xfffff800`0321f453
fffff800`00b9ca38 00000000`00000019 : 00000000`00000000 fffff880`03113180 00000000`00000006 fffff880`044af35e : 0x101
fffff800`00b9ca40 00000000`00000000 : fffff880`03113180 00000000`00000006 fffff880`044af35e 00000006`00000000 : 0x19


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner

I deleted the mouse driver, updated the network driver then I finished the game I was playing (was midmatch in PES2011) and I crashed almost on the end of the match, I havent got any problems after this BSOD but that is normal, Im going to turn my pc off for the night now, Ill report any further BSODs if any.