Random freezes/audio loops Win7 x64

[Hemulen]

I have had Driver Verifier on for a couple of days now, and got a couple of crashes.

What to do now?

 

[ttran]

Can you upload the minidump for the crashes?

 

[Hemulen]

The minidump folder is empty...

 

[ttran]

Have you turned the system on for collecting minidump stuff?
You got BSODs right? Sorry If I misunderstood
Here is the instruction for turning minidump collect:
Set MiniDump

 

[Hemulen]

I included the minidump in this post.

 

[Hemulen]

Opened log file 'c:\debuglog.txt'
1: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
1: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        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: fffffa80082fb038, 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`02ff66b0 fffff800`02ebba79 : fffffa80`082fb010 fffffa80`06a2f680 fffff8a0`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02ff6bd0 fffff800`02d9d5a7 : fffffa80`082fb010 fffff800`02e165f8 fffffa80`06a2f680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02ff6c00 fffff800`02d05b85 : fffff800`02e78360 fffffa80`0909c508 fffffa80`0909c500 fffffa80`06a2f680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02ff6c40 fffff800`02c7e861 : fffff880`010d7e00 fffff800`02d05b60 fffffa80`06a2f680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02ff6c70 fffff800`02f16a86 : 3f3f3f3f`3f3f3f3f fffffa80`06a2f680 00000000`00000080 fffffa80`06a1e040 : nt!ExpWorkerThread+0x111
fffff880`02ff6d00 fffff800`02c4fb06 : fffff880`009e9180 fffffa80`06a2f680 fffff880`009f3f40 3f3f3f3f`3f3f3f3f : nt!PspSystemThreadStartup+0x5a
fffff880`02ff6d40 00000000`00000000 : fffff880`02ff7000 fffff880`02ff1000 fffff880`02ff5da0 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_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

rax=fffffa80083df000 rbx=fffffa80082fb038 rcx=fffff88002ff66f0
rdx=fffff88002f00000 rsi=0000000000000000 rdi=fffffa80083df000
rip=fffff800030a6f3c rsp=fffff88002ff66b0 rbp=0000000000000001
 r8=000000000000f1e0  r9=000000000000060c r10=00000000000007ff
