Windows 8 DCP_WATCH_VIOLATION

hsarkangel · Oct 23, 2012

http://www.4shared.com/rar/49Aq3UZg/W8_online.html

My dmps,

Windows 8 PRO

SSD 60gb Corsair Sata 3, P8z77 LX, 8gb vengeance 1600, gtx 560 zotac, corsair 850w... Sorry if fault some information, 'sorry for english' blue screen is just hard.. =/

writhziden · Oct 23, 2012

I'm afraid your files are not accessible at that site. Please upload them to this site by clicking Go Advanced at the bottom of the post box, click on the paperclip seen in the image below. Upload the .rar file.

hsarkangel · Oct 23, 2012

View attachment W8.rar

Test...

Thx for fast help.

writhziden · Oct 23, 2012

I see that you have an ASUS fast USB charging application installed. Please remove that software and its drivers. I have seen BugChecks like yours caused by that application due to placing the USB ports in an unintended power state.

hsarkangel · Oct 24, 2012

you check the last file? coz That Asus charger, i Just take it 3 Days ago.

writhziden · Oct 24, 2012

The most recent crash shows it in the driver list:

Code:

[FONT=lucida]**************************Tue Oct 23 19:52:23.282 2012 (UTC - 6:00)**************************
LGVirHid.sys                Mon Nov 23 18:36:48 2009 (4B0B38B0)
LGBusEnum.sys               Mon Nov 23 18:36:48 2009 (4B0B38B0)
AsUpIO.sys                  Mon Aug  2 20:47:59 2010 (4C57835F)
ICCWDT.sys                  Wed Aug 18 02:27:45 2010 (4C6B9981)
AsIO.sys                    Mon Aug 23 19:53:02 2010 (4C7325FE)
ladfGSCamd64.sys            Mon Apr 11 12:41:01 2011 (4DA34B3D)
ladfGSRamd64.sys            Mon Apr 11 12:41:07 2011 (4DA34B43)
dtsoftbus01.sys             Wed Jul 27 08:03:42 2011 (4E301ABE)
lvrs64.sys                  Fri Aug 19 03:25:38 2011 (4E4E2C12)
lvuvc64.sys                 Fri Aug 19 03:26:11 2011 (4E4E2C33)
LHidFilt.Sys                Fri Sep  2 00:23:09 2011 (4E60764D)
LMouFilt.Sys                Fri Sep  2 00:23:15 2011 (4E607653)
RTCore64.sys                Tue Sep  6 06:24:50 2011 (4E661112)
[COLOR=red][B]AiChargerPlus.sys           Wed Apr 18 19:17:35 2012 (4F8F67AF)[/B][/COLOR]
ndisrd.sys                  Wed May 30 21:03:33 2012 (4FC6DF85)
RTKVHD64.sys                Tue Jun 12 04:02:32 2012 (4FD713B8)
nvhda64v.sys                Tue Jul  3 09:25:04 2012 (4FF30ED0)
dump_iaStorA.sys            Mon Jul  9 14:42:33 2012 (4FFB4239)
iaStorA.sys                 Mon Jul  9 14:42:33 2012 (4FFB4239)
HECIx64.sys                 Thu Jul 12 20:18:26 2012 (4FFF8572)
bxvbda.sys                  Mon Jul 23 17:30:50 2012 (500DDEAA)
evbda.sys                   Tue Jul 24 06:22:19 2012 (500E937B)
intelppm.sys                Wed Jul 25 20:26:48 2012 (5010AAE8)
xusb22.sys                  Wed Jul 25 20:26:57 2012 (5010AAF1)
Rt630x64.sys                Mon Jul 30 10:03:12 2012 (5016B040)
cpuz135_x64.sys             Sat Aug 11 01:48:20 2012 (50260E44)
nvlddmkm.sys                Tue Oct  2 12:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 21 12:47:44.106 2012 (UTC - 6:00)**************************
HECIx64.sys                 Mon Jul  2 16:14:58 2012 (4FF21D62)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Oct 15 15:45:11.997 2012 (UTC - 6:00)**************************
AtihdW86.sys                Tue Jul 17 01:34:09 2012 (50051571)
atikmpag.sys                Fri Jul 27 19:14:47 2012 (50133D07)
atikmdag.sys                Fri Jul 27 19:48:09 2012 (501344D9)
[/FONT]

