Bluescreens, don't know what is causing.

S

shredzy

n00b
Joined
Dec 23, 2008
Messages
18
I didn't know where to put this thread so I decided to place it here due to the nv4_disp error.

've tried 3 different driver versions (181.20, 181.22, 180.48) and it hasn't solved the problem. Its really random bluescreens, I didn't get 1 bluescreen in any games for 2 days straight. Today when I was play Warcraft 3 I got a bluescreen with the same error as the other bluescreens. My CPU/RAM are stable, CPU ran prime95 for 8 hours straight with no errors and my RAM ran memtest for 6 hours straight and no errors. Here is a debug report of the minidump.

Code: 
 *******************************************************************************
*                                                                             *
*                        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: fffffffe, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: fffffffe, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  fffffffe 

FAULTING_IP: 
+fffffffffffffffe
fffffffe ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

PROCESS_NAME:  war3.exe

LAST_CONTROL_TRANSFER:  from 00000000 to fffffffe

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb4a72c98

STACK_COMMAND:  dds B4A72C98-0x20 ; kb

STACK_TEXT:  
b4a72c78  00000000
b4a72c7c  00000001
b4a72c80  e2226f7c
b4a72c84  e2224800
b4a72c88  e2007f80
b4a72c8c  00002c0e
b4a72c90  00000000
b4a72c94  bf1e2c6b nv4_disp+0x1d0c6b
b4a72c98  e222c540
b4a72c9c  e2007f80
b4a72ca0  e2223a40
b4a72ca4  e2007f80
b4a72ca8  bf1eb4c1 nv4_disp+0x1d94c1
b4a72cac  e2224800
b4a72cb0  e2007f80
b4a72cb4  e2224800
b4a72cb8  e2224800
b4a72cbc  00000000
b4a72cc0  bf1d9f58 nv4_disp+0x1c7f58
b4a72cc4  e2007f80
b4a72cc8  e2224800
b4a72ccc  00000000
b4a72cd0  e2224800
b4a72cd4  e2295efc
b4a72cd8  00000003
b4a72cdc  00000002
b4a72ce0  e2007f80
b4a72ce4  00000000
b4a72ce8  e22f71c0
b4a72cec  bf1334f6 nv4_disp+0x1214f6
b4a72cf0  00000000
b4a72cf4  00000004


FOLLOWUP_IP: 
nv4_disp+1d0c6b
bf1e2c6b ??              ???

SYMBOL_NAME:  nv4_disp+1d0c6b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  496eae28

FAILURE_BUCKET_ID:  0x50_nv4_disp+1d0c6b

BUCKET_ID:  0x50_nv4_disp+1d0c6b

Followup: MachineOwner

These bluescreens have only happened in games and are EXTREMELY random, they might happen within 2 days of each other.

Yesterday I had a bluescreen within 5 mins of playing WoW so I Loaded Optimized Defaults in BIOS to back off my overclocks. I came back into WoW and raided for about 4 hours and no bluescreens "yet", as I've said they are really random. Today I've been playing some CSS / Wacraft 3 and still haven't got a bluescreen.

I really can't find out whats causing the problem because just under a month ago I overclocked my E8400 to 4.0GHz with 1.25 volts and it ran stable in prime95 for 8 hours, my memory (4GB (2X2GB) G-Skill PI PC-8800) which I ran at 1125MHz 5-5-5-15 on memtest for 6 hours and no errors.

Please help I'm pulling my hair out :(.
 
maybe you should try driver 178.24 as well

I've had some crashing problems with 180 and 181, somehow 178 works fine

just saying it may be possible. No harm trying it out.
 
Thanks for the reply.

Yea tonight ill try putting my overclock on my CPU back to 4.0GHz and stress test, then ill try the 178 drivers I guess.

EDIT: Haven't got a bluescreen yet since I put everything to stock, but still waiting.
 
Ok I really need some help with this, I cannot pin point out this issue.

Last night I put my CPU back to 4GHz (450x9) stock volts and kept my RAM underclocked at a 1:1 ratio for the time being. Did 10 Lopps of IBT no errors and prime95 (small ftts) for about 5 hours and no errors. When I played warcraft 3 today I got a bluescreen and has the analysis as all the others.
 
Obviously it's a bad OC. Try clocking it to 3.6 and see what happens. And why do you need the cpu clocked at 4ghz to play warcraft, lol. Check your ram timings, and try using mild clocks on the ram and see if that helps.
 
Ok so even if its stable in prime95 and IBT its still a bad overclock?

Its only nv4_disp errors and its starting to shit me off so much lol.

EDIT: I got a bluescreen in CSS today with the OC
Code: 
*******************************************************************************
*                                                                             *
*                        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: c4903a0c, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf16410e, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  c4903a0c 

FAULTING_IP: 
nv4_disp+15210e
bf16410e 0000            add     byte ptr [eax],al

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

PROCESS_NAME:  hl2.exe

MISALIGNED_IP: 
nv4_disp+15210e
bf16410e 0000            add     byte ptr [eax],al

LAST_CONTROL_TRANSFER:  from bf12064b to bf16410e

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b3fc9c34 bf12064b e2007f40 00000000 e234141c nv4_disp+0x15210e
b3fc9c38 e2007f40 00000000 e234141c 000001a3 nv4_disp+0x10e64b
b3fc9c3c 00000000 e234141c 000001a3 00000000 0xe2007f40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+15210e
bf16410e 0000            add     byte ptr [eax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+15210e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_nv4_disp.dll

BUCKET_ID:  IP_MISALIGNED_nv4_disp.dll

Followup: MachineOwner
 
Thank you for the reply :).

Ok well I've sent a request to Galaxy for a RMA and ill see what happens. Hopefully its just the gfx card and they replace it for me.

Here is most of the debug report

Code: 
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {c4903a0c, 1, bf16410e, 0}


Could not read faulting driver name
Probably caused by : hardware ( nv4_disp+15210e )

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: c4903a0c, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf16410e, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  c4903a0c 

FAULTING_IP: 
nv4_disp+15210e
bf16410e 0000            add     byte ptr [eax],al

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

PROCESS_NAME:  hl2.exe

MISALIGNED_IP: 
nv4_disp+15210e
bf16410e 0000            add     byte ptr [eax],al

LAST_CONTROL_TRANSFER:  from bf12064b to bf16410e

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b3fc9c34 bf12064b e2007f40 00000000 e234141c nv4_disp+0x15210e
b3fc9c38 e2007f40 00000000 e234141c 000001a3 nv4_disp+0x10e64b
b3fc9c3c 00000000 e234141c 000001a3 00000000 0xe2007f40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+15210e
bf16410e 0000            add     byte ptr [eax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+15210e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_nv4_disp.dll

BUCKET_ID:  IP_MISALIGNED_nv4_disp.dll

Followup: MachineOwner
---------
 
You must log in or register to reply here.
Back
Top