locked
Random occurring BSOD due to driver or hardware issues, RRS feed

  • Question

  • Hi

    I have during the last month suffered from random occurring BSODs.They tend to occur when I'm using firefox or playing different Total war games. Further I want to add that I moved my hardware components to a new chassi roughly two months ago.

    I have recently checked if all the power cables were correctly connected and It seems to be the case. Moreover I have updated every driver I could find and ran stress tests on my RAM and my CPU, but no problems were detected. However when I used Memtest86 several errors were detected.

    This link below contains a few minidump files, Bluescreens and the result from Memtest86.

    https://onedrive.live.com/redir?resid=B1EE4F8739E59925!104&authkey=!AOG4gzvH4QebNAU&ithint=file%2crar

    Operating System
        Windows 7 Professional 64-bit SP1
    CPU
        Intel Core i5 3570K @ 3.40GHz
        Ivy Bridge 22nm Technology
    RAM
        8,00GB Dual-Channel DDR3 @ 686MHz (9-9-9-24)
    Motherboard
        ASUSTeK COMPUTER INC. P8H77-V (LGA1155)
    Graphics
        ASUS VN247 (1920x1080@60Hz)
        SyncMaster (1920x1080@60Hz)
        CMC 17" AD (1280x1024@60Hz)
        Intel HD Graphics 4000 (ASUStek Computer Inc)
        1023MB NVIDIA GeForce GTX 560 (ASUStek Computer Inc)
    Storage
        931GB Western Digital WDC WD1001FALS-55J7B0 ATA Device (SATA)
        111GB OCZ-AGILITY3 ATA Device (SSD)
    Optical Drives
        ATAPI iHOS104 ATA Device
    Audio
        NVIDIA High Definition Audio

    Regards
    Johan


    Thursday, October 23, 2014 12:39 PM

Answers

  • Johan

    This was related to memory corruption.  Although verifier was enabled it did not "catch" the mis behaving driver.  Continue to let verifier run and I would also run a system file check.


    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Roger Lu Friday, October 31, 2014 9:38 AM
    Friday, October 24, 2014 2:15 PM

