New PC and 2 BSoD

[44MLX]

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) - Haswell
CPU Heatsink : Coolermaster Hyper 212 Evo - Low Noise
Memory : 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 Sound
Networking : 1 x Wireless Network Card 150Mbps (PCI-E)
Power Supply : Corsair 550W PSU - Low Noise
CPU Compound : Standard CPU Compound Supplied With Heatsink
Hard Drive #1 : 120GB Corsair Force GT SSD SATA-III, Read 550MB/s, Write 515MB/s - Silent
Hard Drive #2 : 500 GB Seagate SATA-III HDD 7200 RPM 16MB

 

Thank you.

[Mindovermaster Moderator]

What are the BSOD code numbers?

[44MLX]

What are the BSOD code numbers?

Not sure, but on the second one I managed to catch "System Service Exception".

[Mindovermaster Moderator]

In Event viewer, do you see any exclamation points?

[44MLX]

In Event viewer, do you see any exclamation points?

Nope.

[Astra.Xtreme]

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.

[sc302 Veteran]

the bsod has a dump file.  put dump file here and paste results.

http://www.osronline.com/page.cfm?name=analyze

[44MLX]

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.

[44MLX]

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?

[44MLX]

C:\Windows\Minidump

[44MLX]

First Dump File:

 

Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`ee67c000 PsLoadedModuleList = 0xfffff802`ee948a20
Debug 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 it
is 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 name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802ee9d4168
GetUlongFromAddress: unable to read from fffff802ee9d41f8
fffffa8054738ac0 Nonpaged pool

