Yeah, almost half a day and no freezing. It's beating the record so far. It looks like it solved. I'll wait at least a couple days and if it is solved, I'll return the mobo I ordered and let you guys know which options helped me with the freezing
So I got a BSOD today, but this time it did not freeze like all other times. The minidump was saved. I believe the freezing issue is solved and this is related to something else. My memory was in it's XMP profile so I set it back to stock(1333mhz, 1.5v). I believe this was the problem, but just in case, could someone take a look at the minidump and see what triggered it?
Thank you!
While your .dmp file is informative, it is not the best information for helping with crashing/freezing problems. If you follow the https://www.sevenforums.com/crashes-d...tructions.html, it provides us with more information than just the .dmp file. The information may be helpful if you continue to have problems so we know more about your system and can determine possible conflicts, application errors, system errors, etc. existing on the system.
Your blue screen crash (seen below) was due to Stop 0x101, and may be resolved using STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg. It may be the RAM, as you said, but there are other possibilities outlined in that thread by usasma, who is one of the best hardware debuggers on here.
Code:Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\meuqsaco\012112-15163-01\012112-15163-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe70 Debug session time: Sat Jan 21 08:24:06.373 2012 (UTC - 7:00) System Uptime: 0 days 1:16:52.294 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {19, 0, fffff880032f9180, 6} 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: fffff880032f9180, The PRCB address of the hung processor. Arg4: 0000000000000006, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: swtor.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0a2e1498 fffff800`02e70463 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`032f9180 : nt!KeBugCheckEx fffff880`0a2e14a0 fffff800`02ecac87 : 00000000`00000000 fffff800`00000006 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d8e fffff880`0a2e1530 fffff800`02e13895 : fffff800`02e38460 fffff880`0a2e16e0 fffff800`02e38460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0a2e1630 fffff800`02ebeab3 : 00000000`83cfc1fa fffff800`0303ce80 00000000`00001000 fffff800`02ff6bfe : hal!HalpHpetClockInterrupt+0x8d fffff880`0a2e1660 fffff800`02ef3621 : 00000003`00000000 fffffa80`00000000 00000000`00000001 c5f00001`83ac3025 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0a2e17f0 fffff800`02ef5cc9 : 00000000`00000000 00000000`0bd90fff fffff880`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x7d8 fffff880`0a2e19b0 fffff800`031d8050 : fffffa80`06a31160 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`0a2e1ad0 fffff800`031d845b : 00000980`00000000 00000000`0bd90000 fffffa80`00000001 00000000`0fe2eb01 : nt!MiUnmapViewOfSection+0x1b0 fffff880`0a2e1b90 fffff800`02ec1813 : 00000000`00000000 00000000`77081a75 fffffa80`06838060 fffffa80`0c767900 : nt!NtUnmapViewOfSection+0x5f fffff880`0a2e1be0 00000000`7762f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0fe2e208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7762f95a 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_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
The pc froze 3 times just now, damn. I read the topic and people say it is most likely the CPU that causes it. Forget the minidump. My new mobo just arrived and I installed everything and formatted windows with updated drivers. I am now going to test it and if it freezes, then I will return the mobo and contact Intel to request an RMA.
One thing I noticed is that the GPU temprature is higher on this board. I'm not sure how the mobo could affect it, maybe the size of the heatsink? On the Asus mobo, the one close to the GPU is bigger.
Quote