All replies

  • Johan

    These were Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft LtdL I would remove it and use MagicISO in its place.  If you continue to crash I would remove Symantec.

    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\Crash\102114-12948-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0344a000 PsLoadedModuleList = 0xfffff800`0368d890
    Debug session time: Tue Oct 21 14:02:28.910 2014 (UTC - 4:00)
    System Uptime: 0 days 0:00:08.956
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {23e, fffff88001b2c324, fffff980084f8ee0, 0}
    
    *** 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+1324 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffff88001b2c324, The address in the driver's code where the error was detected.
    Arg3: fffff980084f8ee0, IRP address.
    Arg4: 0000000000000000, Status code.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_23e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
    
    FAULTING_IP: 
    dtsoftbus01+1324
    fffff880`01b2c324 4053            push    rbx
    
    FOLLOWUP_IP: 
    dtsoftbus01+1324
    fffff880`01b2c324 4053            push    rbx
    
    IRP_ADDRESS: fffff980084f8ee0
    
    DEVICE_OBJECT: fffffa8008f5e7f0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8000394c4ec to fffff800034bfbc0
    
    STACK_TEXT:  
    fffff880`033ed778 fffff800`0394c4ec : 00000000`000000c9 00000000`0000023e fffff880`01b2c324 fffff980`084f8ee0 : nt!KeBugCheckEx
    fffff880`033ed780 fffff800`0395658a : fffff800`0394ab00 fffff880`01b2c324 fffff980`084f8ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`033ed7c0 fffff800`0395745e : 00000000`0000023e 00000000`00000000 fffff980`084f8ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`033ed810 fffff800`0396282f : fffffa80`09033540 fffffa80`08f775d0 fffffa80`08f77688 fffff880`01b30228 : nt!VfErrorReport6+0x6e
    fffff880`033ed8e0 fffff800`03962c73 : fffffa80`08f775d0 00000000`00000002 fffffa80`08f5e7f0 fffff880`01b2c3f4 : nt!IovpCallDriver2+0x13f
    fffff880`033ed940 fffff800`03968d3e : fffff980`084f8ee0 fffff980`084f8ee0 00000000`00000002 fffffa80`08f5e7f0 : nt!VfAfterCallDriver+0x353
    fffff880`033ed990 fffff880`00e2f617 : fffff880`00ebed20 fffff880`033eda60 00000000`00000025 fffffa80`08f775d0 : nt!IovCallDriver+0x57e
    fffff880`033ed9f0 fffff880`00e2fec5 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09031da0 : Wdf01000!FxIoTarget::SubmitSync+0x24b
    fffff880`033edaa0 fffff880`01b8de95 : fffffa80`00000020 fffffa80`09031da0 fffffa80`09097df0 fffffa80`09033600 : Wdf01000!imp_WdfRequestSend+0x2d1
    fffff880`033edb30 fffff880`01b8e2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`033edcf0 : cdrom!DeviceSendRequestSynchronously+0xc9
    fffff880`033edb90 fffff880`01b8cf04 : 0000057f`f6f84fd8 fffff880`033edcf0 fffffa80`09133700 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
    fffff880`033edcc0 fffff880`01b8b825 : fffffa80`00000002 fffffa80`0907b2d0 fffff880`01b833b8 0000057f`f6f84fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
    fffff880`033edd90 fffff880`00e5d4a8 : 00000000`00000000 00000000`00000010 00000000`0000000c fffff880`00ebf0c0 : cdrom!DeviceEvtSelfManagedIoInit+0x105
    fffff880`033eddd0 fffff880`00e49926 : fffffa80`0913b140 00000000`0000000c fffff880`00ebf0c0 00000000`00000002 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
    fffff880`033ede00 fffff880`00e51463 : 00000000`00000000 00000000`00000000 fffff880`033edfa0 fffff880`00ebf0c0 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
    fffff880`033ede70 fffff880`00e3f0f8 : 00000000`00000312 fffff880`033edfa0 00000000`ffff7fff fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
    fffff880`033edea0 fffff880`00e3eda6 : fffff880`00ebee80 fffffa80`0907ec98 fffffa80`0907eae0 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
    fffff880`033ee000 fffff880`00e3f627 : 00000000`00000000 fffff880`033ee0e0 fffffa80`0907ec80 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`033ee070 fffff880`00e571be : 00000000`00000000 00000000`00000501 00000000`00000501 fffff800`039541de : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
    fffff880`033ee110 fffff880`00e415d5 : 00000000`00000501 fffff880`033ee1b0 00000000`00000500 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
    fffff880`033ee140 fffff880`00e3b853 : fffffa80`0907ed48 fffffa80`0907ed50 fffffa80`0907eae0 fffffa80`0907ed48 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c9
    fffff880`033ee1e0 fffff880`00e3fa01 : 00000000`00000000 fffff880`033ee2c0 fffffa80`0907ed38 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3df
    fffff880`033ee250 fffff880`00e51d59 : 00000000`00000000 fffffa80`0907e8d0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
    fffff880`033ee2f0 fffff880`00e50df5 : 00000000`00000101 00000000`00000108 00000000`00000108 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
    fffff880`033ee330 fffff880`00e50ac6 : 00000000`00000002 fffffa80`0907ec08 fffffa80`0907eae0 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
    fffff880`033ee3d0 fffff880`00e50879 : 00000000`00000000 fffff880`033ee4b0 fffffa80`0907ebf0 fffffa80`0907eae0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`033ee440 fffff880`00e51b66 : 00000000`00000000 fffffa80`0907eae0 fffffa80`09044bc0 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
    fffff880`033ee4e0 fffff880`00e2b5d7 : fffffa80`08269710 fffff880`033ee560 00000000`00000000 fffffa80`09050788 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
    fffff880`033ee510 fffff880`00e2a79a : fffff980`0fdf4e50 00000000`00000051 fffff980`0fdf4e50 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
    fffff880`033ee570 fffff880`00e2a866 : fffff980`0fdf4e50 00000000`00000002 fffffa80`0907e8d0 fffffa80`0907e8d0 : Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`033ee5b0 fffff800`03968d26 : fffff980`0fdf4e50 00000000`00000002 fffffa80`0907e8d0 fffffa80`0907e8d0 : Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`033ee5f0 fffff800`0387c18e : fffff980`0fdf4e50 fffffa80`0904be00 fffffa80`0907e8d0 fffffa80`08371910 : nt!IovCallDriver+0x566
    fffff880`033ee650 fffff800`035b67ad : fffffa80`08f5e7f0 fffffa80`0904be00 fffff800`035bfed0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`033ee690 fffff800`0388b506 : fffff800`036c3b60 fffffa80`08f826a0 fffffa80`0904be00 fffffa80`08f82848 : nt!PnpStartDevice+0x11d
    fffff880`033ee750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PnpStartDeviceNode+0x156
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  dtsoftbus01+1324
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dtsoftbus01
    
    IMAGE_NAME:  dtsoftbus01.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f10358a
    
    FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
    
    BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xc9_23e_vrf_dtsoftbus01+1324
    
    FAILURE_ID_HASH:  {a4b0905c-b00f-9d8a-8c18-eafbbc358648}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Yolanda Zhu Friday, October 24, 2014 3:01 AM
    Thursday, October 23, 2014 1:19 PM
  • Hi
    I removed the drivers and the programs you thought were behind the crash, but the problem still persist. I checked my most recent miniddump file and it indicatated that ntoskrnl.exe was the cause. If I understand this correctly this file is a part of the operatingsystem thus cant be removed. What should i do?

    https://onedrive.live.com/redir?resid=B1EE4F8739E59925%21105

    Regards
    Johan

    Friday, October 24, 2014 1:55 PM
  • Johan

    This was related to memory corruption.  Although verifier was enabled it did not "catch" the mis behaving driver.  Continue to let verifier run and I would also run a system file check.


    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Roger Lu Friday, October 31, 2014 9:38 AM
    Friday, October 24, 2014 2:15 PM