Random BSOD

I get a random blue screen of death and i cant figure out whats causing them. Dumps included if someone could help it would be great.

hdfsi said:

I get a random blue screen of death and i cant figure out whats causing them. Dumps included if someone could help it would be great.

Memory corruption caused by an unkown driver (team viewer_des?). Please run memtest and driver verifier to determine if it is the memory or a driver


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\060311-28218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c68000 PsLoadedModuleList = 0xfffff800`02ea5e50
Debug session time: Sat Jun  4 02:56:02.321 2011 (GMT-4)
System Uptime: 0 days 4:45:24.430
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 39d30, 2, 39d2a}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000039d30, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000039d2a, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TeamViewer_Des

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d6833c to fffff80002cd8700

STACK_TEXT:  
fffff880`0e781da8 fffff800`02d6833c : 00000000`0000004e 00000000`00000099 00000000`00039d30 00000000`00000002 : nt!KeBugCheckEx
fffff880`0e781db0 fffff800`02d4a7b9 : 9ca00000`39d30867 00000000`00000000 00000000`63416d4d fffff680`00023218 : nt!MiBadShareCount+0x4c
fffff880`0e781df0 fffff800`02d09401 : 00000000`00000000 fffff680`00023ff8 fffffa80`03ca75a0 9a400000`5d32c867 : nt! ?? ::FNODOBFM::`string'+0x31e93
fffff880`0e781fa0 fffff800`02d0be79 : fffff880`00000000 00000000`051f1fff fffff900`00000000 00000000`00000068 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0e782160 fffff800`02feff20 : fffffa80`03dc9dd0 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0e782280 fffff960`000b3ee5 : 00000000`00000001 fffffa80`056b87b0 00000000`00000001 0000083c`00000000 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0e782340 fffff960`001e598a : 00000000`00000000 fffff880`0e782460 fffff880`0e782450 00000000`00000001 : win32k!SURFACE::Map+0x175
fffff880`0e782390 fffff960`000c4ae8 : fffff900`c010a010 fffff880`0e782450 00000000`00000001 00000438`00001680 : win32k!DEVLOCKOBJ::bMapTrgSurfaceView+0x3e
fffff880`0e7823c0 fffff960`00086a33 : fffff900`c2663250 fffff880`0e782450 00000000`00000001 fffff880`0e782460 : win32k!DEVLOCKOBJ::bPrepareTrgDco+0x98
fffff880`0e7823f0 fffff960`0020bd1a : fffff900`c010a010 00000000`00000001 fffff880`0e782520 00000000`00000003 : win32k!DEVLOCKOBJ::bLock+0x423
fffff880`0e782430 fffff800`02cd7953 : fffffa80`05ff6950 fffff880`0e782520 00000000`02ec0820 fffff900`c060af00 : win32k!GreSetICMMode+0x86
fffff880`0e7824a0 00000000`73492dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009ce08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73492dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d6833c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

I have run the memtest 4 diff times for like 8 passes and i didnt get any errors. I enabled the driver verifier ill post the bsod when it happens.

When i enabled the driver verifier i get a BSOD at start up just passed the windows logo. Any other ideas?

hdfsi said:

When i enabled the driver verifier i get a BSOD at start up just passed the windows logo. Any other ideas?

Boot into safe mode turn off verifier and upload the verified DMP file

Ok i just got the dump and uploaded it.

hdfsi said:

Ok i just got the dump and uploaded it.

Easy Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. remove it and dont use it or failing that update to the newest version

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\060411-28562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e87e50
Debug session time: Sat Jun  4 19:49:23.234 2011 (GMT-4)
System Uptime: 0 days 0:00:14.421
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88003f2c308, fffff98005c38ee0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88003f2c308, The address in the driver's code where the error was detected.
Arg3: fffff98005c38ee0, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`03f2c308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`03f2c308 4053            push    rbx

IRP_ADDRESS:  fffff98005c38ee0

DEVICE_OBJECT: fffffa80062edd50

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80002ebe400 -- (!locks fffff80002ebe400)

