NV4_disp.dll - repeatedly BSOD

Just updated (late last night)to the latest msi vga drivers, and now I I get repeatedly BSOD's stating erronous NV4_disp.dll
Tried to go back to old drivers, without any luck.
Also I have OC'ed the card to 600/300 a few days ago, but it was running smoothly until today
now whats the most likely to cause this fault, a corrupted driver or the OC?
saint

saint,
Have you tried running without overclocking?
Richard

Similar Messages

NX8600GT and nv4_disp.dll BSOD

Hey all, hope someone out there can help.
I recently built 3 PCs to exact same spec (as per my sig) except 1 runs Vista Ultimate and 2 run XP Pro.
For both the XP Pro machines we are experiencing random BSODs almost daily
This only happens when using CTRL-ALT-DEL (we are in a corporate domain) to lock screen or when XP kicks in the screen saver, but not every time C-A-D is used or screen saver kicks in.
It always reports nv4_disp.dll as the culprit and it is always a 1000008e error code
When first built the PCs were tested over a weekend using MemTest+ and overnight using Orthos and all passed.
The Vista PC does not suffer this issue.
The latest ForceWare is installed but the services and startup utilities are disabled due to the XP roaming profiles issue.
TIA
Shevek

Quote from: Bas on 03-December-07, 23:34:45
I don't think your problem is videocard related at all.
More like your system has a shortage of power, the PSU you use is very light compared to the system you have build.
However, I have no clue how Asus uses power for the board and CPU etc...so it's hard to say where the problem is.
My advice is use a far more powerful PSU and see if it solves it.
The PSU is the one which came with the Antec NSK6850 case. I'll see if I can find a spare one in the office somewhere.
My only query against this is that an identical PC running Vista (in fact drawing more power as it has an extra Raptor in it) has no issue at all.

Nv4_disp.dll BSOD on MSI TI4600

I get a BSOD after playing Everquest for over 30 mins and tehn changing to char selection screen, it refers to either "nv4_disp.dll" or "PRF_LIST_CORRUPT", it started happening after i changed from the 21.83 NVIDIA driver to the newest 30.82 (i dont get the looping error)
After having trie all sorts of things i decided to reinstall my system with a complete HD wipe, with this new system, i was stupid enough to NOT install the old 21.83 drivers, and have been unable to make them install, so i still get the BSOD on a brand new install.
I have used MSI live update so BIOS and everything is the newest possible.
my system specs are as follows
CPU: Intel P4 1.8 Ghz
MB: MSI 8xx (im at work dont remember exact model)
Sound: SBlive 5.1
RAM: 2*512 MB Kingston 1.part
Graphic Card: MSI G4 TI4600
Anyone out there that have the same problem, and/or a solution?

Oh well !
I have the problem too and I have WinXP too.
I think, the problem is not RAM but, the library nv4_disp.dll
My PC:
P4 1.8Ghz (Notrhwood)
256 DDR RAM 333Mhz
MSI G4 TI4400

5700 ultra BSOD and nv4_disp.dll

Just got a MSI 5700 Ultra yesterday and am now suffering random BSOD's (they all seem to mention NV4_disp.dll). I've reformatted the drive and done a clean install of XP Pro (with all the latest service pack stuff) and installed 53.04 detonators, to no avail.
I'm running:
2800XP Barton
ASUS A7N8X Delux Mobo
1GB 3200 Ram (TWINMOS)
I've changed most of the stuff recently(but it seemed fairly stable until I installed the 5700),
Does anyone have ideas?
Oh, I've also got a 500W PSU, so I don't think it could be a power problem.
Hope someone can help before I kick it down the stairs!!!!!
Ratchy

Added signature with PSU rating as suggested, also using detonator (forceware 53.3).
IRQ's as follows:
ISA:
0 system timer
1 keyboard
3 (COM 2)
3 (COM 1)
6 Floppy disk controller
8 System CMOS/clock
9 Microsoft ACPI
10 MPU-401 MIDI
12 PS/2 mouse
13 Numeric data processor
14 Primary IDE
15 Secondary IDE
PCI:
5 nForce PCI System Management
18 Silicon Image Sil SATAR Controller
19 GeForce FX 5700 Ultra
20 3Com Ethernet Controller
20 nForce MCP netwoking adapter
20 Standard HCD USB Host Controller
21 NVIDIA nForce MCP Audio Processing Unit
21 OHCI IEEE 1394 Controller
21 Standard HCD USB Controller
22 NVIDIA nForce Audio Codec Interface
22 Standard Enhanced PCI to USB Host Controller
Hope this helps?
Any suggestions

