DPC_WATCHDOG_VIOLATION + Freezes while gaming.

Serpenthebi · Dec 25, 2014

Hello everyone. I just built a gaming PC this monday and everything went as expected, nothing was wrong. I installed Win 8.1 64bit, then the drivers and everything seemed to work just fine. Nothing is overheating. The second day i was testing some games and everything seemed to work. On day three Nvidia Experience found a new driver so i downloaded it and since then i keep getting DPC_WATCHDOG_VIOLATION BSODs. Browsing the internet works fine.
So someone told me to check event viewer and it says the source is Kernel-Power and the ID is 41. I dont know what does that mean (I'm a newbie). I tried updating the drivers once again and it doesnt seem to work. Today I tried to play Dota 2 and instead of getting the BSOD it just froze. I alt tabbed out of the game and couldnt get back, had to End it in task manager. Then I tried The Crew. It froze after a minute + Black screen. Had to restart. Everything else seems stabile. I haven't tried other games.

Specs:
Cpu i5 4690k
Gpu GTX 970 Strix from Asus
Mobo MSI Z97M GAMING
RAM Hyperx Fury 8GB Kit 1866Mhz
PSU EVGA Supernova 750 B1
SSD Hyperx 3k 120GB
HDD Western Digital Caviar Blue 1TB

also sorry for my english, im not a native speaker. thanks

View attachment 55698

usasma · Dec 25, 2014

Kernel Power Event ID 41 is simply Windows' way of saying it doesn't know why it shut down. Examining the entries around it may reveal some patterns - and the absence of any pattern may suggest a hardware/overheating problem.

Please do the following:

- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here: Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012, Windows 7, or Windows Server 2008 R2

While waiting for a reply, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Also, please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):
http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html

Serpenthebi · Dec 25, 2014

View attachment 55699

Also edited my first post with the SFdebugFiles

usasma · Dec 25, 2014

Lot's of problems with the Event Viewer files - mostly nVidia and Intel Smart Connect - but there's a lot of other low-level stuff going on also. All of it occurs just before the system reboots.

Only 81 Windows Updates installed. Most systems have 100 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

This device is disabled. Is this deliberate? If so, why?

PHL 243V5-4 (NVIDIA High Definition Audio) SWD\MMDEVAPI\{0.0.0.00000000}.{AC98120A-F56D-4E23-B446-61C074B06C1D} This device is disabled.

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! :

LVUSBS64.sys Sat Feb 3 13:05:16 2007 (45C4CEDC)
Logitech Camera driver
http://www.carrona.org/drivers/driver.php?id=LVUSBS64.sys

CamDrL64.sys Sat Feb 3 13:17:27 2007 (45C4D1B7)
Logitech QuickCam Pro 3000
http://www.carrona.org/drivers/driver.php?id=CamDrL64.sys

Uninstall the Logitech QuickCam Pro 3000. I have one of these and have never been able to get it to work in Win8/8.1

Update nVidia drivers.

