randomly unresponsive, then long reboot

RobM2 · 24 Oct 2010

I've been trying to track this down, and fix it, since I built this system 5 months ago. Now I'm getting desperate... when all else fails, ask for help.

Problem: every few days, or occasionally twice a day, my system will become very slow. Programs become unresponsive, (even pulling up the task manager), and it takes about 3 minutes for the system to shut down, and another 15-20 minutes for the system to reboot.

I have tried everything I can think of. I have a minimal set of starup items, (just 3 in msconfig; joystick, audio control panel, and IAStorIcon. I have searched through event viewer, and the only indication I get is that windows logoff took an insanely long time to log off. Scannow indicates no problems.

I have turned off dozens and dozens of services, and still I haven't been able to track this down. I've tried manually quitting and restarting expolorer, manually shutting down each service when it gets slow, but invariably when it happens, I'm stuck with a 15-20 minute reboot, instead of 20-30 seconds.

When it reboots, I get a flashing underline, then it sits on the windows startup screen for the next 12-15 minutes, then eventually boots into the desktop and everything is normal again.

I've turned off all power saving features, and have everything running at full power. I've turned off all schedules (as far as I know) of all events that might otherwise run at regular intervals.

When it becomes unresponsive, everything just gets insanely slow, (except mouse movement, which is normal). No, there are no viruses or malware, as it has been happening since Day 1.

It only becomes unresponsive when I'm doing something on the desktop. If I'm in a game, it never happens. I'm running in the windows classic theme and have turned off as much as possible to narrow this down.

Help!

richc46 · 24 Oct 2010

Scan with the antivirus
Download and scan with malwarebytes, full scan after updating.
Let us know
Try in safe mode, see if problem persists, let us know.

RobM2 · 06 Nov 2010

No issues on full scan with the anti-virus. No issues on scan with malwarebytes.
Have not yet had the problem running in safe mode.

Attempted the run with the driver verifier, today, and it crashed during bootup,
http://www3.telus.net/rmuscoby/pics/...D_jcgriff2.zip

However, the mini dump was not from today, (not from the running of the driver verifier).

Still getting random periods of unresponsiveness, followed by a 20 minute reboot.

Still need help!! What's next??

RobM2 · 20 Nov 2010

Bump - still happens every now & then; can't figure out why

richc46 · 20 Nov 2010

Code:

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Rob-Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\102310-13884-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 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03418000 PsLoadedModuleList = 0xfffff800`03655e50
Debug session time: Sat Oct 23 07:19:29.777 2010 (GMT-5)
System Uptime: 0 days 0:00:04.854
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80065918f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80065918f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`0371d6f0 fffff800`036d2a89 : fffffa80`065918d0 fffffa80`05525680 fffffa80`00000004 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0371dc10 fffff800`035b4667 : fffffa80`065918d0 fffff800`0362d5f8 fffffa80`05525680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0371dc40 fffff800`0351cc45 : fffff800`0368f360 fffffa80`06560838 fffffa80`06560830 fffffa80`05525680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0371dc80 fffff800`03495961 : fffff880`01483e00 fffff800`0351cc20 fffffa80`05525680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0371dcb0 fffff800`0372cc06 : 00000000`00000000 fffffa80`05525680 00000000`00000080 fffffa80`05505040 : nt!ExpWorkerThread+0x111
fffff880`0371dd40 fffff800`03466c26 : fffff880`03531180 fffffa80`05525680 fffff880`0353c1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0371dd80 00000000`00000000 : fffff880`0371e000 fffff880`03718000 fffff880`03097590 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------
11: kd> lmtsmn
start             end                 module name
fffff880`00f9e000 fffff880`00ff5000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`01448000 fffff880`01453000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`01415000 fffff880`0141e000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0141e000 fffff880`01448000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00e2b000 fffff880`00eeb000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`011cd000 fffff880`011fd000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cfe000 fffff880`00d5c000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0153f000 fffff880`015b2000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01635000 fffff880`01643000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`01074000 fffff880`0108a000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04cb2000 fffff880`04cc5000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04aa8000 fffff880`04cb2000   dump_iaStor dump_iaStor.sys Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`0149f000 fffff880`014b3000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01453000 fffff880`0149f000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0162b000 fffff880`01635000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0103a000 fffff880`01074000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01800000 fffff880`0184a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`039f4000 fffff800`03a3d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`019f1000 fffff880`019fa000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`0120b000 fffff880`01415000   iaStor   iaStor.sys   Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`010af000 fffff880`011cd000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff800`00bc2000 fffff800`00bcc000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01600000 fffff880`0161a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`019c6000 fffff880`019f1000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00ca6000 fffff880`00cea000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e00000 fffff880`00e0a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`014e1000 fffff880`0153f000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01862000 fffff880`01874000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01874000 fffff880`01966000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01966000 fffff880`019c6000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`03418000 fffff800`039f4000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01648000 fffff880`017eb000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00d8f000 fffff880`00da4000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d5c000 fffff880`00d8f000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e17000 fffff880`00e1e000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0161a000 fffff880`0162b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00cea000 fffff880`00cfe000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0185a000 fffff880`01862000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`014b3000 fffff880`014e1000   symsnap  symsnap.sys  Tue Sep 15 17:02:11 2009 (4AB000D3)
fffff880`01a01000 fffff880`01bfe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`00e0a000 fffff880`00e17000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0184a000 fffff880`0185a000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00da4000 fffff880`00db9000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`015b2000 fffff880`015fe000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00eeb000 fffff880`00f8f000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f8f000 fffff880`00f9e000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ff5000 fffff880`00ffe000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

tezlewis · 20 Nov 2010

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV are you overclocking? Its indicating a issue with your Intel Processor in some way.

RobM2 · 20 Nov 2010

I'm not over-clocking, (no need to with this cpu).

I'm not sure what to do next... should I re-run with driver verifier?

The issue happened again, yesterday, and all I was doing was flipping through some digital camera jpegs with Windows Photo Viewer. Suddenly became slow, and it took about 3 minutes to shut down, and 15+ mins to reboot. Once back at the desktop, after the long reboot, everything was back to normal.

Edit: A few minutes after writing this, I attempted to get into event viewer, and it hung, becoming unresponsive, claiming to be waiting for "snap-ins"... Attempted a reboot, had a long shut-down, attempted a "repair installation" on reboot. All tests checked out okay, except the very last one, which said something about "your configuration has changed, so windows cannot repair the install".

richc46 · 20 Nov 2010

When you boot hear any beeeps?

RobM2 · 20 Nov 2010

No beep(s) on startup, at all.

richc46 · 20 Nov 2010

124 is hardware.
I would do memory test
Driver verifier
Then post back.