Last ditch effort to avoid BSOD due to nv4_disp.dll

greetings-
been reading several old posts regarding the nv4_disp.dll causing the page fault in nopaged area bsod error. i have tried all drivers- the ones on the msi cd, 1.13, 2.0, and 2.03. and have tried to emperically determine the source of the crashing.
noticed that after installing xp sp1a (needed for 2.0 and 2.03), been getting the bsod.
i've memtested my ram for 6+ hours, it's all good.
i've found that xp in fat32 fs crashes more often than in ntfs. (so no use of fat32).
i've found that the mouse cursor becomes a green glob of vertical lines whenever i play an mpeg2 video in mediaplayer9 or 8, and in both directx9 or 8. (not sure if this is a factor)
before i go back to the 1.13 nforce drivers, i'm going to test out a few configurations.
specifically:
winxp + sp1 + 2.03
winxp + sp1 + 2.00
winxp + 2.03
winxp + 2.00
last ditch effort
winxp + sp1 + 1.13
winxp + 1.13
and yes, each time will be a fresh install from a reformated HD.
questions:
what is the difference between sp1 and sp1a?
can i install 2.03 drivers without installing sp1? nvidia says that failure to do so will result in no usb 2.0 support. i don't plan on using usb 2.0.
thanks
joe

ok, bit the bullet and bought the antec true power 430. i was at the store, and i thought, well i've already spent $85 on the PSU, might as well purchase an FX 5200 and free up the 32MB shared memory. then i thought, well got the FX 5200 TRD128 with the "what looked really cool" media center deluxe 2 on the box and what the heck, i'll buy a dvd-rom so i can make full use of the media center (since i already had the TV@nywhere card). so i ended up doing a major overhaul of the computer and so far so good.
thanx for the suggestions

Bsod hardware acceleration nv4_disp.dll firefox 4.0 xp pro

hello,
if i use Firefox 4.0 on xp pro, the machine crashes very quickly.
the bsod says there's a problem with nv4_disp.dll
so i think it's cause of the hardware acceleration into firefox 4.0 that crashes windows xp cause of the nvidia driver.

Thanks for the info, I will investigate further.
I definately think it's the driver though, the RAM I use has been 100% stable with everything else. I have 640MB Kingmax PC133 SDRAM. I have tried going back to my 512MB using 2 sequential (same batch) 256MB SIMMs and that make no real difference.
The strange thing is, it will only happen once in a while, and during those occasions I am generally NOT doing anything special... I usually have around 90% resources free and 400MB or RAM free.... then BSOD.
I am hoping MSI will release another driver soon 30.81 is stable and released, so maybe that will fix my problems.

Nv4_disp.dll errors blue screen of death photoshop cs4 bridge

Sometimes, when opening psd files from bridge in cs4 I am getting the Blue Screen of Death and a message stating the cause is nv4_disp.dll errors. This started occurring a few days ago.
Environment: XP Pro, nvidia 7900 GS video card, nvidia driver version 6.14.11.9038. [ 190.38].
Anyone else experience this and has a solution?

I bet you'll sudennly get this error without doing that to cause it soon aswell. I had a very similar problem with BSoD and Nvidia display drivers on 9800GTX GPU. It started just doing it one day completely out of the blue. Unfortinatly, i'm still not sure what caused it, but it seemed when looking around the web that it was in fact faulty drivers, but not necisarily the graphics card drivers, just a conflict with them for somthing trying to work with them.
For me, i did everything under the sun and it worked.
1. Get Spybot Search & Destroy, COMODO antivirus, Windows Live Onecare 30day free trial, and scan your system with each of them. Each one for me found soemthing new which was fairly unsettling.
2. Re-install GPU drivers, re-install graphics tablet drivers if you have one, because that was thelast thing i had changed since i startd to get them, but it was a good few weeks afterwards, and it didn't fix it doing that anyway, but it may have helped somthing else work properly so just to be safe. Re-install anything you last installed, or remove it if you are willing.
3. Disk defragment, Disk Cleanup, and run Clean Up Utilities. To help track down other problems, you can also download Regmon for windows made by microsoft: http://technet.microsoft.com/en-us/sysinternals/bb896652.aspx you can see what your computer is douing in the registery. The other one to download is Filemon, which is the same thing but shows what your computer processes are doing. http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx
Good luck, but presistence in not wanting to re-install windows will overcome it evertually