If BSOD's continue, please run Driver Verifier according to these instructions: Driver Verifier Settings

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Wed Dec 24 10:01:09.819 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122414-7593-01.dmp]
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Built by: [B]9600[/B].17328.amd64fre.winblue_r3.140827-1500
System Uptime:[B]0 days 0:22:13.453[/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]nvlddmkm.sys ( nvlddmkm+da200 )[/B]
BugCheck [B]133, {0, 501, 500, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_nvlddmkm+da200[/B]
CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.3
  BIOS Release Date             07/22/2014
  Manufacturer                  MSI
  Product Name                  MS-7919
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 24 08:36:10.084 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122414-8218-01.dmp]
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Built by: [B]9600[/B].17328.amd64fre.winblue_r3.140827-1500
System Uptime:[B]1 days 16:31:30.719[/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]nvlddmkm.sys ( nvlddmkm+da200 )[/B]
BugCheck [B]133, {0, 501, 500, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_nvlddmkm+da200[/B]
CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.3
  BIOS Release Date             07/22/2014
  Manufacturer                  MSI
  Product Name                  MS-7919
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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]**************************Wed Dec 24 10:01:09.819 2014 (UTC - 5:00)**************************
[COLOR=RED][B]LVUSBS64.sys                Sat Feb  3 13:05:16 2007 (45C4CEDC)[/B][/COLOR]
[COLOR=RED][B]CamDrL64.sys                Sat Feb  3 13:17:27 2007 (45C4D1B7)[/B][/COLOR]
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
agp440.sys                  Thu Aug 22 07:39:35 2013 (5215F877)
nv_agp.sys                  Thu Aug 22 07:39:38 2013 (5215F87A)
dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
imsevent.sys                Fri Jan 10 12:52:53 2014 (52D03375)
ikbevent.sys                Fri Jan 10 12:52:53 2014 (52D03375)
ISCTD.sys                   Wed Jan 22 14:37:35 2014 (52E01DFF)
e22w8x64.sys                Wed Mar 26 11:58:37 2014 (5332F92D)
INETMON.sys                 Thu Apr  3 12:50:43 2014 (533D9163)
RTKVHD64.sys                Tue Jul 15 06:53:15 2014 (53C5081B)
bwcW8x64.sys                Thu Sep 11 15:43:49 2014 (5411FB75)
nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
nvvad64v.sys                Thu Nov 20 10:33:54 2014 (546E09E2)
NvStreamKms.sys             Sat Nov 22 02:46:45 2014 (54703F65)
nvlddmkm.sys                Sat Dec 13 01:53:17 2014 (548BE25D)
nvvadarm.sys                Sat Dec 13 02:16:06 2014 (548BE7B6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 24 08:36:10.084 2014 (UTC - 5:00)**************************
ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02)
aswMonFlt.sys               Thu Nov  6 07:53:07 2014 (545B6F33)
aswRvrt.sys                 Thu Nov  6 07:53:22 2014 (545B6F42)
aswVmm.sys                  Thu Nov  6 07:53:31 2014 (545B6F4B)
aswSnx.sys                  Thu Nov  6 07:53:55 2014 (545B6F63)
aswRdr2.sys                 Thu Nov  6 07:54:02 2014 (545B6F6A)
aswHwid.sys                 Thu Nov  6 07:55:01 2014 (545B6FA5)
aswSP.sys                   Thu Nov  6 08:09:55 2014 (545B7323)
aswStm.sys                  Thu Nov  6 08:11:00 2014 (545B7364)
[/font]

Serpenthebi · Dec 25, 2014

I've done everything as you said. No more Win updates found, updated everything that was missing and uninstalled the Quickcam 3000. Tried playing Battlefield 3, no DPC_WATCHDOG_VIOLATION but it froze. I alt tabbed to desktop and ended the game from taskbar and got an interesting error.

View attachment 55705

edit: Found out that is just a Battlefield issue. Im testing Dota 2 now and everything works fine for now. Ill keep you updated on other games.

Serpenthebi · Jan 2, 2015

got DPC_WATCHDOG_VIOLATION 2 times again on Battlefield 3.

View attachment 56094

e: Dota 2 works just fine. Could it be some faultry hardware? Maybe some part cant handle the load.

usasma · Jan 4, 2015

MSI Afterburner (along with Riva Tuner and EVGA Precision) is known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately! This one last showed on 26 Dec - so if you've uninstalled it since then just let us know.

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