Resource @ nt!PiEngineLock (0xfffff80002ebe400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002ebe400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800031443dc to fffff80002cba700

STACK_TEXT:  
fffff880`031c39a8 fffff800`031443dc : 00000000`000000c9 00000000`0000023e fffff880`03f2c308 fffff980`05c38ee0 : nt!KeBugCheckEx
fffff880`031c39b0 fffff800`0314e47a : fffff800`031429f0 fffff880`03f2c308 fffff980`05c38ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031c39f0 fffff800`0314f34e : 00000000`0000023e 00000000`00000000 fffff980`05c38ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031c3a40 fffff800`0315a71f : fffffa80`063025d0 fffffa80`062fe850 fffffa80`062fe908 fffff880`03f2fdbc : nt!VfErrorReport6+0x6e
fffff880`031c3b10 fffff800`0315ab63 : fffffa80`062fe850 00000000`00000002 fffffa80`062edd50 fffff880`03f2c3d8 : nt!IovpCallDriver2+0x13f
fffff880`031c3b70 fffff800`03160c2e : fffff980`05c38ee0 fffff980`05c38ee0 00000000`00000002 fffffa80`062edd50 : nt!VfAfterCallDriver+0x353
fffff880`031c3bc0 fffff880`00ea40c2 : fffff880`00f1d7c0 fffffa80`0678bd10 00000000`00000025 fffffa80`062fe850 : nt!IovCallDriver+0x57e
fffff880`031c3c20 fffff880`00eb959f : fffffa80`067d7a40 00000000`00000000 fffff880`00000000 fffff880`0196a5d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`031c3cd0 fffff880`0197ee95 : fffffa80`00000020 fffffa80`067d7a40 fffffa80`0678bd10 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`031c3d20 fffff880`0197f2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`031c3ee0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`031c3d80 fffff880`0197df04 : 0000057f`f9a84fd8 fffff880`031c3ee0 fffffa80`059c3a10 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`031c3eb0 fffff880`0197c825 : fffffa80`00000002 fffffa80`0657b390 fffff880`019743b8 0000057f`f9a84fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`031c3f80 fffff880`00f0e9d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00f17620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`031c3fc0 fffff880`00f0e94e : fffffa80`06789860 00000000`0000000c fffff880`00f17620 fffff880`00f17600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`031c3ff0 fffff880`00f02b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f17620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`031c4060 fffff880`00f026eb : 00000000`00000312 00000000`00000000 fffff880`00f17600 fffff800`02e71a40 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`031c4090 fffff880`00f0238e : fffffa80`067899d0 00000000`00000040 fffff880`00f173e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`031c41c0 fffff880`00f0206c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`067899d0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`031c4230 fffff880`00f0fb5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`031c42c0 fffff880`00f0fabb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`0315f5ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`031c42f0 fffff880`00f0b950 : fffffa80`067899d0 00000000`00000001 00000000`00000000 fffff880`00f13ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`031c4370 fffff880`00f0b372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`0678abd0 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`031c43e0 fffff880`00f07a45 : 00000000`00000000 fffffa80`0678abd0 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`031c4470 fffff880`00f07841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`02dee6eb : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`031c44b0 fffff880`00f074fe : fffffa80`067899d0 fffff880`031c45e0 00000000`00000004 fffff880`00f16390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`031c4520 fffff880`00f07201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`067899d0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`031c4590 fffff880`00efed9c : 00000000`00000000 fffffa80`067899d0 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`031c4620 fffff880`00efddd6 : fffffa80`05c13e70 00000000`00000002 00000000`00000000 fffffa80`067899d0 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`031c4650 fffff880`00ecd245 : fffff980`05c18e50 fffff980`05c18e50 fffffa80`0678abd0 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`031c46c0 fffff880`00ecd14b : fffff880`031c47a8 fffff980`05c18e50 00000000`00000002 fffffa80`0678abd0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`031c46f0 fffff800`03160c16 : fffff980`05c18e50 00000000`00000002 fffffa80`0678abd0 fffffa80`0678abd0 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`031c4730 fffff800`030795ee : fffff980`05c18e50 fffffa80`067d6890 fffffa80`0678abd0 fffffa80`063de180 : nt!IovCallDriver+0x566
fffff880`031c4790 fffff800`02db3fdd : fffffa80`062edd50 fffffa80`067d6890 fffff800`02db9c40 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031c47d0 fffff800`030843d6 : fffff800`02ebe1c0 fffffa80`062d2010 fffffa80`067d6890 fffffa80`062d21b8 : nt!PnpStartDevice+0x11d
fffff880`031c4890 fffff800`03084674 : fffffa80`062d2010 fffffa80`0489002a fffffa80`0489f5e0 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`031c4920 fffff800`030a7966 : fffffa80`062d2010 fffffa80`0489f5e0 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`031c4950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2eb75c

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

Followup: MachineOwner
---------

Is that the only thing that is causing the problem? or is it another driver?

hdfsi said:

Is that the only thing that is causing the problem? or is it another driver?

*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )