Driver giving me BSOD often when..

Hello All, for some reason i seem to get BSOD quite often when i try broadcasting with Xsplit and I checked recently what driver is causing and is nv4_disp.dll which I can't remember if is the video driver or motherboard. Every time I try to broadcast a PC game or if my PC reaches 100% CPU percent my comp would reset giving me a BSOD.

I have a good computer and ever since I installed this driver last year, I would get more BSOD more often which is weird. I wasn't sure where to put this thread/topic sorry if I didn't, if a mod can move it to the right thread I would appreciated. So is there a way to fix this? I running XP, if you need more info on my computer specs, i would be glad to respond with more info. thanks all

Driver that I notice that keeps giving the BSOD is: nv4_disp.dll I'm not sure whats going on with this driver.

 

That's the nVidia graphics driver being flagged as being at fault, update it from the nVidia site, not via MS/Windows update.

If, after updating, you get another BSOD, see if have any minidumps in C:\Windows\Minidump, copy the latest one to your Desktop, zip and attach it to your next post, I'll try to debug it for you.

How to attach items to your post.

 

Thanks Satrow, I just reinstalled the new driver a while ago from the Nvidia website and running on a Nvidia Geforce 8600 GT. I did a while new driver install by using driver sweeper and following these steps http://forums.nvidia.com/index.php?showtopic=169555&hl=

I realized after I did this and everything went good till I started to broadcast then I get this BSOD again and did notice the nv4_disp.dll coming up is the driver error.

here is the most recent minidump from BSOD that just happened at 2:47 am

 

I think the reason why I was getting BSOD from the driver is because, I would usually just install the newest drivers for my video card. So i decide to install the newest driver the right way, by following the link i provided on one of my post.

Also when I log on Windows XP is giving me a error and it says: windows cannot find 'http://wer.microsoft.com/responses/resredir.aspx?sid=10&bucket=0x50_nv4_disp%2b4edaff&State=1&ID=e7fee6ad-6d36-4f61-952b-cfc5ae0ad626&LCID=1033&OS=5.1.2600.2.00010100.3.0'.

This only started happen after I did the new fresh driver reinstall, is there a way to fix this also? thanks

 

Thanks TimW, where would I be able to download that software?

I've only gotten that error once and since i restarted my computer a few times I haven't received that error when i log in (didn't do anything and I'm not sure if it got fixed since it doesn't pop up). I was waiting on satrow to take look at the minidump I attached to my previous post.

 

CCleaner can be found here
http://majorgeeks.com/CCleaner_Standard_d5125.html

 

Thanks Komodo25, cleaning out my cookies,history etcc.. and registry.

 

The preferred version of CCleaner is the Slim one, it comes without the crapware Ask toolbar if the Ask toolbar is installed already, best to uninstall it via Add/Remove Programs, CCleaner itself is the same in both versions.

Code:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
[B]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.[/B]
Arguments:
Arg1: a5005800, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bd4ffaff, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  a5005800 

FAULTING_IP: 
nv4_disp+4edaff
bd4ffaff 660f6f06        movdqa  xmm0,xmmword ptr [esi]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  XSplit.Core.exe

LAST_CONTROL_TRANSFER:  from bd211d28 to bd4ffaff

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a7b68850 bd211d28 094b9840 a5005800 00000800 nv4_disp+0x4edaff
a7b68854 094b9840 a5005800 00000800 000800cb nv4_disp+0x1ffd28
a7b68858 a5005800 00000800 000800cb 00000000 0x94b9840
a7b6885c 00000000 000800cb 00000000 e2a17968 0xa5005800


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+4edaff
bd4ffaff 660f6f06        movdqa  xmm0,xmmword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+4edaff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c1a6

FAILURE_BUCKET_ID:  0x50_nv4_disp+4edaff

BUCKET_ID:  0x50_nv4_disp+4edaff

Followup: MachineOwner

I'd like you to test out the video RAM next using Video Memory Stress Test. Set it to save a log, post up the log once you've completed the test or the test stops at an error, please.

 

>>Excuse me for jumping in but may I ask if I should go to the nvidia or pc manufacturer's site for display drivers?
Thank you

 

>>D.
So no Dell(as the hardware guy suggested) but Nvidia site it is for drivers.
P.