hsarkangel · Oct 24, 2012

I've had other blue screens, as "irql_not_less_or_equal" and others who do not remember now, you know it can be the same program causing error?

Thanks for the help. I'm thinking of reformatting your system to install only programs I actually use.

Viva Google Translator..

writhziden · Oct 24, 2012

It's not possible to say that the ASUS Charger software is definitely the cause, but it should still be removed.

Up to you whether you want to Backup and Clean Install Windows 7.

hsarkangel · Oct 24, 2012

I'll try to reinstall the system, installing only the missing drivers and programs that I use on a daily basis. This "Asus Charger" is not the first time he brought me problems. I tried to uninstall it in the normal way, control panel, add or remove programs, but the blue screen persists.

With the new system, and few programs, if it happens again, I believe it will be easier to identify the blue screen, if it happens again.

Thank you, your help is really impressive. Maybe one day learn to identify problems and blue screens can collaborate with you all.

NOTE: which program to use to open files. Dmp?

writhziden · Oct 24, 2012

You're welcome. I am glad to help. Let us know when you have re-installed and how the system behaves after. :)

We use WinDbg, part of Windows Debugging Tools, to open .dmp files. It provides a lot more information than 3rd party programs for analyzing .dmps

hsarkangel · Nov 1, 2012

Re: New Blue Screen...

Do not know if you need another post, but I thought using an old pollute less, this time was the bsod "memory management", attachment file below.

Thanks in advance.

writhziden · Nov 2, 2012

Recommendations:

Crash provides no clues to software, so I suspect hardware is a possible problem. The most likely culprit in this case is your RAM. Test your RAM with Memtest86+ to see if you have any bad modules or slots.

In case the problem is software related, I also recommend you update/replace/remove the following drivers:

rtl8185.sys Tue Oct 6 01:10:10 2009 (4ACAED52)

rtl8185.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

LGVirHid.sys Mon Nov 23 18:36:48 2009 (4B0B38B0)
Logitech Gamepanel Virtual HID Device Driver
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys

LGBusEnum.sys Mon Nov 23 18:36:48 2009 (4B0B38B0)
Logitech Keyboard
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys

ladfGSCamd64.sys Mon Apr 11 12:41:01 2011 (4DA34B3D)
Driver for the Logitech GSeries Headset
http://www.carrona.org/drivers/driver.php?id=ladfGSCamd64.sys

ladfGSRamd64.sys Mon Apr 11 12:41:07 2011 (4DA34B43)
Driver for the Logitech GSeries Headset
http://www.carrona.org/drivers/driver.php?id=ladfGSRamd64.sys

dtsoftbus01.sys Wed Jul 27 08:03:42 2011 (4E301ABE)
Daemon Tools driver
Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys

lvrs64.sys Fri Aug 19 03:25:38 2011 (4E4E2C12)
Logitech Camera driver
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys

lvuvc64.sys Fri Aug 19 03:26:11 2011 (4E4E2C33)
Logitech USB Video Class Driver (WebCam)
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys

RTCore64.sys Tue Sep 6 06:24:50 2011 (4E661112)
RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys

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

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if possible.

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

[font=lucida console]**************************Thu Nov  1 21:25:31.978 2012 (GMT-6)**************************
[COLOR=RED][B]rtl8185.sys             Tue Oct  6 01:10:10 2009 (4ACAED52)[/B][/COLOR]
[COLOR=RED][B]LGVirHid.sys            Mon Nov 23 18:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]LGBusEnum.sys           Mon Nov 23 18:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]ladfGSCamd64.sys        Mon Apr 11 12:41:01 2011 (4DA34B3D)[/B][/COLOR]
[COLOR=RED][B]ladfGSRamd64.sys        Mon Apr 11 12:41:07 2011 (4DA34B43)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys         Wed Jul 27 08:03:42 2011 (4E301ABE)[/B][/COLOR]
[COLOR=RED][B]lvrs64.sys              Fri Aug 19 03:25:38 2011 (4E4E2C12)[/B][/COLOR]
[COLOR=RED][B]lvuvc64.sys             Fri Aug 19 03:26:11 2011 (4E4E2C33)[/B][/COLOR]
[COLOR=RED][B]RTCore64.sys            Tue Sep  6 06:24:50 2011 (4E661112)[/B][/COLOR]
[COLOR=RED][B]Rt630x64.sys            Wed Oct 19 06:12:55 2011 (4E9EBEC7)[/B][/COLOR]
intelppm.sys                Wed Jul 25 20:26:48 2012 (5010AAE8)
dump_storahci.sys           Wed Jul 25 20:30:35 2012 (5010ABCB)
cpuz135_x64.sys             Sat Aug 11 01:48:20 2012 (50260E44)
AtihdW86.sys                Tue Aug 21 20:26:37 2012 (5034435D)
atikmpag.sys                Thu Sep 27 19:12:52 2012 (5064F994)
atikmdag.sys                Thu Sep 27 20:14:57 2012 (50650821)
[/font]

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

