BSOD DPC_WatchDog_Violation

This machine recently updated to 8.1, ever since then I get the BSOD many times a day. I have looked at the mini dump file but cannot locate how to fix this issue. The mini dumb file states the following:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040914-23218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *

These crashes were related to memory corruption (probably caused by a driver).
Please run this test to find which driver is causing the problem.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
Driver verifier (for complete directions see our wiki here)
Co-Authored by JMH3143
Drivers needing updating
mdmxsdk.sys 6/19/2006 5:27:26 PM fffff800`036bc000 fffff800`036c0280 0x449716be 0x00004280
CAX_DP.sys 2/13/2009 5:18:25 PM fffff800`01e6d000 fffff800`01fe1000 0x4995e3a1 0x00174000
CAX_CNXT.sys 2/13/2009 5:19:32 PM fffff800`02036000 fffff800`02101000 0x4995e3e4 0x000cb000
CAXHWBS2.sys 2/13/2009 5:21:18 PM fffff800`01c00000 fffff800`01c70000 0x4995e44e 0x00070000
XAudio64.sys 4/29/2009 2:21:07 PM fffff800`03bba000 fffff800`03bc2000 0x49f89a93 0x00008000
nvstor64.sys 6/22/2009 6:23:37 PM fffff800`00758000 fffff800`00796000 0x4a400469 0x0003e000
RTKVHD64.sys 8/4/2009 5:50:52 AM fffff800`030b3000 fffff800`03293400 0x4a78047c 0x001e0400
mctkmdldr64.sys 4/8/2011 4:35:33 AM fffff800`011ee000 fffff800`011f6000 0x4d9ec8d5 0x00008000
netr7364.sys 10/4/2011 2:14:37 AM fffff800`034ee000 fffff800`035a7000 0x4e8aa44d 0x000b9000
nvlddmkm.sys 12/7/2012 3:34:03 AM fffff800`022a8000 fffff800`02fb0000 0x50c19beb 0x00d08000
epfwwfpr.sys 12/17/2012 2:36:23 AM fffff800`034ac000 fffff800`034d1000 0x50cebd67 0x00025000
eamonm.sys 12/17/2012 2:39:45 AM fffff800`0163c000 fffff800`0175d000 0x50cebe31 0x00121000
ehdrv.sys 12/17/2012 2:41:16 AM fffff800`0176e000 fffff800`01798000 0x50cebe8c 0x0002a000
How To Find Drivers:
Search Google for the name of the driver
Compare the Google results with what's installed on your system to figure out which device/program it belongs to
Visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
If there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program
The most common drivers are listed on these pages:
http://www.carrona.org/dvrref.php
http://sysnative.com/drivers/
Driver manufacturer links are on this page: http://www.carrona.org
Wanikiya and Dyami--Team Zigzag
Ok I did what you said and ran the driver verifier, went to restart my pc and it has to install updates on startup now. The problem is that it cannot get thru updates to turn on, it gets to 80% then crashes with the error: KMODE_EXCEPTION_NOT_HANDLED

Similar Messages

Windows 8.1 Pro DPC_WATCHDOG_VIOLATION BSOD

I built a PC a few months ago, and recently decided to move to Windows 8. I had a Windows 8 upgrade key, so I had to go through Windows 8 before I could move to 8.1. Before I could upgrade to 8.1, I needed my Ethernet driver updated, because W8 does not
have the proper Intel I217-V driver. I downloaded the latest driver off of the internet, and when I went to install it, every time just before the installation finished, I got a BSOD (DPC_WATCHDOG_VIOLATION). I had to install the drivers off the CD. I upgraded
to Windows 8.1, and updated the drivers without a problem. But now, every once in a while, I get the same BSOD in the Windows 8.1 login screen. I have uploaded the dump file to SkyDrive.
http://sdrv.ms/Ml26aW

