44MLX Posted October 1, 2013 Share Posted October 1, 2013 Hello everyone, today I recieved my new custom built PC, running on Windows 8 and I got two BSoDs. I want to find out what has caused this to happen and prevent such things happening in the future. Any help would be kindly appreciated. The specs are:CPU : Intel i5 4670 - (4 x 3.4 GHZ) - HaswellCPU Heatsink : Coolermaster Hyper 212 Evo - Low NoiseMemory : Corsair Dominator Platinum 8GB PC3-19200 2400 MHz (2x4GB)Graphics Card : NVIDIA GeForce GTX 760 - 2 GB - (ZOTAC) - (PCI-E)Motherboard : MSI Z87-G43 (Intel Z87) Killler LAN Port & Creative HD SoundNetworking : 1 x Wireless Network Card 150Mbps (PCI-E)Power Supply : Corsair 550W PSU - Low NoiseCPU Compound : Standard CPU Compound Supplied With HeatsinkHard Drive #1 : 120GB Corsair Force GT SSD SATA-III, Read 550MB/s, Write 515MB/s - SilentHard Drive #2 : 500 GB Seagate SATA-III HDD 7200 RPM 16MB Thank you. Link to comment Share on other sites More sharing options...
Mindovermaster Moderator Posted October 1, 2013 Moderator Share Posted October 1, 2013 What are the BSOD code numbers? Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 What are the BSOD code numbers? Not sure, but on the second one I managed to catch "System Service Exception". Link to comment Share on other sites More sharing options...
Mindovermaster Moderator Posted October 1, 2013 Moderator Share Posted October 1, 2013 In Event viewer, do you see any exclamation points? Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 In Event viewer, do you see any exclamation points? Nope. Link to comment Share on other sites More sharing options...
Astra.Xtreme Posted October 1, 2013 Share Posted October 1, 2013 Try booting with only one stick of RAM seated. Do this twice using each individual stick. If it boots only with a certain stick, then it's obviously bad RAM. It's not uncommon and they have a lifetime warranty. When I see a BSOD, RAM is always my first thought. Link to comment Share on other sites More sharing options...
sc302 Veteran Posted October 1, 2013 Veteran Share Posted October 1, 2013 the bsod has a dump file. put dump file here and paste results. http://www.osronline.com/page.cfm?name=analyze Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 Try booting with only one stick of RAM seated. Do this twice using each individual stick. If it boots only with a certain stick, then it's obviously bad RAM. It's not uncommon and they have a lifetime warranty. When I see a BSOD, RAM is always my first thought. Right now tried what you have said, and the PC loaded fine each time. Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 the bsod has a dump file. put dump file here and paste results. http://www.osronline.com/page.cfm?name=analyze Where can I find the dump files? Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 C:\Windows\Minidump Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 First Dump File: Primary Analysis Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)Online Crash Dump Analysis ServiceSee http://www.osronline.com for more informationWindows 8 Kernel Version 9200 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9200.16628.amd64fre.win8_gdr.130531-1504Machine Name:Kernel base = 0xfffff802`ee67c000 PsLoadedModuleList = 0xfffff802`ee948a20Debug session time: Tue Oct 1 12:30:02.016 2013 (UTC - 4:00)System Uptime: 0 days 2:36:12.636******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************PAGE_FAULT_IN_NONPAGED_AREA (50)Invalid system memory was referenced. This cannot be protected by try-except,it must be protected by a Probe. Typically the address is just plain bad or itis pointing at freed memory.Arguments:Arg1: fffffa8054738ac0, memory referenced.Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.Arg3: fffff802ee784c4b, If non-zero, the instruction address which referenced the bad memory address.Arg4: 0000000000000002, (reserved)Debugging Details:------------------Could not read faulting driver nameTRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802ee9d4168GetUlongFromAddress: unable to read from fffff802ee9d41f8fffffa8054738ac0 Nonpaged poolFAULTING_IP:nt!NtUnlockVirtualMemory+33bfffff802`ee784c4b 4c8b7e10 mov r15,qword ptr [rsi+10h]MM_INTERNAL_CODE: 2CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTBUGCHECK_STR: AVPROCESS_NAME: firefox.exeCURRENT_IRQL: 0TRAP_FRAME: fffff88006297100 -- (.trap 0xfffff88006297100)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000001c26839 rbx=0000000000000000 rcx=0000000000000067rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000rip=fffff802ee784c4b rsp=fffff88006297290 rbp=fffff880062974a0r8=fffff6fb40000188 r9=8000000000000000 r10=0000000fffffffffr11=0000058000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na pe cynt!NtUnlockVirtualMemory+0x33b:fffff802`ee784c4b 4c8b7e10 mov r15,qword ptr [rsi+10h] ds:00000000`00000010=????????????????Resetting default scopeLAST_CONTROL_TRANSFER: from fffff802ee7975a0 to fffff802ee6d6440STACK_TEXT:fffff880`06296f18 fffff802`ee7975a0 : 00000000`00000050 fffffa80`54738ac0 00000000`00000000 fffff880`06297100 : nt!KeBugCheckExfffff880`06296f20 fffff802`ee710acb : 00000000`00000000 fffffa80`54738ac0 fffffa80`067c4700 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33e2afffff880`06296fc0 fffff802`ee6d3eee : 00000000`00000000 00000000`00000004 00000000`06230000 fffff880`06297100 : nt!MmAccessFault+0x55bfffff880`06297100 fffff802`ee784c4b : 00000000`00000004 fffffa80`0c61e568 00000000`0624f000 00000000`06230000 : nt!KiPageFault+0x16efffff880`06297290 fffff802`ee6d5453 : fffff880`00000002 fffff880`042410d9 00000000`00023c8e 00000000`00023c8e : nt!NtUnlockVirtualMemory+0x33bfffff880`06297420 fffff802`ee6da630 : fffff880`04253d2d fffffa80`00000003 00000000`00000000 fffff880`06297600 : nt!KiSystemServiceCopyEnd+0x13fffff880`062975b8 fffff880`04253d2d : fffffa80`00000003 00000000`00000000 fffff880`06297600 fffff8a0`09465330 : nt!KiServiceLinkagefffff880`062975c0 fffff880`0423788a : 00000000`00020000 fffff8a0`036c85d0 00000000`06230000 fffff8a0`036c8601 : dxgmms1!VIDMM_PROCESS_HEAP::Reset+0x12dfffff880`06297630 fffff880`0424c69f : fffff8a0`036c85d0 00000000`00000000 fffff8a0`036c85d0 00000000`00008000 : dxgmms1!VIDMM_GLOBAL::ResetBackingStore+0x1d2fffff880`062976d0 fffff880`04242f8d : fffffa80`0a4a0000 00000000`00000000 fffff8a0`036c85d0 00000000`00000001 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0x3ebfffff880`06297720 fffff880`0423adc6 : 00000000`c0000001 fffff880`06297860 fffff8a0`036c85d0 fffffa80`067a6750 : dxgmms1!VIDMM_GLOBAL::EvictGlobalAllocation+0x69fffff880`06297760 fffff880`04256e02 : fffffa80`0a2d5400 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x8befffff880`062979d0 fffff880`04256b25 : 00000000`00000000 fffff880`00000000 fffff780`00000320 00000000`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6fffff880`06297ba0 fffff880`04256662 : fffffa80`0bf95870 fffffa80`0ce20bc0 fffffa80`0adc9010 fffffa80`0a2d5400 : dxgmms1!VidSchiSubmitQueueCommand+0x51fffff880`06297bd0 fffff802`ee6a8fd9 : fffffa80`067c4700 fffffa80`0a2d5400 fffff880`00a69e40 00000000`00d8fd5a : dxgmms1!VidSchiWorkerThread+0xe6fffff880`06297c10 fffff802`ee75d7e6 : fffff880`00a5e180 fffffa80`067c4700 fffff880`00a69e40 fffffa80`06700040 : nt!PspSystemThreadStartup+0x59fffff880`06297c60 00000000`00000000 : fffff880`06298000 fffff880`06292000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND: kbFOLLOWUP_IP:dxgmms1!VIDMM_PROCESS_HEAP::Reset+12dfffff880`04253d2d 81fb10011ec0 cmp ebx,0C01E0110hSYMBOL_STACK_INDEX: 7SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Reset+12dFOLLOWUP_NAME: MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME: dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP: 50eceb02FAILURE_BUCKET_ID: X64_AV_dxgmms1!VIDMM_PROCESS_HEAP::Reset+12dBUCKET_ID: X64_AV_dxgmms1!VIDMM_PROCESS_HEAP::Reset+12dFollowup: MachineOwner--------- Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 Second Dump File: Primary Analysis Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)Online Crash Dump Analysis ServiceSee http://www.osronline.com for more informationWindows 8 Kernel Version 9200 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9200.16628.amd64fre.win8_gdr.130531-1504Machine Name:Kernel base = 0xfffff802`d4e13000 PsLoadedModuleList = 0xfffff802`d50dfa20Debug session time: Tue Oct 1 16:12:31.846 2013 (UTC - 4:00)System Uptime: 0 days 3:41:37.466******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff802d4e6751d, Address of the instruction which caused the bugcheckArg3: fffff88009ee5c20, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP:nt!SwapContext_PatchXRstor+0fffff802`d4e6751d 0fae29 xrstor [rcx]CONTEXT: fffff88009ee5c20 -- (.cxr 0xfffff88009ee5c20)rax=0000000000000005 rbx=fffff88001c5e180 rcx=fffff88009ee6cc0rdx=0000000000000000 rsi=fffffa800dfbfa40 rdi=fffffa800db29400rip=fffff802d4e6751d rsp=fffff88009ee6620 rbp=fffff88009ee6c90r8=0000000000000000 r9=0000000000000008 r10=0000000000000000r11=0000000000000040 r12=0000000000000001 r13=0000001ef681052br14=fffffa800c869080 r15=fffff88001c63dc0iopl=0 nv up ei pl nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210206nt!SwapContext_PatchXRstor:fffff802`d4e6751d 0fae29 xrstor [rcx]Resetting default scopeCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTBUGCHECK_STR: 0x3BPROCESS_NAME: explorer.exeCURRENT_IRQL: 2LAST_CONTROL_TRANSFER: from fffff802d4e67106 to fffff802d4e6751dSTACK_TEXT:fffff880`09ee6620 fffff802`d4e67106 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXRstorfffff880`09ee6660 fffff802`d4eb07cb : 00000000`00000000 00000000`00000000 fffff802`00000002 fffff880`01c5e100 : nt!KiSwapContext+0x76fffff880`09ee67a0 fffff802`d4ea55a6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x23bfffff880`09ee6860 fffff802`d5251d3c : fffffa80`0ccdae80 fffffa80`0dfbfa01 00000000`00000001 00000000`0adef800 : nt!KeRemoveQueueEx+0x296fffff880`09ee6910 fffff802`d4eb3355 : fffffa80`0ccdae80 00000000`05d36d60 fffff880`09ee6a40 00000018`000f00ff : nt!IoRemoveIoCompletion+0x4cfffff880`09ee69a0 fffff802`d4e6c453 : 000000fa`0000019c 00000000`05d36d60 00000000`00000010 00000000`0adef830 : nt!NtWaitForWorkViaWorkerFactory+0x295fffff880`09ee6b00 000007fc`56d146ab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0adef7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fc`56d146abFOLLOWUP_IP:nt!SwapContext_PatchXRstor+0fffff802`d4e6751d 0fae29 xrstor [rcx]SYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!SwapContext_PatchXRstor+0FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP: 51a966cdSTACK_COMMAND: .cxr 0xfffff88009ee5c20 ; kbFAILURE_BUCKET_ID: X64_0x3B_nt!SwapContext_PatchXRstor+0BUCKET_ID: X64_0x3B_nt!SwapContext_PatchXRstor+0Followup: MachineOwner--------- Link to comment Share on other sites More sharing options...
Astra.Xtreme Posted October 1, 2013 Share Posted October 1, 2013 Right now tried what you have said, and the PC loaded fine each time. There's a program called Memtest86 which will scan the RAM for errors. Give that a shot and see if anything comes up. Link to comment Share on other sites More sharing options...
sc302 Veteran Posted October 1, 2013 Veteran Share Posted October 1, 2013 looks like it is memory related...but it seems you already know it. Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 There's a program called Memtest86 which will scan the RAM for errors. Give that a shot and see if anything comes up. Running the test. Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 looks like it is memory related...but it seems you already know it. Nope? Link to comment Share on other sites More sharing options...
sc302 Veteran Posted October 1, 2013 Veteran Share Posted October 1, 2013 Are you overclocking? If you are bring it back to normal. Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 Are you overclocking? If you are bring it back to normal. No overclocking. Link to comment Share on other sites More sharing options...
sc302 Veteran Posted October 1, 2013 Veteran Share Posted October 1, 2013 Keep running memtest for at least. 8hrs Link to comment Share on other sites More sharing options...
44MLX Posted October 1, 2013 Author Share Posted October 1, 2013 Keep running memtest for at least. 8hrs Jeez 8 hours? Link to comment Share on other sites More sharing options...
+jamesyfx Subscriber² Posted October 1, 2013 Subscriber² Share Posted October 1, 2013 The test needs to be thorough but to be honest if you're having BSOD's every time you boot the PC the errors should typically flag up quickly. I generally run 2 complete passes of Memtest if I've a suspicion that there is a problem with my RAM. Link to comment Share on other sites More sharing options...
vcfan Posted October 1, 2013 Share Posted October 1, 2013 looks graphics related. update your graphics driver. if on the latest one, try an earlier version. if no change, reseat your cpu. xendrome 1 Share Link to comment Share on other sites More sharing options...
44MLX Posted October 2, 2013 Author Share Posted October 2, 2013 The test needs to be thorough but to be honest if you're having BSOD's every time you boot the PC the errors should typically flag up quickly. I generally run 2 complete passes of Memtest if I've a suspicion that there is a problem with my RAM. After seven hours this is what it looked like. http://s18.postimg.org/v3c1nbe0p/IMG_0120.jpg looks graphics related. update your graphics driver. if on the latest one, try an earlier version. if no change, reseat your cpu. My graphics card driver is the latest. Link to comment Share on other sites More sharing options...
spaceelf Posted October 2, 2013 Share Posted October 2, 2013 Is your RAM 1.65v? I can't speak for the newer Core models but afaik Intel chips do not like 1.65v. Link to comment Share on other sites More sharing options...
44MLX Posted October 2, 2013 Author Share Posted October 2, 2013 Is your RAM 1.65v? I can't speak for the newer Core models but afaik Intel chips do not like 1.65v. Not sure how would I find out? Link to comment Share on other sites More sharing options...
Recommended Posts