Nice work
sumitkm!
FYI - the PROCESS_NAME: line usually isn't significant in BSOD analysis - as BSOD's occur in the kernel space, and most of the process names are from the user space (a full explanation of this would take a lot longer to type!).
I only use the PROCESS_NAME: line when I see a number of memory dumps (at least 4 or 5) that mention the same process (in this case chrome.exe is named once, YCMMirage.exe is named once, and System is named 3 times).
In those cases I look into what drivers that process could be trying to access - and then concentrate on them.
This does not mean that you should disregard the PROCESS_NAME:, but rather that you should understand that it's not often that it points at the solution.
For example, YCMMirage.exe is a background program that launches the YouCam software.
If the camera is USB, then it's reasonable to check into the USB drivers as you've mentioned
Now, I haven't run the dump file myself - but from looking at the stack text there are 2 significant things:
1) usb80236 (usb80236.sys), nt (ntoskrnl.exe), and hal (hal.dll) are the only drivers listed in the stack. Of them, the most info comes from usb80236 - it is a driver that is related to USB and to networking (FileDescription: Remote NDIS USB Driver)
2) hal (hal.dll) is in the stack. I usually see this when there's a problem between the device and Windows (
Microsoft Windows library files - Wikipedia, the free encyclopedia ). In these cases, I tend to find that compatibility or hardware problems are the most common.
Since Windows drivers are the least likely to be the problem (in a fully updated system), then it's most likely that a 3rd party driver or a hardware problem are causing this. It could be due to compatibility issues, so a look at the driver dates wouid probably help.
I've run the memory dumps - so on with more of my opinion:
The 5 memory dumps that were uploaded are essentially the same as the one that sumitkm posted.
Interestingly, the oldest device driver in the memory dumps is from a Cyberlink program. This tends to support the theory that it's an incompatibility - but it is not proof. The "proof" will be getting a copy of the Cyberlink software that's certified to be Win8 compatible and installing it to see if that stops the BSOD's.
Please note that I haven't seen issues with the 2012 version of AMD Overdrive as I did with the older versions - so this step may e unnecessary:
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from
Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the
DRIVER ONLY:
ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums
If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.
If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
There are a couple of other drivers that date from before the release of Win8 (26 Oct 2012). It would be advisable to check them to ensure that they are compatible with Win8 (if uncertain, just install the one that you're certain is compatible with Win8).
BUT, note that there is a problem device (related to networking) in Device Manager:
WAN Miniport (Network Monitor) #2 ROOT\MS_NDISWANBH\0001 This device is not working properly because Windows cannot load the drivers required for this device.
If Network Monitor is installed, please uninstall it. If not, then please right click on the device and select "Uninstall" - then reboot the computer and check to see if the device shows a problem again..
If this doesn't help stop the BSOD's, please run Driver Verifier according to these instructions:
Driver Verifier Settings
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Mon Mar 24 17:18:37.514 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-24180-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 0:05:58.225[/B]
*** WARNING: Unable to verify timestamp for usb80236.sys
*** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
Probably caused by :[B]usb80236.sys ( usb80236+2dd8 )[/B]
BugCheck [B]133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
Arg3: 0000000000000503, 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_usb80236+2dd8[/B]
BIOS Version F.31
BIOS Release Date 12/04/2013
Manufacturer Hewlett-Packard
Product Name HP Pavilion 15 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 24 17:12:17.254 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-30279-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 0:36:31.955[/B]
*** WARNING: Unable to verify timestamp for usb80236.sys
*** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
Probably caused by :[B]usb80236.sys ( usb80236+2dd5 )[/B]
BugCheck [B]133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
Arg3: 0000000000000503, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR: 0x133
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: [B]0x133_DPC_usb80236+2dd5[/B]
BIOS Version F.31
BIOS Release Date 12/04/2013
Manufacturer Hewlett-Packard
Product Name HP Pavilion 15 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Mar 23 20:41:33.856 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-29764-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 0:04:31.567[/B]
*** WARNING: Unable to verify timestamp for usb80236.sys
*** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
Probably caused by :[B]usb80236.sys ( usb80236+2dd8 )[/B]
BugCheck [B]133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
Arg3: 0000000000000503, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR: 0x133
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: YCMMirage.exe
FAILURE_BUCKET_ID: [B]0x133_DPC_usb80236+2dd8[/B]
BIOS Version F.31
BIOS Release Date 12/04/2013
Manufacturer Hewlett-Packard
Product Name HP Pavilion 15 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Mar 23 20:36:37.040 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-48297-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 0:25:14.739[/B]
*** WARNING: Unable to verify timestamp for usb80236.sys
*** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
Probably caused by :[B]usb80236.sys ( usb80236+2dd2 )[/B]
BugCheck [B]133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
Arg3: 0000000000000503, 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_usb80236+2dd2[/B]
BIOS Version F.31
BIOS Release Date 12/04/2013
Manufacturer Hewlett-Packard
Product Name HP Pavilion 15 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Mar 23 20:06:25.045 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-59670-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 22:05:02.088[/B]
*** WARNING: Unable to verify timestamp for usb80236.sys
*** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
Probably caused by :[B]usb80236.sys ( usb80236+2dd2 )[/B]
BugCheck [B]133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
Arg3: 0000000000000503, 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_usb80236+2dd2[/B]
BIOS Version F.31
BIOS Release Date 12/04/2013
Manufacturer Hewlett-Packard
Product Name HP Pavilion 15 Notebook PC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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]**************************Mon Mar 24 17:18:37.514 2014 (UTC - 4:00)**************************
[COLOR=RED][B]CLVirtualDrive.sys Mon Dec 26 08:26:47 2011 (4EF87617)[/B][/COLOR]
[COLOR=RED][B]AODDriver2.sys Thu Apr 5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
GEARAspiWDM.sys Thu May 3 15:56:17 2012 (4FA2E2E1)
RNDISMP6.SYS Wed Jul 25 22:27:53 2012 (5010AB29)
usbfilter.sys Tue Aug 28 21:27:12 2012 (503D6FF0)
WirelessButtonDriver64.sys Wed Aug 29 23:11:29 2012 (503ED9E1)
RimSerial_AMD64.sys Mon Oct 22 16:51:51 2012 (5085B1E7)
amd_sata.sys Fri Nov 30 04:00:42 2012 (50B875BA)
amd_xata.sys Fri Nov 30 04:00:46 2012 (50B875BE)
Rt630x64.sys Thu Dec 27 19:04:06 2012 (50DCE1F6)
RtsP2Stor.sys Wed Jan 23 03:26:31 2013 (50FF9EB7)
SynTP.sys Tue Feb 5 22:26:11 2013 (5111CD53)
usb80236.sys Mon Feb 11 19:17:50 2013 (51198A2E)
AtihdW86.sys Thu Feb 14 17:11:12 2013 (511D6100)
atikmpag.sys Mon Feb 25 23:28:21 2013 (512C39E5)
atikmdag.sys Mon Feb 25 23:35:39 2013 (512C3B9B)
Accelerometer.sys Tue Feb 26 15:08:10 2013 (512D162A)
hpdskflt.sys Tue Feb 26 15:08:12 2013 (512D162C)
RTKVHD64.sys Thu Mar 7 05:31:01 2013 (51386C65)
rimvndis6_AMD64.sys Wed Mar 20 09:56:02 2013 (5149BFF2)
rtwlane.sys Thu Jul 11 05:03:02 2013 (51DE74C6)
RimUsb_AMD64.sys Mon Nov 25 16:52:56 2013 (5293C6B8)
aswRdr2.sys Tue Mar 18 16:32:20 2014 (5328AD54)
aswKbd.sys Tue Mar 18 16:32:37 2014 (5328AD65)
aswSnx.sys Tue Mar 18 16:32:53 2014 (5328AD75)
aswNdisFlt.sys Tue Mar 18 16:33:50 2014 (5328ADAE)
aswRvrt.sys Tue Mar 18 16:34:02 2014 (5328ADBA)
aswVmm.sys Tue Mar 18 16:34:12 2014 (5328ADC4)
aswMonFlt.sys Tue Mar 18 16:34:52 2014 (5328ADEC)
aswSP.sys Tue Mar 18 16:40:59 2014 (5328AF5B)
aswStm.sys Tue Mar 18 16:41:44 2014 (5328AF88)
[/font]
http://www.carrona.org/drivers/driver.php?id=CLVirtualDrive.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
RNDISMP6.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.
http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
http://www.carrona.org/drivers/driver.php?id=WirelessButtonDriver64.sys
http://www.carrona.org/drivers/driver.php?id=RimSerial_AMD64.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=RtsP2Stor.sys
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
usb80236.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.
http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=Accelerometer.sys
http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
rimvndis6_AMD64.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.
http://www.carrona.org/drivers/driver.php?id=rtwlane.sys
http://www.carrona.org/drivers/driver.php?id=RimUsb_AMD64.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswNdisFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
aswStm.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.