BSOD problems :(
- Thread starter Armadillo
- Start date
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
One from the 10th
. 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
---------
Last edited:
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.
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.
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?
(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?
Last edited:
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.
Was set at 1.65V, rated max for them modules.
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
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
Could just be the ram needed more voltage, My XMS3 with 4 sticks (8GB) I have to set voltage manually up to 1.7v or it would BSOD but within windows its showing 1.65v not 1.7v so could be your board is not putting out as much power as it says it is!