[font=lucida console]**************************Thu Nov  1 21:25:31.978 2012 (GMT-6)**************************
Loading Dump File [C:\Documents and Settings\writh ziden\My Documents\BSODDmpFiles\hsarkangel\Minidump\Minidump\110212-8968-01.dmp]
Windows 7 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16384.amd64fre.win8_rtm.120725-1247
System Uptime:[B]1 days 3:36:53.831[/B]
BugCheck Code: [B]BugCheck 1A, {41793, fffff68000058080, 11, 10}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3672c )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff68000058080
Arg3: 0000000000000011
Arg4: 0000000000000010
BUGCHECK_STR:  0x1a_41793
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME: [B]chrome.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41793_nt!_??_::FNODOBFM::_string_+3672c[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3310[/B]
  BIOS Version                  0812
  BIOS Release Date             08/01/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

hsarkangel · Nov 3, 2012

I just make all recommended... but it came again.

writhziden · Nov 3, 2012

What were the results of the Memtest86+ diagnostics? How many passes did it run?

I see RivaTuner or MSI Afterburner installed. Please remove that software ASAP. It is known to cause problems with Windows 7 and likely Windows 8.

Crashes still point to memory as a likely suspect. They also may indicate hard disk problems. In addition to Memtest86+, I would recommend doing the following checks:

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Event Viewer. In Event Viewer, expand Windows Logs, click Application to let it load, right click Application and click Find.... Search for chkdsk or wininit to find the logs.
For any drives that do not give the message:

Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:

Windows has made corrections to the file system
after running the disk check, run the disk check again.
Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
SeaTools for Windows

SeaTools for DOS
If you have an SSD, make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
Run a system file check to check Windows for corruption:
1. Click Start Menu
2. Click All Programs
3. Click Accessories
4. Right click Command Prompt
5. Click Run as administrator
6. Type
  Code:
```
sfc /scannow
```
  and press Enter
7. Once it is complete, make note of the message. If it says Windows Resource Protection did not find any integrity violations., restart your computer and post back
8. If the message does not say Windows Resource Protection did not find any integrity violations., restart your computer and do steps 1-6 again.
9. You may need to do steps 1-6 up to three times with a restart in between each run to resolve all corrupted files.
10. If you still have corrupted files after a fourth run, post back here with the following:
  - Click Start Menu
  - Click Computer
  - Open your C: drive
  - Open Windows
  - Open Logs
  - Open CBS
  - Copy and paste CBS.log or CBS (it may not have the log extension) to a location you will remember.
  - Compress (zip) the CBS file and attach the .zip file to your next post.
Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, I recommend:
- http://windows.microsoft.com/en-US/windows/products/security-essentials coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
Make sure to update the security software before running the full scan.
Run Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find errors. You should also run it once when the system has been on for a few hours and is warm, and then run it again once the system has been off for a few hours and is cold.

Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. You may want to run both Memtest86+ and the Windows Memory Diagnostics Tool overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

Windows 8 DCP_WATCH_VIOLATION

hsarkangel

Member

writhziden

Administrator, .NET/UWP Developer

hsarkangel

Member

writhziden

Administrator, .NET/UWP Developer

hsarkangel

Member

writhziden

Administrator, .NET/UWP Developer

hsarkangel

Member

writhziden

Administrator, .NET/UWP Developer

hsarkangel

Member

writhziden

Administrator, .NET/UWP Developer

hsarkangel

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

hsarkangel

Member

Attachments

writhziden

Administrator, .NET/UWP Developer