D4
This one was related to a known problem with LogMeIn Hamachi Virtual Miniport Driver. Driver Update Site: https://secure.logmein.com/products/ios/
Their 1/23/2014 driver (which is your date) is buggy. I suggest you contact them for a patch, beta, or work around or wailing that revert to an older driver until they figure it out
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\013014-6031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff802`a1674000 PsLoadedModuleList = 0xfffff802`a1938990
Debug session time: Thu Jan 30 09:32:29.245 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:21.933
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 44, {ffffe00003338db0, f8a, 0, 0}
*** WARNING: Unable to verify timestamp for Hamdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for Hamdrv.sys
Probably caused by : Hamdrv.sys ( Hamdrv+1f0a )
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffe00003338db0, Address of the IRP
Arg2: 0000000000000f8a
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
IRP_ADDRESS: ffffe00003338db0
FOLLOWUP_IP:
Hamdrv+1f0a
fffff800`01985f0a ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
DEVICE_OBJECT: ffffe00001fcb9e0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff802a17fcb4b to fffff802a17c1ca0
STACK_TEXT:
ffffd000`22bc9818 fffff802`a17fcb4b : 00000000`00000044 ffffe000`03338db0 00000000`00000f8a 00000000`00000000 : nt!KeBugCheckEx
ffffd000`22bc9820 fffff800`01985f0a : 00000000`00000000 ffffd000`2256bb00 ffffe000`01f6db80 ffffe000`01f6db80 : nt! ?? ::FNODOBFM::`string'+0x2a9ab
ffffd000`22bc9930 00000000`00000000 : ffffd000`2256bb00 ffffe000`01f6db80 ffffe000`01f6db80 ffffd000`00000020 : Hamdrv+0x1f0a
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Hamdrv+1f0a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Hamdrv
IMAGE_NAME: Hamdrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52e10c23
FAILURE_BUCKET_ID: 0x44_Hamdrv+1f0a
BUCKET_ID: 0x44_Hamdrv+1f0a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x44_hamdrv+1f0a
FAILURE_ID_HASH: {af270f7d-2329-db64-39cf-85dffdd63412}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

DPC_WATCHDOG_VIOLATION Help!