r11=000000000000060c r12=fffff80002e783c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`030a6f3c 48897c2438      mov     qword ptr [rsp+38h],rdi ss:0018:fffff880`02ff66e8=fffffa8000000950
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`02ff66b0 fffff800`02ebba79 : fffffa80`082fb010 fffffa80`06a2f680 fffff8a0`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02ff6bd0 fffff800`02d9d5a7 : fffffa80`082fb010 fffff800`02e165f8 fffffa80`06a2f680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02ff6c00 fffff800`02d05b85 : fffff800`02e78360 fffffa80`0909c508 fffffa80`0909c500 fffffa80`06a2f680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02ff6c40 fffff800`02c7e861 : fffff880`010d7e00 fffff800`02d05b60 fffffa80`06a2f680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02ff6c70 fffff800`02f16a86 : 3f3f3f3f`3f3f3f3f fffffa80`06a2f680 00000000`00000080 fffffa80`06a1e040 : nt!ExpWorkerThread+0x111
fffff880`02ff6d00 fffff800`02c4fb06 : fffff880`009e9180 fffffa80`06a2f680 fffff880`009f3f40 3f3f3f3f`3f3f3f3f : nt!PspSystemThreadStartup+0x5a
fffff880`02ff6d40 00000000`00000000 : fffff880`02ff7000 fffff880`02ff1000 fffff880`02ff5da0 00000000`00000000 : nt!KxStartSystemThread+0x16
start             end                 module name
fffff800`00ba4000 fffff800`00bae000   kdcom    kdcom.dll    Tue Jul 14 03:31:07 2009 (4A5BDFDB)
fffff800`02c01000 fffff800`031dd000   nt       ntkrnlmp.exe Sat Feb 27 08:55:23 2010 (4B88CFEB)
fffff800`031dd000 fffff800`03226000   hal      hal.dll      Tue Jul 14 03:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 03:32:13 2009 (4A5BE01D)
fffff880`00cec000 fffff880`00d30000   mcupdate mcupdate.dll Tue Jul 14 03:29:10 2009 (4A5BDF66)
fffff880`00d30000 fffff880`00d44000   PSHED    PSHED.dll    Tue Jul 14 03:32:23 2009 (4A5BE027)
fffff880`00d44000 fffff880`00da2000   CLFS     CLFS.SYS     Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`00da2000 fffff880`00dfe000   volmgrx  volmgrx.sys  Tue Jul 14 01:20:33 2009 (4A5BC141)
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Tue Jul 14 01:19:34 2009 (4A5BC106)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Tue Jul 14 01:19:51 2009 (4A5BC117)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Tue Jul 14 01:19:26 2009 (4A5BC0FE)
fffff880`00e6a000 fffff880`00e9d000   pci      pci.sys      Tue Jul 14 01:19:51 2009 (4A5BC117)
fffff880`00e9d000 fffff880`00eaa000   vdrvroot vdrvroot.sys Tue Jul 14 02:01:31 2009 (4A5BCADB)
fffff880`00eaa000 fffff880`00ebf000   partmgr  partmgr.sys  Tue Jul 14 01:19:58 2009 (4A5BC11E)
fffff880`00ebf000 fffff880`00ed4000   volmgr   volmgr.sys   Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`00ed4000 fffff880`00edb000   pciide   pciide.sys   Tue Jul 14 01:19:49 2009 (4A5BC115)
fffff880`00edb000 fffff880`00eeb000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 01:19:48 2009 (4A5BC114)
fffff880`00eeb000 fffff880`00ef6000   amdxata  amdxata.sys  Tue May 19 19:56:59 2009 (4A12F2EB)
fffff880`00efb000 fffff880`00f9f000   Wdf01000 Wdf01000.sys Tue Jul 14 01:22:07 2009 (4A5BC19F)

 

[ttran]

Yep, you got it, stop code 124, u might want to read this article:
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

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

Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.602\062210-17940-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Tue Jun 22 18:38:49.562 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:11.122
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, fffffa80082fb038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------

Tuan

 

[Hemulen]

Yep, you got it, stop code 124, u might want to read this article:
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

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

Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.602\062210-17940-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Tue Jun 22 18:38:49.562 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:11.122
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, fffffa80082fb038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------

Tuan

I checked the thread you linked to;

1) No hardware overclocked
2) PC have enough cooling
3) I updated all my drivers (I have RAID setup, but no RAID card)
4) Latest BIOS
6)
7) I have ran RAM tests without errors before, and same thing on the HDD's. (I can run again)
8) I did not try a "vanilla" re-install, but I have done several clean installs, and got the same error without even touching Windows after installation.
9) I airdust my computer with compressor every week
10) Haven't removed hardware piece for piece, but I can do that and report back.

 

[Hemulen]

No harddrive error or RAM problems. (Checked it with Windows build-in programs)

 

[Hemulen]

Where to go from here?

 

[Hemulen]

BUMP

 

[ttran]

crash again?

 

[Hemulen]

Yes, still crashing.

 

[ttran]

BSODs? Minidump?

 

[Hemulen]

Still crashing guys. Any help? "/

 

[ttran]

BSODs? Can you upload DMP file

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

 

[Hemulen]

BSODs? Can you upload DMP file

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

Its still the same shit as before. Still same error code.

 

[ttran]

You mean still same stop code 124, that's related to hardware as I mentioned earlier.
Let's try some hardware test:
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Don't use built in window memtest, it's not trust worthy

Check your CPU with prime 95
Try this free stress test: http://www.mersenne.org/freesoft/

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Check CPU temperature with SpeedFan - Access temperature sensor in your computer

Do a hard drive diagnostic: HD Diagnostic , download the diagnostic from manufacture site perhaps