BSOD problems :(

Armadillo · 20 Feb 2012 at 19:20

My Dad's pc is having some bsod issues

. They are not frequent, but do seem to be random and the error is different every time. I've been keeping track of them this month and it's had three so far. One was on the 01/02/2012, one on 02/02/2012 and the last one was 20/02/2012. So pretty random.

Errors from bluescreen view are

01/02/2012 - KMODE_EXCEPTION_NOT_HANDLED. Bug check code 0x0000001e. Caused by driver ntoskrnl.exe, Caused by address ntoskrnl.exe+7cc40

02/02/2012- INTERRUPT_EXCEPTION_NOT_HANDLED. Bug check code 0x0000003d. Caused by driver nvlddmkm.sys. Caused by address nvlddmkm.sys+290783

20/02/2012- PAGE_FAULT_IN_NONPAGED_AREA. Bug check code 0x00000050 . Caused by driver Ntfs.sys. Caused by address Ntfs.sys+d9bb.

Haven't got the logs, but pretty much same for other months, random error and random times. Tried to solve them, but having no luck

.

System is

Gigabyte GA-770t-ud3
Athlon II x3 450, with 4th core unlocked.
4GB OCZ memory
MSI 7800GTX.

Far as I can tell, it's not hardware. I've done all the usual tests. Memory passes multiple runs of memtest. Let it run 3 times which took ages and no errors. System will happily prime as well, let it run for over 12 hours priming and no errors. So hardware is stable and they still occur when running 3 cores anyway.

All drivers are up to date.

HDD windows is on is pretty old, but passes all health tests fine, I suppose it could be an intermittent fault.

Suggestions? or any idea the cause of these bluscreens

.

Armadillo · 21 Feb 2012 at 00:03

Not tried the reinstall yet, was hoping to avoid it

. Hdtune scan on hdd comes back fine

.

Armadillo · 26 Feb 2012 at 14:35

Well this sucks

. Reinstalled windows onto another hdd just in case, was fine and thought it was sorted for a few days and just got a bsod

.
Again a random error, this time It was system service exception. Drivers, all up to date. System can prime fine for 12+ hours with no errors, memtest has been run for 3 passes ( or around 12-15 hours I think, took ages to do 4GB), all passes. Fresh install, yet still they persist.

One other thing, just from keeping my eye on it, seems it only bsod when windows loads or when windows has put monitor into standby and you wake it up (system is not hibernating, just monitor).

Is there a easy way to get more info from the dmp files than what bluscreen view gives, I see when searching some Bugcheck Analysis logs, that show more, but I have no idea how to do that or even work out the problem from it

.

Thanks

.

Armadillo · 26 Feb 2012 at 14:58

I don't have another card to test with. I could always pick a cheap second hand card to test though if I can't get to the bottom of it.

Drivers, don't think it is them as I've already tried different versions. Before the fresh install, I had older sets of drivers for everything. Motherboard, ethernet, sound and graphics. It was doing it then, so I updated them all and it was still doing it, so I went with the fresh install. It's always a different error as well

.

Armadillo · 27 Feb 2012 at 00:14

Right ran the bug check on the files and maybe hardware

1

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88008b9fd60, 0, 0, fffff880132fd783}

Probably caused by : nvlddmkm.sys ( nvlddmkm+290783 )

Followup: MachineOwner

2

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffce7fb3706939, 0, fffff80002c5812c, 7}

Could not read faulting driver name
Probably caused by : hardware ( nt!FsRtlRemovePerFileObjectContext+2c )

Followup: MachineOwner

3

....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d5e379, fffff880033bd720, 0}

Probably caused by : hardware ( nt!CmpKcbCacheLookup+6e9 )

Followup: MachineOwner

Two say hardware, one shows an nvidia file. 1&2 were dumps made before the fresh install, 3 was made on the fresh install.

I have the full logs as well that are got by !analyze -v for them three, but can't make sense of anything there

.