I'm having bsod lately while playing games and weird thing is it's only happens to some games only by far it only happens to The Wolf Among Us and The Walking Dead Season 2 which are telltale games and whenever I play them they freeze and the BSOD DPC_WATCHDOG_VIOLATION
but what's bugging me is it's never happened to me while I'm playing TWD before but now after installing and playing The Wolf Among Us, both games starts freezing and THE BSOD dpc watchdog error appears.
My laptop is not SSD cause it's 1tb and it doesn't happen to other games and it ONLY happens to Telltale games :(
Please Help! (O_O)

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

GTX 980 4G OC BSoD while playing Evolve tonight DPC_WATCHDOG_VIOLATION

Caused by driver nvvad64v.sys so it was a gpu crash. How often are driver crashes related to a bad gpu? No OC and honestly I never got crashes on my old gpu until it started overheating which I fixed with custom cooling. This GPU isn't overheating at all.
The crash address was ntoskrnl.exe+153ca0

Quote from: JLio01 on 03-November-14, 13:49:23
What's the driver version?
was .16 but I did a DDU and reinstalled the latest .48 drivers. Just got done playing the game for like 3-4 hours and didn't crash at all.

Windows 8 Encore CS4 Blu-ray BSOD

I'm getting a BSOD in Encore CS4 when I try to build a blu-ray project. I have an HP laptop with an LG USB blu-ray burner. When I click build, even to build just an image, and then change from "DVD" to "Blu-Ray", there is a hang then a BSOD. My crashdump indicates that pxhlpa64.sys is the culprit.
This seems to be relevant, BUT the solution is to upgrade CS6 to new patch:
http://forums.adobe.com/message/4672190
I'm up-to-date in CS4, so that doesn't help. However, it sounds related and I'm hoping that my copy of CS4 Production Premium is still supported.
My version of pxhlpa64.sys is 3.0.78.0. WU can't find any updates as far as I can tell. I have not installed any drivers for my LG BE12LU38 Super Multi Blue, but it seems to be recognized and there are no updates via WU.
Here is my crashdump analysis:
0: kd> !analyze -v
* Bugcheck Analysis *
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
TAG_NOT_DEFINED_c000000f: FFFFF80393BA8FB0
LAST_CONTROL_TRANSFER: from fffff80393e48853 to fffff80393cee740
STACK_TEXT:
fffff803`93ba2128 fffff803`93e48853 : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx
fffff803`93ba2130 fffff803`93d19e51 : 0000034b`321b0754 fffff803`93f6a180 fffff803`93ba2290 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c4c
fffff803`93ba21b0 fffff803`93c2ae94 : ffffffff`ffd1dc08 fffff803`93c54502 fffff880`012a0740 fffff880`0318e9c0 : nt!KeUpdateRunTime+0x51
fffff803`93ba21e0 fffff803`93ce7b2e : fffff803`93ba2290 00000000`279cdae1 fffff803`93c54580 fffff880`012a0740 : hal!HalpTimerClockInterrupt+0x50
fffff803`93ba2210 fffff803`93cde643 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x1ce
fffff803`93ba23a0 fffff803`93d1b025 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x23
fffff803`93ba23d0 fffff880`01298644 : 00000000`00000000 00000000`00000000 fffff6fd`4008aa48 fffff6fb`7ea00450 : nt!KeAcquireSpinLockRaiseToDpc+0x35
fffff803`93ba2400 fffff880`01298c1d : fffffa80`0d3855c0 fffff803`93ba2559 00000000`00000006 00000000`00000005 : PxHlpa64+0x2644
fffff803`93ba2470 fffff803`93d26406 : 00000000`00000001 fffff880`06da1c00 fffffa80`10ca75b0 ffff0083`95c9c410 : PxHlpa64+0x2c1d
fffff803`93ba24f0 fffff880`00a76c92 : fffffa80`11549b18 fffffa80`0e1f9e00 fffffa80`0d4bfbf0 00000000`00000000 : nt!IopfCompleteRequest+0x446
fffff803`93ba25d0 fffff880`00a29f30 : 00000000`00000000 fffffa80`0d494400 00000000`00000000 fffffa80`0d494400 : iaStorV!ScsiPortCompleteSrb+0x31a
fffff803`93ba2690 fffff880`00a29762 : fffff803`93ba2870 00000000`00000000 00000000`00000000 fffff880`0476de14 : iaStorV!DeviceToHostCompleteRequest+0x530
fffff803`93ba27b0 fffff880`00a76959 : fffff803`93f6cf00 fffff803`93ba2ab0 fffffa80`0d488630 00000000`00019ba2 : iaStorV!AHCIFinishIntProcessing+0xea
fffff803`93ba2980 fffff803`93d15fd8 : 00000028`00000002 00000345`2a93dd9e fffffa80`0d66e010 fffff803`93ba2a00 : iaStorV!SpRequestCompleteDpc+0x45
fffff803`93ba29b0 fffff803`93d155d0 : fffff880`00a7685c 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiExecuteAllDpcs+0x198
fffff803`93ba2af0 fffff803`93d1a4ba : fffff803`93f6a180 fffff803`93f6a180 00000000`00183de0 fffff803`93fc4880 : nt!KiRetireDpcList+0xd0
fffff803`93ba2c60 00000000`00000000 : fffff803`93ba3000 fffff803`93b9d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
PxHlpa64+2644
fffff880`01298644 48b90800000080f7ffff mov rcx,0FFFFF78000000008h
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: PxHlpa64+2644
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PxHlpa64
IMAGE_NAME: PxHlpa64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 475dd06d
FAILURE_BUCKET_ID: 0x133_DPC_PxHlpa64+2644
BUCKET_ID: 0x133_DPC_PxHlpa64+2644
Followup: MachineOwner

For CS4 you must update the Roxio component http://forums.adobe.com/thread/400484
More on Encore and Roxio http://forums.adobe.com/thread/528582 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
Right click the program icon and select Run as Administrator, which is NOT the same thing as running the computer with the Administrator account, and which fixes several "odd" problems... To create a two layer DVD (or a BluRay?), you MUST have Encore set to use the Run as Administrator option
Run as Administrator http://forums.adobe.com/thread/969395
Also, for CS4, right click the program icon and see if Win8 has the same WinXP compatibility mode that is available in Win7
As far as support outside of this user to user group... I seriously doubt that Adobe will provide any help for a program that is 3 versions old, and which was written before Win8 was more than a Microsoft dream

DPC_WatchDog_Violation on Yoga 13

I updated my Yoga 13 to Windows 8.1 a couple of weeks ago.
Yesterday, suddendly, I started getting a BSOD, stating DPC_WatchDog_Violation.
The windows would load, and a few seconds later, the keyboard and touchpad would stop responding, and then I get the BSOD stating the error.
The computer restarts to the Novo Button Menu, but the keyboard doesn't respond, and I can't select any option, until shutting down and pressing the Novo button.
Non of the recovery options seem to work, and I keep getting the violation.
Why is this happening? What can I do? Do I need to send my Yoga for service?
Solved!
Go to Solution.

I have the same problem!
However I managed to make a recovery installation - shut the computer down and keep the power button pressed for about 30 seconds. When the computer boots, turn it off again. Than press the novo button and do a recovery installation (the keyboard is now working again).
Next I will try this:
http://social.technet.microsoft.com/Forums/windows/en-US/a74beaec-87af-4660-8c7f-19e8b9b23382/dpc-wa...
Otherwise it would be great to get some support from lenovo!!!

MSI GT60 0ND-250US BSOD during gaming

I've had this laptop for about 6 months now and recently (this past week) I've been having problems with it. Every time I try to play a game other than league of legends the game runs for about 30 seconds to a minute before locking up and freezing. Sometimes I get a BSOD sometimes I get the popup that says my driver has recovered from an error. I've been monitoring my CPU and GPU temps during this time and they don't even go over 80c. There's no artifacting or anything just locks up on me. Runs league of legends flawlessly, but anything else from my steam library doesn't work. The error codes have been DPC_Watchdog_Violation or VIDEO_TDR_FAILURE nvlddmkm.sys.
System Specs:
Windows 8
Intel Core i7 -3630QM
Nvidia GeForce GTX 675M / 2GB GDDR5
12GB DDRIII RAM
Please help me, I have no idea what else to do.

Try uninstalling current nvidia driver in safemode using >>Driver Fusion<< and after reboot install latest MSI one: http://www.msi.com/service/download/nbdriver-19196.html
Run Unigine Valley benchmark at ultra details and measure temps while doing it: http://unigine.com/products/valley/download/

DPC_WATCHDOG_VIOLATION (133)

hi,
I ran the CHAOS test on our driver and get DPC_WATCHDOG_VIOLATION (133).
in the stack I see tat last try is to enqueue a request to the IoDefaultQueue (from EvtIoIncallerContext):
      nt!VfIrpDatabaseCheckExFreePool+0x7d
                                        nt!VerifierExFreePoolWithTag+0x1e
                                        Wdf01000!FxTagTracker::UpdateTagHistory+0x1ae
                                        Wdf01000!FxObject::Release+0x41e3e
                                        Wdf01000!FxPkgIo::EnqueueRequest+0x26a
                                        Wdf01000!imp_WdfDeviceEnqueueRequest+0xc9
                                        myDriver!WdfDeviceEnqueueRequest+0x3d
                                        myDriver!EvtIoInCallerContext+0x551
is there any internal spinlock used by the framework to insert requests to queue? if so, how can I know which spinlocks are used and who catch them? Is there an option that another callback use the internal spinlock and for that, the enqueue is stuck?
we have in our default queue only one callback: EvtIoDefault and our queue dispach its requests as WdfIoQueueDispatchParellel, so I assume that the EvtIoDefault don't cause the enqueue to be stucked.
Any guidance how to progress with this BSOD will be very appreciated.
thanks,
Shosho
EvtIoDefault

The frame Wdf01000!FxTagTracker::UpdateTagHistory in the call stack you pasted, suggests that you have "TrackHandles" verification enabled for the driver. Tracking reference counts on WDF objects may add significant over head,
especially if enabled for all or multiple WDF object types and while running stress (CHAOS test). I'd suggest you try running the test with handle tracking disabled.
The use of TrackHandles is documented here:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff544573(v=vs.85).aspx
This blog post also has useful information relevant to this bug check code:
http://blogs.msdn.com/b/ntdebugging/archive/2012/12/07/determining-the-source-of-bug-check-0x133-dpc-watchdog-violation-errors-on-windows-server-2012.aspx

Tecra M9-136 - BSOD during Vista SP2 update

Tecra M9-136 asked this morning to update to Vista SP2 and during the process the BSOD 0x0000007E arrived. Restarted in Safe Mode and the installer continued and then finally reported that the update had failed - and reverted to SP1. This took most of the morning.
It will start in Safe Mode but on a normal boot-up, Vista SP1 gets through the fingerprint recognition and then fails with the same BSOD (it doesn't get as far as displaying the desktop).
The laptop has BIOS level 1.80. I've tried in Safe mode to install 1.90 but it tells me that the battery has insufficient charge and the power adapter isn't attached. Both untrue.
Stuck - need advice. Could this be a hard fault? Can't see how I can update anything if it's a soft fault.
thanks

The message with the BSOD mentioned checking BIOS and driver versions. Anyway, no change made to that.,
I tried System Restore but the only available restore point was the SP2 installation. I thought Vista was supposed to save a restore point every 24 hours even if nothing new had been installed.
I've now found in System Information / Windows Error Reporting several messages like this:
28/09/2009 12:08 Windows Error Reporting Fault bucket 0x7E_NULL_IP_DRVNDDM+57bd, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\Mini0928 09-04.dmp
C:\Users\me\AppData\Local\Te mp\WER-75660-0.sysdata.xml
C:\Users\me\AppData\L ocal\Temp\WER7D78.tmp.version.txt
& #x000d;
These files may be available here:
C:\Users\me\AppData\Local\Mic rosoft\Windows\WER\ReportArchive\Report06d1c4b5

Pavilion Elite e9180f freezes, crashes, BSOD

I am one of the many unhappy customers who bought this piece of junk (Pavilion Elite e9180f) and waited too long to return it because in my naivete, I thought it was some kind of simple software issue. Nope! It's definitely something wrong with the hardware, because the freezes and crashes have been happening since day 1, right when I took the thing out of the box.
Yeah, the system is fast and runs Windows Vista great, when it's actually WORKING, which is usually only guaranteed for about the first 5 minutes after you power the system on and boot windows. After that, it's just buying time before it crashes again. Forget trying to get anything done on this computer. Forget about asking this PC to play a video or music file without the files "stuttering" during playback. Even my 7 year old Sony Vaio which is running XP can handle playing an MP3 file without stuttering and crashing!
Like everyone else, the freezes and crashes happen either one of two ways:
1) The machine begins to "stutter", stutter more, then freeze/crash. When I say stutter, I mean I move the mouse, the pointer graphic will hesitate on the screen and lag behind. If you start to play a video or music file, this manifests in an audible "stutter". The stuttering gets worse and worse as minutes pass until eventually it freezes for good, blasting that 1/50th second moment of audio into infinity. You have to reboot immediately if you don't want to go deaf or be driven mad.
2) I will be doing nothing at the time (example, I close all programs out and leave Windows sitting on the main desktop screen), I'll walk out of the room for a minute, then come back and find I can't move the mouse. This system will often lock-up without any warning!
Sometimes I'll get a BSOD or error screen, sometimes I won't (in which case your only option is to do a cold re-boot.) When I do get the BSOD, the error is ALWAYS the "did not get a response from the secondary processor" yada yada. I wish HP would just admit they shipped this model out with a bad processor/motherboard/whatever and do an official recall. I have owned PCs for the last 13 years and this is the worst and most consistently disappointing experience I have ever had.
What is the hardware issue? Which part is the lemon part? The motherboard? The processor? The BSODs seem to indicate a bad processor. I do have the Pegatron Truckee version 1.03 motherboard. Is that the problem?
P.S. I have contacted HP on many occasions about this, literally stayed on the phone for hours with "customer support" (according to one HP rep, 80% of their customer service reps are based outside of the United States...good luck getting any "technical" help from them) to no avail. I did talk to one nice tech support guy in Canada who said "it sounds like your unit has a bad processor", so he had HP send me a box to ship my unit to their repair center so they can replace the processor. However, I have also had HP reps tell me it could be anything from the memory to the hard drive. Multiple HP reps claimed to me that they have "received no complaints" about this system. One guy told me he "thought he got an email last week" regarding "something" about the system, but couldn't remember what it was and he put me on hold while he searched for the email. He never found it. What a joke.
EDIT: Just to clarify, the crashing issue has been happening since day one, but initially I thought it was an issue with Vista. I had never owned or used Vista before, so I thought maybe Vista was just unstable. Nope. I know several people who own Vista and have never experienced these issues. I have downloaded every update from Microsoft/Windows Update. I have upgraded to Vista SP2 with all the latest drivers and software for all of my hardware. No luck. It is definitely a hardware issue. Thank god HP's warranty is good for 1 year (I bought my Elite in July).
Message Edited by Doonyman on 09-24-2009 02:58 AM

Unfortunately I have to add my disastrous encounter with HP's E9180F a true lemon HP is selling. I must take some responsibility for not carefully researching this model before I purchased, but I trusted the HP name and got stung- big time.
The scoundrel :
HP and its Pavilion Elite e9180f
Windows 7 64bit
motherboard - Pegatron Truckee ver 1.03
BIOS ver 5.22Intel Core i7 920 @ 2.67GHz
Memory 9206 MB Ram
As so many others have reported my HP E9180f started locking up and going to BSOD right out of the box. My first freeze-up came when I was doing the Windows update process. At first I didn't think much about it but I started getting random freezes a couple time a day. At that point I went online to see if others had experienced the same problem and perhaps had a fix. What I found was very troubling; I found extensive documentation describing my exact problems and what was really horrifying was the reports of how ridiculous HP's help services were treating people with the problem. At first I didn't totally believe what I was reading on HP's own customer forum; I do now.
·         I've went through the total recovery process three times now, HP techs have spent hours remotely running my computer, (yes it did lock up on them to)
·         I had to upgraded the BIOS. (HP tech tried, said he had, but he hadn't)
·         I was directed to clear the BIOS (luckily for me I had the tools
·         Updated all drivers again and again.
·         Next I was asked to remove the video card, memory, and motherboard power cable and reseat them. I declined because I didn't want to give HP any reason to void my HP 2 year House Call Care Pack which covers this unit. When I invited HP to send a service tech out to perform these tasks, they said that house call only covers part replacement, we weren't replacing a part. I couldn't believe what I was told. Are you feeling my frustration?
Keep in mind that each time HP requests that I make changes, they then ask me to test the system, which I did and each time with the same result, BSOD
I'm heading into my fifth week of working with HP to fix this problem. and I still haven't even been able to get my case moved up to a senior case manager, what a joke HP's help process is.
One conversation I loved was;
HP tech: "I'll have a senior case manager call you within 24 hours."
Skeptical me: "What should I do if I don't get a call?"
Silence, no response.
Me again: "What should I do if I don't get a call?"
HP tech: "That's an impossibility."
Guess what? The impossibility became reality (I bet you guessed) .
HP's last stall tactic was to have me fax them my proof of purchase and invoice and call back in 24 hours. Where have I heard that before? Apparently nothing can go forward until they receive it. So I faxed them the stuff within 10 minutes, and when I called back 24 hours later, guess what, you're right it wasn't on their system yet. I asked couldn't I be escalated to a senior case manager (it's apparent that only a senior case manager can do anything). "No," was the tech's reply, "call back again later".
Please if anyone out there knows the secrete to getting a senior case manager, or an HP tech support number here in the U.S. so I can get this thing fixed I'd love to know it.
Fast becoming HP never again.

BSOD K8N2 AMD X2 3800

Noticed problem accessing E drive = error message
tried defrag, chkdsk /f and couldn't complete
nothing before today stored in system restore
started getting BSOD IRQ_EQUAL_TO_NOT_LESS_THAN Stop 0x000000000xA
tried to start copying files from E with bsod after a 1-2 min of copy process
ran Hitachi drive diag and drive failed in basic and advanced mode
ran ontrack drive diag and drive would stop after a few min on the read test
so...thought drive was bad...copied what I could from drive and returned for warranty replacement
installed and formatted new SATA drive...copied files to E
now getting BSOD on copying all files
cannot complete virus check on any drive... bsod on all drive access after a few minutes
updated BIOS and mobo drivers
no change... did Win Repair
now computer really runs like crap...getting fail on spoolsv.exe
booted into safe mode and did virus check ccleaner and spybot check
??? should I fix ccleaner registry problems?
didn't BSOD during safe mode
went back to normal mode, same spoolsv.exe error
kept saying I need to update to sp2, but hangs during 'finishing install'
tried running sp3 candidate...hangs
what would you do?
should I give up and try to upgrade to Vista and hope it fixes everything?

Seems like your OS files have gotten corrupted - from Command Prompt try SFC /SCANNOW with the OS CD-ROM in a drive. You also need to calm down and run some basic diagnostics, e.g. memtest86+ like someone else said and then run WDC diags on your remaining drives and a full Windows scan of at least the boot drive with CHKDSK /R or "Scan for and attempt recovery of bad sectors" with the Windows scanner.
Which nForce3 driver pack are you using - the last from nVidia was 5.10 (5.11 is bad so do not use). Where did you DL the SATA/RAID drivers? If from MSI and it's the version with V5.34 NVATABUS.SYS I wouldn't use that - the 5.10 pack SATA is OK but the best SATA/IDE driver, if you must, is the V4.79 SATA-IDE which is only available as part of an aborted attempt at a unified driver pack, 6.37Beta, by nVidia... available here http://downloads.guru3d.com/nForce-6.37-Beta-Drivers-download-971.html BUT use only the drivers in the IDE folder, which you'd have to install manually. You could also do a custom remix, like I have, by replacing the IDE folders in the 5.10 pack with the ones from the 6.37Beta pack.
BTW forget about Vista with a nForce3 mbrd - nVidia has removed all "compatibility" notices and their official stance is that it(Vista+nForce3) does not work with a dual-core CPU and they will not be doing drivers.

Usb 6501 unresponsive causing BSOD(Blue Screen Error)

There are a lot posts about the same issue but mine is a little peculiar so i decided to post it.
I am using two usb DAQ in the same pc(usb-6501, usb-6001), connected to the usb port on the back. The usb-6501 is used to obtain digital inputs from read switches, Sensors through an ssr. The usb-6001 is used to control 2 double valve solenoid, 1 dc motor, 2 indicator lamps. usb-6001 is also used to read analog values of current(using hall effect sensor) and voltage(using potentiometer).
At first i was facing problems with the usb-6001(the usb-6501 was working fine at this point) resetting during operation accompanied by BSOD. Then i learned it was due to my relay, which requires 30 mA of current to switch so i used the ULN2003a to interface the usb-6001 with the relays and after that the application was running perfectly for 4 days.
Now the usb-6501 is having the same problem and when i perform "Self Test" from NI MAX it shows "Error Code:50405" and i am able to reset the device from NI MAX only sometimes, other times i would have to unplug the USB device then plug it back in. As the application is used for an automated test rig the customer is frustrated by this problem. Once the card becomes unresponsive(or after the card is reset) BSOD occours.
I have checked all the device drivers and OS for any errors but they are fine. i have even tried changing the ram to solve the BSOD with no use.
System Details:
Windows 7 SP1
NI MAX 14.0
power saving is disabled
I have attached the latest mini dump files as they might help in finding out the reason behind this problem(File extensions changed for the purpouse of uploading).
I need to know: Is there any permanent solution for this problem? and what is the reason for this problem.
Attachments:
060115-12480-01.txt ‏315 KB
053015-12324-01.txt ‏315 KB
052615-17440-01.txt ‏315 KB

Additional info : i did an analysis of the dump files and this is the result
0: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88009fe10b1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800657922e, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e8
fffff88009fe10b1
CURRENT_IRQL: 2
FAULTING_IP:
nifslk+822e
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c6b0 -- (.trap 0xfffff80000b9c6b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009fe10b2 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80000b9c8e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800657922e rsp=fffff80000b9c840 rbp=fffff88009fe10b1
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nifslk+0x822e:
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1] ds:c8e0:fffff880`09fe10b1=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003091be9 to fffff80003092640
STACK_TEXT:
fffff800`00b9c568 fffff800`03091be9 : 00000000`0000000a fffff880`09fe10b1 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c570 fffff800`03090860 : fffffa80`06adc250 fffffa80`05c3a060 fffffa80`06adc250 00000000`0000ffff : nt!KiBugCheckDispatch+0x69
fffff800`00b9c6b0 fffff880`0657922e : fffff880`05d47468 fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 : nt!KiPageFault+0x260
fffff800`00b9c840 fffff880`05d47468 : fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 : nifslk+0x822e
fffff800`00b9c848 fffff880`01d91f90 : 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 : 0xfffff880`05d47468
fffff800`00b9c850 00000000`00000000 : fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 fffff800`00b9c8e0 : nipalk+0x75f90
STACK_COMMAND: kb
FOLLOWUP_IP:
nifslk+822e
fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nifslk+822e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nifslk
IMAGE_NAME: nifslk.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 51f2daeb
FAILURE_BUCKET_ID: X64_0xD1_nifslk+822e
BUCKET_ID: X64_0xD1_nifslk+822e
Can anyone help me with what this means?

Win XP BSOD while capture video on MSI GF FX 5900XT-VTD128

Hello.
I have such a problem. While capture video (overlay mode, 720x576) very
often (but not always) Windows XP crashes on BSOD with the following error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000d1 (0xF0504000, 0x00000002, 0x00000001, 0xF7A2CE57)
nv4_mini.sys - address F7A2CE57 base at F7A1A000, datestamp 4061d74b.
My system configuration is:
Hardware: MB Epox EP-8RDA3I (latest BIOS version), CPU AMD Athlon XP 2400+,
RAM DDR PC3200 512 MB dual channel (Kingston), Video MSI GeForce FX 5900
XT-VTD 128 (VIVO, Philips SAA 7114). NO overclocking!
Software: Windows XP Prof SP1, DirectX v.9.0.b, Nvidia Nforce driver v.4.24
WHQL, Nvidia ForceWare driver v.56.72 WHQL (default settings), MSI WDM capture driver v.3.08 (late). Capture software: VirtualDUB, iuVCR and any other.
What anyone will advise me?
Thank You.
Best regards, Dmitry.

61.21 driver is a beta driver. its not 100%. wait until they release a full working driver. it will be released on http://www.nvidia.com.

MSI K7N2 Delta-ILSR (MS-6570) BSOD problems grrr

I recently purchased this board and although it is an awesome product, I'm having a problem with BSOD's when I play a game for a certain period of time
Specs:
MSI K7N2 Delta-ILSR (7.6 BIOS)
AMD Athlon XP 2800+ Barton
512MB (2x256MB) Samsung PC-2700 DDR memory (2.5-3-3-6 1T)
MSI 128MB GeForce4 Ti 4200 (4X AGP)
NVIDIA nForce on-board sound
Western Digital 80GB drive w/ 8MB cache
MSI X48 CD/CD-RW/DVD combo drive
Windows XP Professional SP1
PSU:
Turbolink 420watt (came with case)
+3.3V is 28A
+5V is 40A
+12V is 18A
So what happens is I get a STOP error during the game that shows the kmixer.sys driver as the culprit. Sometimes it's accompanied by PAGE_FAULT_IN_NON_PAGED_AREA too. I read somewhere that kmixer.sys has to do with windows audio and that it's a 3rd party driver issue or a memory issue. I'm using the latest NVIDIA 3.13 nForce platform drivers. I ran Memtest lastnight for 12 hours straight and 0 errors. I'm thinking the memory may not be compatible with the board nor dual channel, is this possible? I have also tried several different drivers for both video and chipset including MSI's own and I still get the kmixer.sys BSOD when playing games. My previous motherboard was an MSI KT3 Ultra2-R (MS-6380E) which I had no issues with. Any help would be greatly appreciated. Thank you in advance.
--Update--
I just tried to play a game with audio disabled and it crashed this time with DRIVER_IRQL_NOT_LESS_OR_EQUAL with nv4_mini.sys as the problem. My IRQ table shows some sharing, but device manager shows no conflicts.

Ok I tried running the DTM-CB3 module which is nForce2 approved at 3-4-4-11 2T timings and experienced the same result even at 2.6 and 2.7v. I tried both in dual-channel and same thing happened. However, I downloaded a program called Prime95 and ran the CPU torture test and the system returned a fatal error within the first few minutes. CPU Temp was at 57 C and the warning beep (set to 60C though) sounded intermittentley which is strange. I let it cool down then ran the torture test again and about 5min. later the system either seized completely or the program crashed. IE has also crashed randomly on me. I did this several times, before trying a different FSB/DRAM ratio. So I left the system at 200 FSB and used a 6:5 ratio so my memory was running at DDR333 and processor was a 3200+. I ran Prime95 again and the system locked up just as it did the other times. So after I did this a few times with consistent results. I went back and set the FSB to 166 and tried a 5:6 ratio so the memory was DDR400 and processor was the normal 2800+. I ran it again and to my suprise it passed all the tests and after an hour of this, I tried a game and that was perfectly fine as well. I checked the temps and CPU was only 45 C this time. So I'm thinking the processor can't handle anything above 50C or it's just plain overheating. I ordered a Thermaltake Silent Boost HSF today which is tested up to 3400+ so this should fix my problem. If not, then I'm going to replace the memory with a 512MB Geil PC3200 golden dragon dual-channel kit.

BSOD / Lock-ups with new Q9550 in P965 Platinum

MSI P965 Platinum Mobo
E6700 CPU, recently upgraded to Q9550
Zalman Cu heat sink + fan.
4GB Corsair 6400 C4 (4-4-4-12 800 MHz)
MSI 8800 GTX graphics
Auzentech Meridian sound
2 x 36GB Raptors RAID 0 (System)
2 x 250 GB Western Digital Caviar WD2500KS RAID 0 (Data)
Corsair HX620W PSU
All drives attached to the ICH8R Intel RAID controller.
BIOS: 1.8 (latest)
Vista Ultimate 32 bit SP1 + latest patches
Intel Matrix Storage Manager v8.6
Hi all,
I have run with the above hardware specification since Jan 2007 without experiencing any hardware problems at all. Two weeks ago I upgraded the CPU from an E6700 dual-core to a Q9550 quad. I was a little concerned about doing this, because the P965 supports a max FSB of 1066 and the Q9550 is rated at 1333. In any case, I Googled around and found that some flavours of the Q9550 had been tested on my mobo (http://www.cpu-upgrade.com/mb-MSI/P965_Platinum_(MS-238).html) and also MSI list the Q9550 stepping C1 as being compatible so I took the leap.
Early indications were good - Vista detected the new chip and I rebooted when prompted. However, in the space of two weeks I have experienced around one or two BSODs per day STOP 101 or 124 codes. Hmm!
I have switched back to my trusty E6700 chip and the system is then as solid as a rock. I see 3 possibilities here:
1.The Mobo website (MSI P965) lists the Q9550 stepping type C1 as being compatible. There is no mention of E0 or C0 which seem to be the other two variants. I have no idea which stepping type mine is as the product numbers for the Q9550 chips are all the same (EU80569PJ073N or BX80569Q9550) regardless of whether it is a C0, C1 or E0 stepping. Is there any way to tell which on I have - I tried with CPU-Z but didn't spot the stepping type? In any case, could this be the problem or am I off-base?
2. It's possible I have a faulty chip. How likely is this do you think? I could ask for a swap with Novatech but could be back in the same boat, and they will reject the return unless it is 'proven faulty'.
3. I need to mod the clocking on my rig to support the Q9550. If so, can anyone advise on what I should do?
I doubt the problem is caused by an OS factor as I ran some tested in an XP pre-boot environmet and still got the lock-ups.
What should I do? i don't really want to ebay the chip at say a £50 loss if i can help it.
Many thanks in advance.

Quote
I have no idea which stepping type mine is as the product numbers for the Q9550 chips are all the same (EU80569PJ073N or BX80569Q9550) regardless of whether it is a C0, C1 or E0 stepping.
No, the OEM Order Code is different, and the sSpec Number also.
Have a look at these links
Q9550=SLAWQ=C1--> http://processorfinder.intel.com/details.aspx?sSpec=SLAWQ
Q9550=SLB8V=E0 --> http://processorfinder.intel.com/details.aspx?sSpec=SLB8V

BSOD DPC_WatchDog_Violation

Similar Messages

Maybe you are looking for