Windows 8 BSOD 0x133

carrollj87 · Mar 7, 2013

Within the past couple of days I've been getting a BSOD 0x133 DPC_WATCHDOG_VIOLATION error. This just started happening, it's been rock solid for about 2 months on Windows 8 Professional, and for about 1 1/2 years prior to that on Windows 7. I don't believe there were any driver updates at the time it started happening, though I have tried both rolling back some drivers, and updating them. I have a Dell XPS 17, Core i7 2630QM, 8GB RAM, 128GB Samsung 830 SSD. I checked, and the SSD does have the latest firmware. I tried running the driver verifier but I am getting a BSOD on startup after rebooting. I have the contents of the MINIDUMP folder attached, let me know if you need anything else, or if I missed something.

Thank you
View attachment minidump.zip

usasma · Mar 7, 2013

Please provide this information so we can provide a complete analysis: https://www.sysnative.com/forums/bs...d-posting-instructions-windows-8-7-vista.html

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
~~- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)~~
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.

Driver Verifier memory dump blames uim_vimx64 - a component of a Paragon product. Most likely to be Paragon Backup, although it could be a part of Magic ISO. Please:
- turn off Driver Verifier
- uninstall the program
- test for further BSOD's (make sure that Driver Verifier is off)
If you've stopped the BSOD's, please feel free to download a fresh copy of the latest, Win8 compatible software in order to reinstall the program.

Interestingly, the memory dump before this blamed your video drivers. If the BSOD's haven't stopped - please uninstall your current video drivers, then download and install a fresh copy from World Leader in Visual Computing Technologies | NVIDIA

Should that not stop the BSOD's, then start with these free diagnostics: Hardware Diagnostics Please be sure to run all of the video tests as the video sub-system was involved.

Please be sure to update your Norton/Symantec product as at least one of it's drivers dates from 2009. This will be an update of the program itself - NOT an update of the virus definitions.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

symsnap.sys Tue Sep 15 17:02:11 2009 (4AB000D3)
StorageCraft Volume Snap-Shot or Symantec/Norton Backup Exec
http://www.carrona.org/drivers/driver.php?id=symsnap.sys

GenericMount.sys Mon Jan 18 08:50:40 2010 (4B546730)
GenericMount Helper Service - Part of Symantec
http://www.carrona.org/drivers/driver.php?id=GenericMount.sys

qicflt.sys Thu Jul 1 21:46:34 2010 (4C2D44FA)
QicFilterDriver-64Bits from Quanta Computer/Dell Webcam Driver
http://www.carrona.org/drivers/driver.php?id=qicflt.sys

HECIx64.sys Tue Oct 19 19:33:43 2010 (4CBE2AD7)
Intel Management Engine Interface
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys

NETwNs64.sys Thu Oct 6 10:45:03 2011 (4E8DBEEF)
Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7
http://www.carrona.org/drivers/driver.php?id=NETwNs64.sys

Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
Realtek PCI/PCIe Adapters
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

btmhsf.sys Wed Nov 2 08:26:12 2011 (4EB136E4)
Intel Proset Bluetooth HighSpeed Filter Driver
http://www.carrona.org/drivers/driver.php?id=btmhsf.sys

iBtFltCoex.sys Fri Dec 9 14:45:13 2011 (4EE26549)
Intel Centrino Wireless (Bluetooth Adapter driver
http://www.carrona.org/drivers/driver.php?id=iBtFltCoex.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Mar  7 02:10:54.216 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030713-11593-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 0:00:07.996[/B]
*** WARNING: Unable to verify timestamp for uim_vimx64.sys
*** ERROR: Module load completed but symbols could not be loaded for uim_vimx64.sys
Probably caused by :[B]uim_vimx64.sys ( uim_vimx64+182be )[/B]
BugCheck [B]C4, {e1, fffff98001442f9c, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C4]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 00000000000000e1, Synchronization object address is bogus or pageable.
Arg2: fffff98001442f9c, Synchronization object address.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_e1
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0xc4_e1_VRF_uim_vimx64+182be[/B]
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar  7 01:26:15.469 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030713-8843-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 0:36:46.172[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13cdc )[/B]
BugCheck [B]133, {1, 780, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above. The offending component can usually be
	identified with a stack trace.
Arg2: 0000000000000780, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  ieutil.exe
FAILURE_BUCKET_ID: [B]0x133_ISR_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
  BIOS Version                  A19
  BIOS Release Date             09/07/2012
  Manufacturer                  Dell Inc.         
  Product Name                  Dell System XPS L702X
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Thu Mar  7 02:10:54.216 2013 (UTC - 5:00)**************************
[COLOR=RED][B]symsnap.sys                 Tue Sep 15 17:02:11 2009 (4AB000D3)[/B][/COLOR]
stdcfltn.sys                Fri Jul 13 19:30:14 2012 (5000AF86)
dump_storahci.sys           Wed Jul 25 22:30:35 2012 (5010ABCB)
uimx64.sys                  Thu Nov 22 07:07:52 2012 (50AE1598)
UimFIO.SYS                  Thu Nov 22 07:07:54 2012 (50AE159A)
Uim_IMx64.sys               Thu Nov 22 07:07:58 2012 (50AE159E)
uim_vimx64.sys              Thu Nov 22 07:08:04 2012 (50AE15A4)
VBoxNetFlt.sys              Wed Dec 19 08:47:16 2012 (50D1C564)
VBoxUSBMon.sys              Wed Dec 19 08:47:17 2012 (50D1C565)
VBoxNetAdp.sys              Wed Dec 19 08:47:17 2012 (50D1C565)
VBoxDrv.sys                 Wed Dec 19 08:48:25 2012 (50D1C5A9)
nvpciflt.sys                Fri Jan 25 04:29:40 2013 (51025084)
nvkflt.sys                  Fri Jan 25 04:29:51 2013 (5102508F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar  7 01:26:15.469 2013 (UTC - 5:00)**************************
[COLOR=RED][B]GenericMount.sys            Mon Jan 18 08:50:40 2010 (4B546730)[/B][/COLOR]
[COLOR=RED][B]qicflt.sys                  Thu Jul  1 21:46:34 2010 (4C2D44FA)[/B][/COLOR]
[COLOR=RED][B]HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)[/B][/COLOR]
[COLOR=RED][B]NETwNs64.sys                Thu Oct  6 10:45:03 2011 (4E8DBEEF)[/B][/COLOR]
[COLOR=RED][B]Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)[/B][/COLOR]
[COLOR=RED][B]btmhsf.sys                  Wed Nov  2 08:26:12 2011 (4EB136E4)[/B][/COLOR]
[COLOR=RED][B]iBtFltCoex.sys              Fri Dec  9 14:45:13 2011 (4EE26549)[/B][/COLOR]
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
ST_Accel.sys                Fri Jul 13 19:30:18 2012 (5000AF8A)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
igdkmd64.sys                Wed Dec 12 19:42:26 2012 (50C92472)
nvlddmkm.sys                Thu Feb 28 01:43:51 2013 (512EFCA7)
nvpciflt.sys                Thu Feb 28 01:44:16 2013 (512EFCC0)
[/font]

Windows 8 BSOD 0x133

carrollj87

New member

usasma

Retired Admin