QuickCam drivers still showing (LVUSBS64.sys in the latest dump). Double check that they have been removed. If they have (and they show up again), I'll provide manual removal instructions.

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Fri Jan  2 17:57:49.460 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\010215-5375-01.dmp]
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 0:15:43.094[/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]nvlddmkm.sys ( nvlddmkm+da200 )[/B]
BugCheck [B]133, {0, 501, 500, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_nvlddmkm+da200[/B]
CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.3
  BIOS Release Date             07/22/2014
  Manufacturer                  MSI
  Product Name                  MS-7919
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 26 11:57:24.601 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122614-6046-01.dmp]
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Built by: [B]9600[/B].17476.amd64fre.winblue_r5.141029-1500
System Uptime:[B]0 days 20:22:42.235[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c46e )[/B]
BugCheck [B]133, {1, 1e00, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]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: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_ISR_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.3
  BIOS Release Date             07/22/2014
  Manufacturer                  MSI
  Product Name                  MS-7919
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 25 14:23:13.616 2014 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\122514-5609-01.dmp]
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Built by: [B]9600[/B].17328.amd64fre.winblue_r3.140827-1500
System Uptime:[B]0 days 1:03:06.250[/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]nvlddmkm.sys ( nvlddmkm+da200 )[/B]
BugCheck [B]133, {0, 501, 500, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_nvlddmkm+da200[/B]
CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.3
  BIOS Release Date             07/22/2014
  Manufacturer                  MSI
  Product Name                  MS-7919
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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]**************************Fri Jan  2 17:57:49.460 2015 (UTC - 5:00)**************************
[COLOR=RED][B]LVUSBS64.sys                Sat Feb  3 13:05:16 2007 (45C4CEDC)[/B][/COLOR]
ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
e22w8x64.sys                Wed Mar 26 11:58:37 2014 (5332F92D)
TeeDriverx64.sys            Mon Aug 25 17:01:32 2014 (53FBA42C)
bwcW8x64.sys                Thu Sep 11 15:43:49 2014 (5411FB75)
nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
nvvad64v.sys                Thu Nov 20 10:33:54 2014 (546E09E2)
NvStreamKms.sys             Sat Nov 22 02:46:45 2014 (54703F65)
nvlddmkm.sys                Sat Dec 13 01:53:17 2014 (548BE25D)
nvvadarm.sys                Sat Dec 13 02:16:06 2014 (548BE7B6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 26 11:57:24.601 2014 (UTC - 5:00)**************************
[COLOR=RED][B]RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Dec 25 14:23:13.616 2014 (UTC - 5:00)**************************
[COLOR=RED][B]CamDrL64.sys                Sat Feb  3 13:17:27 2007 (45C4D1B7)[/B][/COLOR]
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
imsevent.sys                Fri Jan 10 12:52:53 2014 (52D03375)
ikbevent.sys                Fri Jan 10 12:52:53 2014 (52D03375)
ISCTD.sys                   Wed Jan 22 14:37:35 2014 (52E01DFF)
INETMON.sys                 Thu Apr  3 12:50:43 2014 (533D9163)
RTKVHD64.sys                Tue Jul 15 06:53:15 2014 (53C5081B)
[/font]

Serpenthebi · Jan 4, 2015

My GPU is factory overclocked and I used MSI Afterburned to downclock it to reference speeds. If I uninstall the program will my gpu stay at those reference speeds? And can you please guide me through those drivers in red?

usasma · Jan 5, 2015

Get rid of MSI Afterburner.
I'm not familiar with overclocking video cards, but the card should come with a utility (GPU Tweak) that's used to change the overclock.

Code:
1) Create a Restore Point using System Restore
2) Create a Repair disc (Recovery Drive in Win8.1):
Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (Autoruns for Windows) and use it to disable any instances of LVUSBS64.sys and CamDrL64.sys that are starting (or any other Logitech QuickCam entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of LVUSBS64.sys and CamDrL64.sys (or any other Logitech QuickCam entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of LVUSBS64.sys and CamDrL64.sys or any other Logitech QuickCam entries are disabled.
7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (LVUSBS64.sys and CamDrL64.sys) or the program name (Logitech QuickCam). Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this).
8) Go to C:\Windows\System32\drivers and rename the LVUSBS64.sys and CamDrL64.sys drivers to LVUSBS64.BAD and CamDrL64.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).

In the event that the system doesn't boot:

1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename LVUSBS64.BAD and CamDrL64.BAD to LVUSBS64.sys and CamDrL64.sys

Code:

ren C:\Windows\System32\drivers\LVUSBS64.BAD C:\Windows\System32\drivers\LVUSBS64.sys ren C:\Windows\System32\drivers\CamDrL64.BAD C:\Windows\System32\drivers\CamDrL64.sys

2) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

DPC_WATCHDOG_VIOLATION + Freezes while gaming.

Serpenthebi

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Serpenthebi

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Serpenthebi

New Member

My Computer

System One

Serpenthebi

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

Serpenthebi

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One