[GeForce 6] NX6800GT-TD256 Freezes with "snow", nv4_disp.dll loops

I have had this card running successfully for a while now and I was surprised when it suddenly stopped working. After a very short time (particularly in games, but just as often on the desktop) the display locks up with a fine spray of snow over the screen. A few times the system goes to a blue screen saying that nv4_disp.dll is caught in an infinite loop. From what I have seen on my searches on the forums, this seems to be an overheating related problem, except that the card is stone cold to the touch (the control panel displays 72 degrees just before the crash, but that is inflated slightly apparently).
I have tried a number of approaches, including installing the 71.84 reference drivers and downclocking the card (a lot). Disabling fast writes and AGP 4 doesn't seem to help either. Nothing that I have tried seems to work, although running the card at a lower resolution (1024x768 instead of 1280x1024) seems to increase the amount of time that I get to use my computer (from about 40-100 seconds to about 5 minutes).
I have filled out an RMA form, but I don't know where to look to find the serial number, I have a fair number of options:
- The large barcode (and on the box): 4 719072009076 and 912-8966-0050410900162 (The number on the box is the same, although 912-8966-005 is repeated).
- Near the DVI and VGA plugs: 4A920100070053ZZ
- On the opposite end there are three numbers: 0064104001972, 900-10201-0007-250 E, and 600-10201-0007-210 Z.
The RMA site doesn't include this information, it only includes information on how to find the serial number on a motherboard.
Any help would be appreciated, I'll fill the RMA with all the numbers if I have to.

