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

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.

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

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.

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

Code:

BugCheck 101, {19, 0, fffff88003342180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Code:

Usual causes:  Device driver, BIOS bug, hardware defect

Code:

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

Code:

2: kd> lmvm k57nd60a
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:        Fri Feb 10 03:53:30 2012 (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

Code:

2: kd> lmvm intelppm
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:        Tue Jul 14 00:19:25 2009 (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

x BlueRobot said:

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

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

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

Code:

0: kd> lmvm VirtuWDDM
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:        Thu Jan 05 16:57:06 2012 (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.

Code:

0: kd> lmvm VirtuWDDM
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:        Thu Jan 05 16:57:06 2012 (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:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

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