BSOD couple times a month, usually (but not always) 0x0000101, 0000019

[arbeleg]

Hi, and thanks in advance for helping a first-time poster,

I have a Win7 x64 system that BSOD's on me a couple of times a month. I tried to live with it for awhile, figuring a driver update somewhere along the way might sort it out, but it's been going on for months and months. No apparent pattern that I've noticed. It doesn't seem to happen when the system is stressed, sometimes it's completely idle. Temperatures are not a problem (CPU temps usually 38-40 C, MB temps a few degrees below that), and I am not overclocking.

Most often the crash code indicates a CLOCK WATCHDOG TIMEOUT, although I have also seen DRIVER_VERIFIER_IOMANAGER_VIOLATION, NTFS_FILE_SYSTEM, and DRIVER_PORTION_MUST_BE_NONPAGED occasionally. Based on some googling, I've tried bumping up the voltage a few notches (one notch at a time, trying higher level next time the problem occurs), but that hasn't helped much (if at all). I've updated all device drivers that I'm aware of to the latest revisions, and flashed BIOS to revision 2.20A, run chkdsk /f at boot time and SFC /scannow.

System is a custom built Core i7-2600k on a ASRock Z68 Extreme4, 16 GB RAM, Plextor 256GB SSD and 2 TB WD hard drive, using integrated graphics to drive dual monitors.

I've attached SF diagnostics. Any help, guidance and/or suggestions would be appreciated.

Thanks,
Arbeleg

 

[koolkat77]

Latest dumps (of May) indicate the 101 error code. We have a guide on how to troubleshoot, suggest you go through it: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Security App

[FONT="Lucida Console"]aswRvrt.sys                 Thu May  2 05:22:25 2013 (5181A3B1)
aswFsBlk.SYS                Thu May  2 05:22:39 2013 (5181A3BF)
aswMonFlt.sys               Thu May  2 05:22:46 2013 (5181A3C6)
aswTdi.SYS                  Thu May  2 05:22:55 2013 (5181A3CF)
aswrdr2.sys                 Thu May  2 05:23:03 2013 (5181A3D7)
aswSP.SYS                   Thu May  2 05:23:52 2013 (5181A408)
aswSnx.SYS                  Thu May  2 05:23:56 2013 (5181A40C)
aswVmm.sys                  Thu May  2 20:52:28 2013 (51827DAC)[/FONT]

Crashes indicate Avast! being a possible cause. Remove Avast! for the time being and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free - Make a full scan with both separately.

   Information

DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

Follow this:

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.

Daemon Tools/Alcohol %

dtsoftbus01.sys Fri Jan 13 19:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys

sptd.sys Sun Aug 19 03:05:38 2012 (503003A2)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
http://www.carrona.org/drivers/driver.php?id=sptd.sys

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

teamviewervpn.sys Thu Dec 13 15:22:09 2007 (4760F9C1)
TeamViewerVPN Network Adapter
http://www.carrona.org/drivers/driver.php?id=teamviewervpn.sys

dsNcAdpt.sys Tue Mar 31 08:33:33 2009 (49D180FD)
Network Connect VPN software by Juniper Networks
http://www.carrona.org/drivers/driver.php?id=dsNcAdpt.sys

LGPBTDD.sys Thu Jul 2 00:47:52 2009 (4A4BAF58)
Logitech GamePanel Software
http://www.carrona.org/drivers/driver.php?id=LGPBTDD.sys

AsrAppCharger.sys Fri Jun 11 12:37:12 2010 (4C11D998)
ASRock App Charger Likely BSOD cause - haven't seen recently (15Jan2013)
http://www.carrona.org/drivers/driver.php?id=AsrAppCharger.sys

The below is for information purposes only. Contains relevant information from the blue screen analysis:

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

BSOD BUGCHECK SUMMARY

