New
#1
BSOD when computer has been idle
I just built this computer about a month ago and it seems that when the computer stay idle for a little bit, it BSOD. I have turned my power options to never turn off display or put computer to sleep but still occurs. this is the first pc ive built, so maybe it was something i did. Please assist
CPU: Intel Pentium G3258 3.2GHz Dual-Core Processor
CPU Cooler: Arctic Cooling Freezer 7 Pro Rev.2 45.0 CFM Fluid Dynamic Bearing CPU Cooler
Motherboard: Gigabyte GA-Z97-HD3 ATX LGA1150 Motherboard
Memory: Corsair Vengeance 8GB (2 x 4GB) DDR3-1600 Memory
Storage: Crucial MX100 128GB 2.5" Solid State Drive
Storage: Western Digital Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive
Video Card: MSI Radeon R9 290 4GB TWIN FROZR Video Card
Case: Corsair SPEC-03 Red ATX Mid Tower Case
Power Supply: Enermax 600W 80+ Platinum Certified Semi-Modular ATX Power Supply
DRW-24B1ST/BLK/B/AS
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
Machine Name:
Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03462730
Debug session time: Thu May 14 21:50:15.603 2015 (UTC - 4:00)
System Uptime: 0 days 0:51:34.571
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80074d4038, bf800000, 200401}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
1: 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: fffffa80074d4038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: ubssrv_oc_only
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
STACK_TEXT:
fffff880`009f59d8 fffff800`03819a3b : 00000000`00000124 00000000`00000000 fffffa80`074d4038 00000000`bf800000 : nt!KeBugCheckEx
fffff880`009f59e0 fffff800`033a8c33 : 00000000`00000001 fffffa80`075063b0 00000000`00000000 fffffa80`07506400 : hal!HalBugCheckSystem+0x1e3
fffff880`009f5a20 fffff800`03819700 : 00000000`00000728 fffffa80`075063b0 fffff880`009f5db0 fffff880`009f5d00 : nt!WheaReportHwError+0x263
fffff880`009f5a80 fffff800`03819052 : fffffa80`075063b0 fffff880`009f5db0 fffffa80`075063b0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f5bd0 fffff800`03818f0d : 00000000`00000002 00000000`00000001 fffff880`009f5e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f5c10 fffff800`0380ce88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f5c40 fffff800`0328e1ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f5c70 fffff800`0328e013 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f5db0 fffff800`032864e8 : fffff800`03533bc7 fffff880`075eec60 00000000`00000018 00000000`00000010 : nt!KiMcheckAbort+0x153
fffff880`075ee738 fffff800`03533bc7 : fffff880`075eec60 00000000`00000018 00000000`00000010 00000000`00000000 : nt!memcpy+0x208
fffff880`075ee740 fffff800`035339df : fffffa80`0b38b570 00000000`0069006d fffffa80`06cbcb10 00000000`02cfe6f8 : nt!MmCopyVirtualMemory+0x17b
fffff880`075eeaf0 fffff800`0328eb53 : fffffa80`0db3fb50 00000000`046be1b8 fffff880`075eeb88 00000000`00003ee4 : nt!NtReadVirtualMemory+0xff
fffff880`075eeb70 00000000`7752dfaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`046be198 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7752dfaa
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner
---------
Quote