Armadillo · 27 Feb 2012 at 00:44

Here we go, think I done it right, so formatting should be fine

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88008b9fd60, 0, 0, fffff880132fd783}

Probably caused by : nvlddmkm.sys ( nvlddmkm+290783 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88008b9fd60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff880132fd783

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


CONTEXT:  fffff88008b9fd60 -- (.cxr 0xfffff88008b9fd60)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004c71000
rdx=0000000000000017 rsi=0000000000000000 rdi=fffffa8003a20320
rip=fffff880132fd783 rsp=fffff88008ba0740 rbp=fffff88008ba0828
 r8=0000000000000002  r9=0000000000000000 r10=0000000000800002
r11=fffff88008ba0690 r12=0000000000000000 r13=0000000000000000
r14=0000000000000002 r15=00000000ffffffff
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nvlddmkm+0x290783:
fffff880`132fd783 415d            pop     r13
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  b

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880132fd783

STACK_TEXT:  
fffff880`08ba0740 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x290783


FOLLOWUP_IP: 
nvlddmkm+290783
fffff880`132fd783 415d            pop     r13

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+290783

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7f64

STACK_COMMAND:  .cxr 0xfffff88008b9fd60 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_nvlddmkm+290783

BUCKET_ID:  X64_0x3D_nvlddmkm+290783

Followup: MachineOwner

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffce7fb3706939, 0, fffff80002c5812c, 7}


Could not read faulting driver name
Probably caused by : hardware ( nt!FsRtlRemovePerFileObjectContext+2c )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffffce7fb3706939, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c5812c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebe100
 ffffce7fb3706939 

FAULTING_IP: 
nt!FsRtlRemovePerFileObjectContext+2c
fffff800`02c5812c 848cd00900488b  test    byte ptr [rax+rdx*8-74B7FFF7h],cl

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006fa0a80 -- (.trap 0xfffff88006fa0a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800631bbb0 rbx=0000000000000000 rcx=fffffa80061de070
rdx=fffffa80043ed5b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c5812c rsp=fffff88006fa0c18 rbp=fffff88006fa0d80
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8004aaf010
r11=fffffa80057b1f10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!FsRtlRemovePerFileObjectContext+0x2c:
fffff800`02c5812c 848cd00900488b  test    byte ptr [rax+rdx*8-74B7FFF7h],cl ds:ffffce7f`b3706939=??
Resetting default scope

MISALIGNED_IP: 
nt!FsRtlRemovePerFileObjectContext+2c
fffff800`02c5812c 848cd00900488b  test    byte ptr [rax+rdx*8-74B7FFF7h],cl

LAST_CONTROL_TRANSFER:  from fffff80002c36347 to fffff80002c8bc40

STACK_TEXT:  
fffff880`06fa0918 fffff800`02c36347 : 00000000`00000050 ffffce7f`b3706939 00000000`00000000 fffff880`06fa0a80 : nt!KeBugCheckEx
fffff880`06fa0920 fffff800`02c89d6e : 00000000`00000000 ffffce7f`b3706939 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44711
fffff880`06fa0a80 fffff800`02c5812c : 00000000`00000000 fffffa80`043f9000 fffffa80`043f4010 fffffa80`043f4010 : nt!KiPageFault+0x16e
fffff880`06fa0c18 fffffa80`04aaf108 : fffff880`06fa0d80 fffffa80`061de070 00000000`00000000 fffffa80`057b1c70 : nt!FsRtlRemovePerFileObjectContext+0x2c
fffff880`06fa0c58 fffff880`06fa0d80 : fffffa80`061de070 00000000`00000000 fffffa80`057b1c70 fffffa80`043f4010 : 0xfffffa80`04aaf108
fffff880`06fa0c60 fffffa80`061de070 : 00000000`00000000 fffffa80`057b1c70 fffffa80`043f4010 fffffa80`04aaf0a0 : 0xfffff880`06fa0d80
fffff880`06fa0c68 00000000`00000000 : fffffa80`057b1c70 fffffa80`043f4010 fffffa80`04aaf0a0 00000000`00000801 : 0xfffffa80`061de070


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!FsRtlRemovePerFileObjectContext+2c
fffff800`02c5812c 848cd00900488b  test    byte ptr [rax+rdx*8-74B7FFF7h],cl

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!FsRtlRemovePerFileObjectContext+2c

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d5e379, fffff880033bd720, 0}

Probably caused by : hardware ( nt!CmpKcbCacheLookup+6e9 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80002d5e379, Address of the instruction which caused the bugcheck
Arg3: fffff880033bd720, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!CmpKcbCacheLookup+6e9
fffff800`02d5e379 00488d          add     byte ptr [rax-73h],cl

CONTEXT:  fffff880033bd720 -- (.cxr 0xfffff880033bd720)
rax=0000000000000376 rbx=0000000000000000 rcx=0000000000061085
rdx=0000000000000376 rsi=fffff880033be280 rdi=00000000ccf4be6f
rip=fffff80002d5e379 rsp=fffff880033be100 rbp=fffff8a0000231f0
 r8=0000000000000376  r9=0000000000000000 r10=0000000000000003
r11=fffff880033be280 r12=fffff8a0000237e8 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!CmpKcbCacheLookup+0x6e9:
fffff800`02d5e379 00488d          add     byte ptr [rax-73h],cl ds:002b:00000000`00000303=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!CmpKcbCacheLookup+6e9
fffff800`02d5e379 00488d          add     byte ptr [rax-73h],cl

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002d5e379

STACK_TEXT:  
fffff880`033be100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x6e9


FOLLOWUP_IP: 
nt!CmpKcbCacheLookup+6e9
fffff800`02d5e379 00488d          add     byte ptr [rax-73h],cl

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpKcbCacheLookup+6e9

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880033bd720 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

First two are from before fresh install, third is from after.

Thanks for the help

.

Armadillo · 27 Feb 2012 at 23:06

Yeah, the hdd was a seagate and I used seatools on it and also a hdtune error scan. I also changed the hdd on the new install. So the first two are from when I had windows installed on the seagate and the third one is the fresh install on a western digital drive.

Armadillo · 27 Feb 2012 at 23:28

wazza300 said:
02/02/2012- INTERRUPT_EXCEPTION_NOT_HANDLED. Bug check code 0x0000003d. Caused by driver nvlddmkm.sys. Caused by address nvlddmkm.sys+290783

not sure what the others are but thats a nvidia related error,probably drivers,others looklike memory to me but not sure

I've had multiple drivers installed and still the odd bsod. Memory appears fine as it's passed multiple runs of memtest (3 runs, 0 errors) Only other memory is what's on the card, but would have though that would cause video errors if it was going bad.

Pho said:
Could you upload that dumps so I can take a closer look?

http://www.mediafire.com/?o17hl9mfncqhj6e

Armadillo · 27 Feb 2012 at 23:50

wazza300 said:
you might have but just saying nvlddmkm is nvidia related,when does it blue screen? web browsing/gaming? random blue screens? still could be memory or cpu northbridge voltage or graphic card related

Oh right, I gathered that one was nvidia releated. Not sure what I can do about it though. Before the fresh install of windows I tried different drivers and with the fresh install, I went straight to the latest.

As for when it does it, only times I've seen it bluescreening are when the monitor wakes up and on windows load. If it does it when you wake up the monitor, by the time picture comes on it's back on the post screen (I get the bluscreen using bluescreenviewer) and the times it has done it on windows load, it gets to windows symbol, bsod, the restarts.

Timing/frequency of it, seems completely random. I did have more logs than those three (lost them unfortunately) and it's just random. One time it bsod two days in a row, then went for over a month without incident.

Armadillo · 28 Feb 2012 at 00:14

Pho said:
Have you tried disabling automatically turning your monitors off? Just hit the switch manually .

Thought about it

, but it would bug me knowing it isn't fixed and I've just worked around it

.

wazza300 said:
i dont know much about amd systems but i think you need one or two clicks more cpu nb(northbridge)voltage,if its memory it could be causing gpu drivers to crash hence the nvidia error ect

and cold start ups and s3 sleep resume/screen resume are nearly always memory related or memory to cpu(nb) related

try going back a few nvidia driver versions and see if it does it

Been in the bios and nudged it up from it's default of 1.175 to 1.2, see if it sorts it, if not I'll give it one more nudge as it'll still be in safe limits. Just have to wait and see now and hope it works

.

Thanks for the help.

Armadillo · 10 Mar 2012 at 14:28

Thought I'd leave it for a while due to the frequency of them to see if it sorted it, so updating now and unfortunately they still persist. Ran from the 28th, when I nudged the cpu-nb from default 1.175 to 1.2 until the 7th when it bsod again

. Gave it another nudge to 1.225 and it bsod again this morning

. Both were on windows load again.

Bug check from these two, in case more logs will help.

One from the 7th

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8004ee3f2e2, 8, fffff8004ee3f2e2, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44791 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8004ee3f2e2, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff8004ee3f2e2, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb1100
 fffff8004ee3f2e2 

FAULTING_IP: 
+3830616639333564
fffff800`4ee3f2e2 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800336e810 -- (.trap 0xfffff8800336e810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000048 rbx=0000000000000000 rcx=fffff8800336eb58
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004ee3f2e2 rsp=fffff8800336e9a0 rbp=0000000000000001
 r8=00000000001574c8  r9=0000000000000020 r10=fffffa8005c35860
r11=fffff8800336e9f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`4ee3f2e2 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a293bf to fffff80002a7ec40

STACK_TEXT:  
fffff880`0336e6a8 fffff800`02a293bf : 00000000`00000050 fffff800`4ee3f2e2 00000000`00000008 fffff880`0336e810 : nt!KeBugCheckEx
fffff880`0336e6b0 fffff800`02a7cd6e : 00000000`00000008 fffff800`4ee3f2e2 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0336e810 fffff800`4ee3f2e2 : 00000000`00000000 fffffa80`064e1440 fffffa80`05bbe070 fffff880`02c2c103 : nt!KiPageFault+0x16e
fffff880`0336e9a0 00000000`00000000 : fffffa80`064e1440 fffffa80`05bbe070 fffff880`02c2c103 00000000`00000000 : 0xfffff800`4ee3f2e2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+44791
fffff800`02a293bf cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+44791

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+44791

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+44791

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

One from the 10th

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff87ffc88526c, 2, 0, fffff80002a12b43}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff87ffc88526c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a12b43, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d03100
 fffff87ffc88526c 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalSendSoftwareInterrupt+b
fffff800`02a12b43 4883ec20        sub     rsp,20h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  audiodg.exe

TRAP_FRAME:  fffff880039cd530 -- (.trap 0xfffff880039cd530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffffffffffff02 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a12b43 rsp=fffff880039cd6c0 rbp=0000000000000003
 r8=000000000000000b  r9=0000000000000000 r10=fffff80002a54000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hal!HalSendSoftwareInterrupt+0xb:
fffff800`02a12b43 4883ec20        sub     rsp,20h
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad01e9 to fffff80002ad0c40

STACK_TEXT:  
fffff880`039cd3e8 fffff800`02ad01e9 : 00000000`0000000a fffff87f`fc88526c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`039cd3f0 fffff800`02acee60 : 00000000`004c5c10 00000000`00dbecc0 00000000`004b9468 fffff880`02fd3180 : nt!KiBugCheckDispatch+0x69
fffff880`039cd530 fffff800`02a12b43 : 00000000`00000202 fffff800`02ad6fbd fffff880`02fd3180 fffffa80`05c6a060 : nt!KiPageFault+0x260
fffff880`039cd6c0 fffff800`02ad6fbd : fffff880`02fd3180 fffffa80`05c6a060 fffff8a0`00760b80 fffff880`039cd900 : hal!HalSendSoftwareInterrupt+0xb
fffff880`039cd6d0 fffff800`02aaf62e : fffffa80`05c95040 00000000`00000000 00000000`00000000 fffff880`02f63180 : nt!KiDeferredReadyThread+0x2fd
fffff880`039cd750 fffff800`02ddc406 : fffffa80`05c6a168 00000000`00020000 00000000`00000000 fffffa80`05e67168 : nt!AlpcpQueueIoCompletionPort+0x30e
fffff880`039cd7d0 fffff800`02dde04e : 00000000`00020000 00000000`05e689a8 00000000`00000000 fffff880`00000000 : nt!AlpcpCompleteDispatchMessage+0x5b6
fffff880`039cd860 fffff800`02ddb94f : fffffa80`00020000 fffff8a0`02025f18 00000000`004c5c10 fffff8a0`01b54d00 : nt!AlpcpDispatchNewMessage+0x24e
fffff880`039cd8c0 fffff800`02de0526 : 00000000`000f0000 fffffa80`059c1800 00000000`004b9468 00000000`00000001 : nt!AlpcpSendMessage+0x4ad
fffff880`039cd9c0 fffff800`02dde36b : fffffa80`06167e60 00000000`00020000 00000000`004c5c10 00000000`004b9468 : nt!AlpcpProcessSynchronousRequest+0x2f3
fffff880`039cdb00 fffff800`02acfed3 : fffffa80`0612b660 fffff880`039cdca0 fffff880`039cdbc8 fffffa80`00000000 : nt!NtAlpcSendWaitReceivePort+0x1ab
fffff880`039cdbb0 00000000`7fff019f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00dbeb88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fff019f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02acee60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

Armadillo · 10 Mar 2012 at 15:07

PC doesn't really get rebooted too often, generally it gets turned on and stays on for the day, but as far as I know it is only when starting from cold it has done it. I've never seen it do it on the occasions I've told it to reboot and when it does do it, it's only the once. So boot->bsod->boot fine. I have 4GB of spare ddr3 from when I upgraded this to 8GB, that is a different brand (patriot), OCZ is in there now. So I can try that see if it fixes it.

If it does, is the ocz faulty and should try and get it replaced (which will be hard considering it passed multi memtest runs) or just not playing nice with this particular setup.

Armadillo · 10 Mar 2012 at 16:57

PSU is new. Was bought at same time as other components. Bequiet pure power 530W. So more than enough to power it.

Armadillo · 10 Mar 2012 at 17:42

Pho said:
Neither really seem to point the blame. It might be another driver somewhere not listed (though hardware is still the most obvious). Could you enable driver verifier and then do your best to try and crash the machine and upload those dumps?

(n.b. driver verified might slow your system down a little, so disable it after you've collected a few crash dumps)

edit: could you upload those last two dumps too?

I'll upload the other dumps a little later. Haven't got them stored on this machine.

I switched the memory already as it's a quick and easy change, so it's now running patriot sector 5, which was ran in this machine (also amd) for two years without issue. If it does it again, I'll enable driver verifier and try to crash it, although I'm not sure if I'll be able to do anything other than constantly restart and hope it crashes.

RevBillyG said:
What's you RAM voltage set at?
Had to up mine a touch in order for it to boot stably (ASUS M4A79XTD Evo + AMD 550 BE unlocked + OCZ RAM)

Was set at 1.65V, rated max for them modules.

Armadillo · 6 Apr 2012 at 22:27

Quick update. Since I changed the memory, no more bluescreens. Forgot to upload the last two dumps, seems a little pointless now though, although I do still have them.

So just an incompatibility? CPU/Motherboard & that memory just not playing nice, as the memory does pass multiple runs of memtest or could it still be faulty? If so how would I go about changing it as saying random bsod, but memtest passes doesn't seem like it would work as an rma reason