[FONT="Lucida Console"]Debug session time: Fri May 10 23:17:28.935 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\051013-148356-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 2 days 3:07:48.825
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {19, 0, fffff880035e6180, 4}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000101]CLOCK_WATCHDOG_TIMEOUT (101)[/url]
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880035e6180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  winvnc.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue May  7 22:56:51.558 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050713-143708-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 19:02:07.448
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {19, 0, fffff88003542180, 2}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000101]CLOCK_WATCHDOG_TIMEOUT (101)[/url]
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003542180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu May  2 00:17:29.801 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\050113-165860-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 1 days 4:00:26.691
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {19, 0, fffff880035e6180, 4}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000101]CLOCK_WATCHDOG_TIMEOUT (101)[/url]
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880035e6180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  TeamViewer_Des
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[arbeleg]

Thanks, I have now replaced Avast with MSE, and uninstalled Daemon Tools and ASRock App Charger. MSE and MalwareBytes scans came back clean. We'll see if this resolves the problem. Thanks for your help!

 

[koolkat77]

You're welcome.
Keep us posted, good luck!

 

[koolkat77]

Have the BSOD's occured?

 

[arbeleg]

Unfortunately, yes. It ran OK for a few days, but then I had another BSOD on May 22. Same CLOCK_WATCHDOG_TIMEOUT with Arg1=19 as has happened before. Should I reupload crash info? Any other suggestion? I forgot to mention in my previous response that I had also run a boot-time ChkDsk and that SFC/scannow came back clean. I do see now that I missed the removal utility for SPTD.sys after the uninstall of Daemon Tools. Will try that and see if it helps.

 

[koolkat77]

Yes please upload new reports.

 

[x BlueRobot]

You will need to configure a Kernel Memory dump to be created upon BSOD, and then upload the file to a free cloud-based file sharing site such as SkyDrive or Dropbox, then post the link to the file in your next post.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[arbeleg]

Sorry for the long delay in following up on this -- travel and other unrelated issues made it hard for me to get back to this for awhile. In any event, I had another crash today, and have uploaded new diagnostics to https://www.dropbox.com/s/226fo19kkwb7zde/SF_02-08-2013.zip

 

[x BlueRobot]

You uploaded a Minidump, not a Kernel Memory dump, sorry I should have specified where to find it in my previous instructions

C:\Windows\MEMORY.DMP or %systemroot%\MEMORY.DMP

 

[arbeleg]

Whoops! My apologies. I guess I didn't read closely enough. I don't have a MEMORY.DMP file from the latest crash, although there is a huge (7 GB) file from a crash on 6/28. However, even compressed it was too large to upload to Dropbox or SkyDrive, so I'm guessing it isn't the right kind of dump anyways. I've reconfigured per the instructions to save a Kernel Memory dump next time it BSOD's, and will update further next time it happens.

 

[x BlueRobot]

Okay thanks, and that really big file will be a Full Memory Dump.

 

[arbeleg]

Well, I didn't have to wait long for another BSOD. Oddly, the MEMORY.DMP file is still huge (> 6 GB), even though I verified that "write debugging information" is set to "kernel memory dump". The timestamp on the file has changed to the time of the BSOD, so it appears to have been overwritten.

Due to the size, I couldn't post it directly on SkyDrive, so I used 7-Zip to compress it and upload it.

http://sdrv.ms/18Yss9d

I've renamed the dump file on my system so that the next BSOD won't have an existing (huge) MEMORY.DMP file to overwrite, in case that was the reason the file size was so large. If it does produce a smaller file, I'll upload that and reply here.

 

[x BlueRobot]

Downloading the file now, and the file is big, because it's the entire Kernel address space at the time of the crash.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 101[/COLOR], {19, 0, [COLOR="SeaGreen"]fffff88003342180[/COLOR], 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Usual causes:  Device driver, BIOS bug, hardware defect

2: kd> [COLOR="SeaGreen"]!prcb[/COLOR]
PRCB for Processor 2 at fffff88003342180:
Current IRQL -- [COLOR="Red"]0[/COLOR]
Threads--  Current [COLOR="Red"]fffff8800334d0c0[/COLOR] Next 0000000000000000 Idle fffff8800334d0c0
Processor Index 2 Number (0, 2) GroupSetMember 4
Interrupt Count -- 0a5595db
Times -- Dpc    000000b0 Interrupt 00000bdd 
         Kernel 0054fe74 User      000a6eb0

2: kd>[COLOR="SeaGreen"] lmvm k57nd60a[/COLOR]
start             end                 module name
fffff880`0658f000 fffff880`065fc000   k57nd60a   (no symbols)           
    Loaded symbol image file: k57nd60a.sys
    Image path: \SystemRoot\system32\DRIVERS\k57nd60a.sys
    Image name: k57nd60a.sys
    Timestamp:        [COLOR="Red"]Fri Feb 10 03:53:30 2012[/COLOR] (4F3494BA)
    CheckSum:         00072352
    ImageSize:        0006D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver, seems to be causing problems, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom

2: kd> [COLOR="SeaGreen"]lmvm intelppm[/COLOR]
start             end                 module name
fffff880`06999000 fffff880`069af000   intelppm   (no symbols)           
    Loaded symbol image file: intelppm.sys
    Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: intelppm.sys
    Timestamp:        [COLOR="Red"]Tue Jul 14 00:19:25 2009[/COLOR] (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would also check for any chipset updates from here - https://downloadcenter.intel.com/default.aspx

 

[arbeleg]

Your Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver, seems to be causing problems, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom
[...]
I would also check for any chipset updates from here - https://downloadcenter.intel.com/default.aspx

Thank you for your help. I've now updated the Broadcom drivers. I had previously tried checking with Intel Download Center's utility, and it didn't report any drivers needing updating, but I just now also ran the Intel Chipset Device Software (INF Update Utility) separately, and it may have updated a few files.

We'll see if things improve -- my fingers are crossed!

Thanks so much for the help.

Arbeleg

 

[x BlueRobot]

Welcome, glad to be able to help, let's hope it solves everything

 

[arbeleg]

Unfortunately, updating the drivers doesn't seem to have fixed the problem. I've had 3 crashes in the past couple of weeks. I've uploaded a new memory dump to http://sdrv.ms/1dfAA9E in case anyone can take another look.

All the help has been (and continues to be) appreciated,
Arbeleg

 

[x BlueRobot]

0: kd> [COLOR="SeaGreen"]lmvm VirtuWDDM[/COLOR]
start             end                 module name
fffff880`064e8000 fffff880`064fd000   VirtuWDDM   (no symbols)           
    Loaded symbol image file: VirtuWDDM.sys
    Image path: \SystemRoot\system32\DRIVERS\VirtuWDDM.sys
    Image name: VirtuWDDM.sys
    Timestamp:        [COLOR="Red"]Thu Jan 05 16:57:06 2012[/COLOR] (4F05D662)
    CheckSum:         00013A17
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your VIRTU LucidInterop WDDM Driver by LucidLogix seems to be a possible cause, please update the driver or remove the driver/program completely.

 

[x BlueRobot]

0: kd> [COLOR=SeaGreen]lmvm VirtuWDDM[/COLOR]
start             end                 module name
fffff880`064e8000 fffff880`064fd000   VirtuWDDM   (no symbols)           
    Loaded symbol image file: VirtuWDDM.sys
    Image path: \SystemRoot\system32\DRIVERS\VirtuWDDM.sys
    Image name: VirtuWDDM.sys
    Timestamp:        [COLOR=Red]Thu Jan 05 16:57:06 2012[/COLOR] (4F05D662)
    CheckSum:         00013A17
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your VIRTU LucidInterop WDDM Driver by LucidLogix driver seems to be a possible cause, please update the driver completely, or remove the program/driver completely.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Any Stop 0x101's with Driver Verifier running will indicate a hardware issue.