We've been plagued by similar problems lately, and it seems the nVidia drivers may be causing problems.
We have been using a Jaton Video118PCI-64DDRTV (or variations - basically a GeForce 4/MX440 GPU) for a few years now in our systems. Just lately we have had problems with systems freezing, or with nv4disp.dll errors etc. One fault mode is the left side of the screen is "fuzzy", while the right hand side has vertical lines on it.
Anyway, after experimenting with various drivers, including the original Jaton 2.1.8.1, the Jaton 4.x.x.x drivers currently supplied with the cards, and the fairly recent nVidia 71.84 drivers (all of which fail with at least one hardware combination), we downloaded the latest drivers from the Jaton website. These are also V71.84, but have presumably been adapted from the nVidia drivers by Jaton to suit their exact hardware configuration. So far, the Jaton drivers seem to fix the problem (but we're still testing...).
One suggested cause is that somehow the nVidia drivers are causing the GPU or other components to overheat, causing memory errors and freezing. Some of the pictures posted by emptyweevil and others suggest graphics memory errors to me.
Anyway, it might be worth trying the MSI website for better drivers, or even rolling back to the ones provided with the card.
It seems that Windoze has an appalingly rude habit of deciding that it will update drivers without notice. Unfortunately, newer ain't always better. {Anyone know how to turn this "feature" off?} So maybe the old drivers will solve the problem.
Anyway, I thought I'd share our experiences, in case it helps someone else.
Cheers

Satellite A100-998: Blue Screen error - nv4_disp.dll infinite loop

I bought this laptop a month ago and I have a serious problem with 3d applications, 3ds max and video games. I receive a blue screen saying
Error message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
nv4_disp.dll
STOP: 0x000000EA (0x8408E6B8, 0x88D33F60, 0xBAF7BCBC, 0x00000001)
(hope i noted down correctly) and it says something about "that this device caught in an infinite loop)
I downloaded the latest drivers for my nvidia display Forceware 84.68 (GeForce Go 7300, 512ram)from Toshiba but nothing changed. Any suggestions ? What is the problem? the performance is really good until the blue screen appears, so i don't see why this happens...
The laptop came with windows xp media center edition.
Thanks in advance.

> Yes, i think so, the problem is that it is not easy
> to be separated with my laptop ... especially when
> you have deadlines! I will call them tomorrow maybe
> there is a hardware problem. It happens in all 3d
> applications, and i have the most recent drivers.
Did you ever get an answer? When i took my laptop home, the first thing i did once it was setup was test various 3d programs, because i bought it to do my 3d work on as well as having something mobile for work. I got that stop error, called toshiba and was told to uninstall and reinstall the graphics driver. Sounded like a fob but i did it anyway, and it had no effect. It seems like there's nothing i can do as Nvidia says they don't support it, it's a toshiba problem, and toshiba swears it can't be their fault.
I used to see it on my desktop (before it went to computer heaven) until i updated the driver (a new one came out), and then i never got it again. From what toshiba tech support told me, it sounds like they won't be updating the driver for the go 7300 as it's regarded as too old? I'm pretty disappointed as my search of reviews of the product never revealed this flaw.
One person who i talked to advised me to disable Hardware Acceleration, but wihout that i might as well saved money and gotten a cheapy graphics card. The price difference between a notebook with this card and one with the onboard intel type was huge.
The first notebook i bought had a faulty dvd drive and i returned it for this one. I cringe at the thought of calling toshiba again and having them tell me to return it to them as if it was a hardware failure, when it sounds like a poorly written driver is causing the STOP.

Nv4_disp.dll BSOD Errors (solved by driver rollback)

http://projectm.us/murc/planetside/BSOD2.jpg It happens whenever im running a game or program that uses a lota ram. Ive completly replaced my drivers (uninstall/reinstall) and im going to try the MSI drivers, does anyone know how to fix this crap?

If you still have problems, you may want to consider the same process for the chipset drivers.
Before you consider that, also, I think we'd like to see a little more detailed spec of your system, take a look at some of the other user's signatures and create one so we don't have to keep scrolling to see what you have. You don't have to have a graphic one, simple text will do.
Also, copy and past the IRQ's from system information and post it.
It should look like this. Mind you, my workstation is not an AMD based system and the IRQ's will look totally different than that of an nForce board.
IRQ 0   System timer   OK
IRQ 1   Standard 101/102-Key or Microsoft Natural PS/2 Keyboard   OK
IRQ 4   Communications Port (COM1)   OK
IRQ 6   Standard floppy disk controller   OK
IRQ 7   Intel(R) 82801DB/DBM SMBus Controller - 24C3    OK
IRQ 8   System CMOS/real time clock   OK
IRQ 9   Microsoft ACPI-Compliant System   OK
IRQ 12   Microsoft PS/2 Port Mouse (IntelliPoint)   OK
IRQ 13   Numeric data processor   OK
IRQ 15   Secondary IDE Channel   OK
IRQ 16   NVIDIA GeForce4 MX 440   OK
IRQ 16   Intel(R) 82801DB/DBM USB Universal Host Controller - 24C2    OK
IRQ 17   SoundMAX Integrated Digital Audio   OK
IRQ 18   Intel(R) 82801DB/DBM USB Universal Host Controller - 24C7    OK
IRQ 19   Intel(R) 82801DB/DBM USB Universal Host Controller - 24C4    OK
IRQ 20   Intel(R) PRO/100 VE Network Connection   OK
IRQ 21   Silicon Image SiI 3112 SATALink Controller   OK
IRQ 23   Intel(r) 82801DB/DBM USB 2.0 Enhanced Host Controller - 24CD   OK

Repeated BSOD Problem

Hello, i have been getting BSOD repeatedly and it's always when i play video games. My laptop has been running fine for over 3 years and it just started to randomly occur. I do have my graphics card underclocked because it started to overheat years ago,
but it has always ran fine. The BSOD has persisted for the last three weeks. I tried doing a factory reset yesterday to see if it would help, but I still got a BSOD today. My laptop is a Dell XPS L502x with windows 7 64-bit. I have the dump file from when
the blue screen occurs. Any help would be greatly appreciated, let me know if you need anymore information.
Dump File : http://www.filedropper.com/120714-40575-01
Thanks

The crash was caused by NVIDIA Graphics filter driver, nvkflt.sys.
Since you have the latest NVidia Display driver installed, I would suggest that you first uninstall it, the
"clean" reinstall the same driver.
Guide on how to install the NVIDIA Display Driver under Windows 7/Windows 8.
http://nvidia.custhelp.com/app/answers/detail/a_id/2900/~/guide-on-how-to-install-the-nvidia-display-driver-under-windows-7%2Fwindows-8
If you continue to crash, navigate to "services" on your computer, stop and set the startup type for NVidia Streamer service, to "disabled".
If you still continue to crash, try and install older versions, until you find one that is stable.**Crash details and more troubleshooting tips**
BugCheck 116, {fffffa8007839010, fffff88003083010, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
Probably caused by : nvkflt.sys ( nvkflt+15010 )
Loaded symbol image file: nvkflt.sys
    Image path: \SystemRoot\system32\DRIVERS\nvkflt.sys
    Image name: nvkflt.sys
    Timestamp:        Wed Nov 12 15:36:27 2014 (5463C4CB)
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007839010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003083010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
STOP 0x116: VIDEO_TDR_ERROR troubleshooting(also
for STOP 0x117 errors
http://www.sevenforums.com/crash-lockup-debug-how/63320-stop-0x116-video_tdr_error-troubleshooting.html
Bug Check 0x116: VIDEO_TDR_ERROR.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx
Resolving stop (blue screen) errors in Windows 7.
http://windows.microsoft.com/en-us/windows7/resolving-stop-blue-screen-errors-in-windows-7

Nv4_disp.dll & Win2k/XP

This is an issue that happens with winxp/2k where the pc would lockup and restart and has to do with some driver probs.
lilt and i have these problems, i've been searching through other forums only to find ppl with the same problems and mixed not-working solutions.
Does any1 know anything about this issue?

lol! seems like im not alone ny a longshot!
Almost everyone has this problem at the viaforums.
This person has the exact same problem as me:
I am a happy owner of a Creative Geforce2 GTS. After installing win XP i started getting a nv_disp.dll error causing the pc to crash or halt. After trying several different drivers from wth 21.* or 22.* series the same error appeared a few mins/hours after booting.
The error only happened in 2D applications. I was able to play 3D games for a few hours but left on a windows desktop the machine would die at random times. After testing the tempature of the heatsink at various times heat was not to blame.

Ituneshelper.exe causing repeated BSODs

Hi. I have recently been experiencing a number of BSODs which WinCrashReport is identifying as being caused by ituneshelper.exe.
Has anybody else experienced this issue and how can i go about finding a solution for this.
Regards

Perhaps try a complete uninstall/reinstall of iTunes and related software components, as per the following document? (That should swap out all the ituneshelper.exe componentry.)
Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7

Repeated BSODs in my brand new X230 (with Windows 8)

Hello
I purchased the new X230 in early December and then went on vacation (without it) for two weeks. Thus this is really my first week using it. I've had NINE blue screens of death already, each with the term dpc_watchdog_violation. Further, my Citrix remote work-enabled system shuts down on this computer, making this computer just about useless for work purposes. I'm worried this is a lemon -- how can I have so many crashes in the first week of use? The summary of the crash events is below. Has anyone had similar problems? Has anyone had problems with rtwlane.sys on their X230s?
Thanks for your thoughts and time,
ML
On Sat 1/12/2013 7:41:48 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011213-19546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 1/12/2013 7:41:48 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: rtwlane.sys (rtwlane+0xFF204)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\drivers\rtwlane.sys
product: Realtek PCIEWireless LAN PCI-E NIC
company: Realtek Semiconductor Corporation
description: Realtek PCIE NDIS Driverr
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation ).
Google query: Realtek Semiconductor Corporation DPC_WATCHDOG_VIOLATION
On Fri 1/11/2013 7:08:31 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011113-22437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 1/11/2013 6:27:07 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011113-20000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 1/10/2013 7:25:31 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011013-19296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 1/10/2013 7:18:01 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011013-25890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 1/10/2013 6:50:59 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011013-26921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 1/10/2013 7:01:44 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\011013-73421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 1/9/2013 7:18:40 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\010913-17562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AD40)
Bugcheck code: 0x133 (0x0, 0x281, 0x280, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Solved!
Go to Solution.

Hi, MLinBerlin
I did some research on the issue on Microsoft's website and found this page explaining what a DPC_WATCHDOG_VIOLATION is. According to Microsoft, this error is normally caused by either hardware or a driver of associated hardware. For this reason, I would recommend making sure that all the drivers and BIOS are up to date to rule out any software reasons for this issue. All drivers for your system can be found here. It could possibly be hardware, but let's hope that some updates will get it running smoothly.
Good luck, and let me know how it goes
Adam
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

Why is Firefox intermittently and randumly causing NV4_DISP.DLL fault?

This fault has been going on for the last 6 months

ok, bit the bullet and bought the antec true power 430. i was at the store, and i thought, well i've already spent $85 on the PSU, might as well purchase an FX 5200 and free up the 32MB shared memory. then i thought, well got the FX 5200 TRD128 with the "what looked really cool" media center deluxe 2 on the box and what the heck, i'll buy a dvd-rom so i can make full use of the media center (since i already had the TV@nywhere card). so i ended up doing a major overhaul of the computer and so far so good.
thanx for the suggestions

NV4_disp.dll - repeatedly BSOD

Similar Messages

Maybe you are looking for