FAULTING_IP:
nt!NtUnlockVirtualMemory+33b
fffff802`ee784c4b 4c8b7e10 mov r15,qword ptr [rsi+10h]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

TRAP_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=0000000000000067
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802ee784c4b rsp=fffff88006297290 rbp=fffff880062974a0
r8=fffff6fb40000188 r9=8000000000000000 r10=0000000fffffffff
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!NtUnlockVirtualMemory+0x33b:
fffff802`ee784c4b 4c8b7e10 mov r15,qword ptr [rsi+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802ee7975a0 to fffff802ee6d6440

STACK_TEXT:
fffff880`06296f18 fffff802`ee7975a0 : 00000000`00000050 fffffa80`54738ac0 00000000`00000000 fffff880`06297100 : nt!KeBugCheckEx
fffff880`06296f20 fffff802`ee710acb : 00000000`00000000 fffffa80`54738ac0 fffffa80`067c4700 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33e2a
fffff880`06296fc0 fffff802`ee6d3eee : 00000000`00000000 00000000`00000004 00000000`06230000 fffff880`06297100 : nt!MmAccessFault+0x55b
fffff880`06297100 fffff802`ee784c4b : 00000000`00000004 fffffa80`0c61e568 00000000`0624f000 00000000`06230000 : nt!KiPageFault+0x16e
fffff880`06297290 fffff802`ee6d5453 : fffff880`00000002 fffff880`042410d9 00000000`00023c8e 00000000`00023c8e : nt!NtUnlockVirtualMemory+0x33b
fffff880`06297420 fffff802`ee6da630 : fffff880`04253d2d fffffa80`00000003 00000000`00000000 fffff880`06297600 : nt!KiSystemServiceCopyEnd+0x13
fffff880`062975b8 fffff880`04253d2d : fffffa80`00000003 00000000`00000000 fffff880`06297600 fffff8a0`09465330 : nt!KiServiceLinkage
fffff880`062975c0 fffff880`0423788a : 00000000`00020000 fffff8a0`036c85d0 00000000`06230000 fffff8a0`036c8601 : dxgmms1!VIDMM_PROCESS_HEAP::Reset+0x12d
fffff880`06297630 fffff880`0424c69f : fffff8a0`036c85d0 00000000`00000000 fffff8a0`036c85d0 00000000`00008000 : dxgmms1!VIDMM_GLOBAL::ResetBackingStore+0x1d2
fffff880`062976d0 fffff880`04242f8d : fffffa80`0a4a0000 00000000`00000000 fffff8a0`036c85d0 00000000`00000001 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0x3eb
fffff880`06297720 fffff880`0423adc6 : 00000000`c0000001 fffff880`06297860 fffff8a0`036c85d0 fffffa80`067a6750 : dxgmms1!VIDMM_GLOBAL::EvictGlobalAllocation+0x69
fffff880`06297760 fffff880`04256e02 : fffffa80`0a2d5400 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x8be
fffff880`062979d0 fffff880`04256b25 : 00000000`00000000 fffff880`00000000 fffff780`00000320 00000000`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6
fffff880`06297ba0 fffff880`04256662 : fffffa80`0bf95870 fffffa80`0ce20bc0 fffffa80`0adc9010 fffffa80`0a2d5400 : dxgmms1!VidSchiSubmitQueueCommand+0x51
fffff880`06297bd0 fffff802`ee6a8fd9 : fffffa80`067c4700 fffffa80`0a2d5400 fffff880`00a69e40 00000000`00d8fd5a : dxgmms1!VidSchiWorkerThread+0xe6
fffff880`06297c10 fffff802`ee75d7e6 : fffff880`00a5e180 fffffa80`067c4700 fffff880`00a69e40 fffffa80`06700040 : nt!PspSystemThreadStartup+0x59
fffff880`06297c60 00000000`00000000 : fffff880`06298000 fffff880`06292000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Reset+12d
fffff880`04253d2d 81fb10011ec0 cmp ebx,0C01E0110h

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Reset+12d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 50eceb02

FAILURE_BUCKET_ID: X64_AV_dxgmms1!VIDMM_PROCESS_HEAP::Reset+12d

BUCKET_ID: X64_AV_dxgmms1!VIDMM_PROCESS_HEAP::Reset+12d

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

[44MLX]

Second Dump File:

 

Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`d4e13000 PsLoadedModuleList = 0xfffff802`d50dfa20
Debug 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 bugcheck
Arg2: fffff802d4e6751d, Address of the instruction which caused the bugcheck
Arg3: fffff88009ee5c20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!SwapContext_PatchXRstor+0
fffff802`d4e6751d 0fae29 xrstor [rcx]

CONTEXT: fffff88009ee5c20 -- (.cxr 0xfffff88009ee5c20)
rax=0000000000000005 rbx=fffff88001c5e180 rcx=fffff88009ee6cc0
rdx=0000000000000000 rsi=fffffa800dfbfa40 rdi=fffffa800db29400
rip=fffff802d4e6751d rsp=fffff88009ee6620 rbp=fffff88009ee6c90
r8=0000000000000000 r9=0000000000000008 r10=0000000000000000
r11=0000000000000040 r12=0000000000000001 r13=0000001ef681052b
r14=fffffa800c869080 r15=fffff88001c63dc0
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210206
nt!SwapContext_PatchXRstor:
fffff802`d4e6751d 0fae29 xrstor [rcx]
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff802d4e67106 to fffff802d4e6751d

STACK_TEXT:
fffff880`09ee6620 fffff802`d4e67106 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXRstor
fffff880`09ee6660 fffff802`d4eb07cb : 00000000`00000000 00000000`00000000 fffff802`00000002 fffff880`01c5e100 : nt!KiSwapContext+0x76
fffff880`09ee67a0 fffff802`d4ea55a6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x23b
fffff880`09ee6860 fffff802`d5251d3c : fffffa80`0ccdae80 fffffa80`0dfbfa01 00000000`00000001 00000000`0adef800 : nt!KeRemoveQueueEx+0x296
fffff880`09ee6910 fffff802`d4eb3355 : fffffa80`0ccdae80 00000000`05d36d60 fffff880`09ee6a40 00000018`000f00ff : nt!IoRemoveIoCompletion+0x4c
fffff880`09ee69a0 fffff802`d4e6c453 : 000000fa`0000019c 00000000`05d36d60 00000000`00000010 00000000`0adef830 : nt!NtWaitForWorkViaWorkerFactory+0x295
fffff880`09ee6b00 000007fc`56d146ab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0adef7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fc`56d146ab


FOLLOWUP_IP:
nt!SwapContext_PatchXRstor+0
fffff802`d4e6751d 0fae29 xrstor [rcx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!SwapContext_PatchXRstor+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 51a966cd

STACK_COMMAND: .cxr 0xfffff88009ee5c20 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!SwapContext_PatchXRstor+0

BUCKET_ID: X64_0x3B_nt!SwapContext_PatchXRstor+0

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

[Astra.Xtreme]

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.

[sc302 Veteran]

looks like it is memory related...but it seems you already know it.

[44MLX]

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.

[44MLX]

looks like it is memory related...but it seems you already know it.

Nope?

[sc302 Veteran]

Are you overclocking? If you are bring it back to normal.

[44MLX]

Are you overclocking? If you are bring it back to normal.

No overclocking.

[sc302 Veteran]

Keep running memtest for at least. 8hrs

[44MLX]

Keep running memtest for at least. 8hrs

Jeez 8 hours?

[+jamesyfx Subscriber²]

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.

[vcfan]

looks graphics related. update your graphics driver. if on the latest one, try an earlier version.

 

if no change, reseat your cpu.

[44MLX]

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.

[spaceelf]

Is your RAM 1.65v?  I can't speak for the newer Core models but afaik Intel chips do not like 1.65v.

[44MLX]

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?