BSOD "Custom Error"

Have you tried booting your computer in selective star up? Go into MSCONFIG and under Startup choose selective startup and uncheck Load Startup Items and then save and reboot and see if the problem continues. If the computer crashes again upload a new report not just the minidump files.

https://www.sevenforums.com/crashes-d...tructions.html

Well, we got lucky - one of the three dumps had an exception record that contained something useful:

Code:

3: kd> !thread
GetPointerFromAddress: unable to read from fffff80003510000
THREAD fffffa800c323b60  Cid 0890.0dec  Teb: 000000007efa7000 Win32Thread: fffff900c45408c0 RUNNING on processor 3
IRP List:
    Unable to read nt!_IRP @ fffffa800c124e10
Not impersonating
GetUlongFromAddress: unable to read from fffff8000344dba4
Owning Process            fffffa800c11b920       Image:         DTLite.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      1186071      
Context Switch Count      854                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x0000000072c6c724
Stack Init fffff8800a99cdb0 Current fffff8800a99bdf0
Base fffff8800a99d000 Limit fffff8800a997000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a999ea8 fffff880`0ad82d82 : 00000000`00000023 00000000`000e0107 fffff880`0a99ae88 fffff880`0a99a6e0 : nt!KeBugCheckEx
fffff880`0a999eb0 fffff880`0ad84c44 : fffff880`0ad872d0 fffff880`0a99bc40 00000000`00000000 fffff8a0`03d93001 : fastfat!FatExceptionFilter+0xaa
fffff880`0a999ef0 fffff800`0330b4ec : 00000000`00000000 fffff8a0`0c91b001 00000000`00000000 fffff8a0`03d83001 : fastfat!_GSHandlerCheck_SEH+0x134
fffff880`0a999f30 fffff800`0330af6d : fffff880`0ad872c4 fffff880`0a99bc40 00000000`00000000 fffff880`0ad81000 : nt!_C_specific_handler+0x8c
fffff880`0a999fa0 fffff800`03309d45 : fffff880`0ad872c4 fffff880`0a99a018 fffff880`0a99ae88 fffff880`0ad81000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a999fd0 fffff800`0331adc1 : fffff880`0a99ae88 fffff880`0a99a6e0 fffff880`00000000 fffffa80`075af5b0 : nt!RtlDispatchException+0x415
fffff880`0a99a6b0 fffff800`032decc2 : fffff880`0a99ae88 fffffa80`0c695000 fffff880`0a99af30 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0a99ad50 fffff800`032dd83a : 00000000`00000000 00000000`00000040 00000000`00730000 fffffa80`0c695000 : nt!KiExceptionDispatch+0xc2
fffff880`0a99af30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
 
3: kd> .exr 0xfffff8800a99ae88
ExceptionAddress: fffff880015ab0b0 (dtsoftbus01+0x00000000000050b0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000040
Attempt to read from address 0000000000000040
 
3: kd> kb
  *** Stack trace for last set context - .thread/.cxr resets it
RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dtsoftbus01+0x50b0
 
3: kd> lmvm dtsoftbus01
start             end                 module name
fffff880`015a6000 fffff880`015e9000   dtsoftbus01 T (no symbols)           
    Loaded symbol image file: dtsoftbus01.sys
    Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
    Image name: dtsoftbus01.sys
    Timestamp:        Thu Jan 13 03:27:08 2011 (4D2EB75C)
    CheckSum:         00045141
    ImageSize:        00043000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This appears to be the Daemon Tools Virtual Bus driver, which is causing the exception to disk, which is causing the bugcheck. If you uninstall Daemon Tools (and make sure this driver is gone after the reboot), I'm suspecting the problem will go away.

jakeythesnake said:

Marvellous, thank you. I shall report back if it reoccurs, but +rep!

That should have been caught from the beginning but at the time I wasn't aware of the dtsoftbus driver and overlooked it. Glad everythings working out for you.