BSOD and random hangups while watching videos, gaming, browsing

lintok · 25 Apr 2012

Windows 7
- x64
- originally installed OS
- retail version from Microsoft Dynamics Academic Alliance
- first os installation (no re-install, so far thinking to do so)

My system is just about a month old and I experience random bsod or hangups, it can occur after 3 days without problems. I have done memtest for about 7 passes but there are no errors, also performed vidmemtest and no errors. I have performed driver verifier and there are 2 recent bsods which points out at Caused by driver address: ntoskrnl.exe+7cc80 as seen in blue screen view, other past dump files also say it is due to atikmdag.sys, hal.dll

lintok · 25 Apr 2012

Here are the dump files, the last two where from performing driver verifier.

lintok · 26 Apr 2012

Can a reason be that I changed the sata cable of the hard disk drive inside or just software issues? Can someone explain what the dump files point out to

writhziden · 27 Apr 2012

Code:

tuneuputilitiesapp64.exe	c:\program files (x86)\tuneup utilities 2012\tuneuputilitiesapp64.exe	2304	8	200	1380	4/25/2012 11:01 PM	12.0.3010.5	1.29 MB (1,352,512 bytes)	2/9/2012 9:13 PM
tuneuputilitiesservice64.exe	c:\program files (x86)\tuneup utilities 2012\tuneuputilitiesservice64.exe	1800	8	200	1380	4/25/2012 11:01 PM	12.0.3010.5	2.04 MB (2,143,552 bytes)	2/9/2012 9:13 PM

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\lintok\Windows_NT6_BSOD_jcgriff2\042512-24897-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
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03052650
Debug session time: Tue Apr 24 12:31:38.552 2012 (UTC - 6:00)
System Uptime: 0 days 0:09:16.396
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Unable to load image \SystemRoot\system32\DRIVERS\epfwwfpr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for epfwwfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
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: fffff880009e9180, 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:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0a2a4f48 fffff800`02ee1a3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009e9180 : nt!KeBugCheckEx
fffff880`0a2a4f50 fffff800`02e947f7 : 00000000`00000000 fffff800`00000001 00000000`00026161 fffff880`0a2a0000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a2a4fe0 fffff800`03400895 : fffff800`03426460 fffff880`0a2a5190 fffff800`03426460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a2a50e0 fffff800`02e871d3 : 00000000`68e9a8c5 fffff800`02fffe80 00000000`00000000 fffff800`02e0e000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a2a5110 fffff800`02e8fae0 : fffff800`02fffe80 00000000`00000001 00000000`00000000 fffff880`0a2a53c8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a2a52a0 fffff800`02eede68 : 0000007f`fffffff8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x260
fffff880`0a2a5370 fffff800`02f8bced : fffff800`030bf600 fffff880`0a2a5580 00000000`00000000 fffff800`00000003 : nt! ?? ::FNODOBFM::`string'+0x20a3e
fffff880`0a2a5560 fffff800`02f8d2b7 : fffffa80`082f9060 00000000`00000001 00000000`00000000 00000000`00000008 : nt!MiEmptyWorkingSet+0x27d
fffff880`0a2a5610 fffff800`0332a261 : 00000000`00000000 fffff880`07f28102 fffff880`07f1e6c3 fffffa80`082d4e40 : nt!MiTrimAllSystemPagableMemory+0x218
fffff880`0a2a5670 fffff800`0332a3bf : fffff880`07f28102 fffffa80`06c82568 fffffa80`06c82568 fffffa80`0a3007c8 : nt!MmVerifierTrimMemory+0xf1
fffff880`0a2a56a0 fffff800`0332a85c : fffff880`07f28140 00000000`000000e0 00000000`00000e80 ffffffff`ffffffff : nt!ViKeRaiseIrqlSanityChecks+0xcf
fffff880`0a2a56e0 fffff880`07f1e6c3 : 00000000`00000000 00000000`00000000 00000000`000001c2 00000000`00000000 : nt!VerifierKeAcquireInStackQueuedSpinLock+0xac
fffff880`0a2a5720 00000000`00000000 : 00000000`00000000 00000000`000001c2 00000000`00000000 fffffa80`082d4e80 : epfwwfpr+0x116c3


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_VRF_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

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

The above crash information can be found in STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

It may be due to a corrupt installation of your ESET software since the ESET software is in the memory stack at the time of the crash, and the ESET driver listed appears to be corrupted. I would recommend removing ESET completely using How do I manually uninstall my Windows ESET security product? - ESET Knowledgebase and then downloading and installing the latest version of ESET.

lintok · 27 Apr 2012

Thanks sir for your reply, I thought someone wouldn't notice.
I will do your recommendations and thanks again for the tip in optimizations and performance maintenance. :)

writhziden · 27 Apr 2012

You're welcome. We try not to let threads go unnoticed. :)

Look forward to hearing back how the system responds to the steps.

lintok · 29 Apr 2012

Ugh

, I've done a reinstall/reformat of windows (Deleting all partition) to the hope of clearing things up. Didn't installed tuneuputilities and installed the latest version of eset. Just now I got a freeze or lockup while only on the desktop explorer. I'm thinking if it is related to the graphics/video card, cable, connection, monitor, or the (AMD Catalyst Driver itself which is the latest version 12.4 w/c has just been released on 4/25/2012) because sometimes when I reboot the resolution goes back to low and the display detects Generic Non-Pnp monitor then detect doesn't work and I would follow simple steps of turning down power and unplugging the power cable to the monitor and when booting up again it would revert back to detecting my monitor/display SyncMaster and to the recommended resolution.

Would I post another BSOD Dump & System File Collection and Perfmon?

writhziden · 29 Apr 2012

Have you had another blue screen crash? If not, it would be enough just to post the msinfo32 log. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

I would also recommend a hardware stripdown.

Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves by running Windows for twice as long as it typically takes for you to get a crash. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

lintok · 29 Apr 2012

I haven't had any bsods yet, I'll work into what you have said. Thanks, here is the msinfo32.

writhziden · 29 Apr 2012

I would recommend removing rocketdock for testing purposes. See if you have more stability. The software seems to be intended for Windows prior to Windows 7 since Windows 7 already provides much of the functionality offered in that application. It's possible the old software is causing issues with explorer.exe; it seems to be integrated into explorer.exe based on what I have read.