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

.

Ohlawll · 20 Feb 2012 at 22:44

Have you tried reinstalling windows at all? If your sure its not hardware related then its either a conflict or corruption in windows

. I would also try running a hdtune error scan on the hdd.

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

.

Raumarik · 26 Feb 2012 at 14:45

Graphics card possibly? I can't remember off hand but I don't think prime or memtest check the card.

It could even just be driver related, I'd drop back to an older version or even use the PC for a few days without the card (assuming you have an alternate graphics card you can use.)

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

.

Pho · 27 Feb 2012 at 00:25

Post the full logs (including !analyze -v) and I'll take a look.

Put them in code blocks to stop the forums messing up the formatting though.

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

.

Pho · 27 Feb 2012 at 22:52

Hmm I don't know off hand. When you say the HDD passes the health tests, is this with the manufacturer's tools?

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.

wazza300 · 27 Feb 2012 at 23:14

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

Pho · 27 Feb 2012 at 23:18

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

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

wazza300 · 27 Feb 2012 at 23:33

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

Pho · 27 Feb 2012 at 23:49

I think wazza300 could be right, Microsoft suggest SYSTEM_SERVICE_EXCEPTION could be down to video drivers, and nvlddmkm is an nVidia error. Might be worth trying another card if you can, or newer (beta) drivers or even older drivers.

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.

Pho · 27 Feb 2012 at 23:52

Have you tried disabling automatically turning your monitors off? Just hit the switch manually

.

wazza300 · 27 Feb 2012 at 23:55

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

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.