BSOD on start up. Attached minidumps.


  1. Posts : 6
    WINDOWS 7 ULTIMATE x64
       #1

    BSOD on start up. Attached minidumps.


    I have a hp dv6 laptop with windows 7 ultimate x64. I am facing severe BSOD problems. I know its not a hardware problem as I have done memtest. Also, my SFC/scannow says that there are corrupt files that it cannot repair. SO I'm pretty sure its a software problem. Please help me out. I have attached the minidump files as required by you. Please help me.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hello aalekh1508.

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
    5. Apply > OK
    6. Accept then restart.

    Now restart the computer a few times. Does the BSODs continue? If so, test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.


    If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip




    Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
    ___________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41287, 0, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
        Parameter 2 contains the referenced virtual address.
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41287
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800d17d700 -- (.trap 0xfffff8800d17d700)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000fffffffff rbx=0000000000000000 rcx=0000000000002b26
    rdx=0000000000930975 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000341e93d rsp=fffff8800d17d890 rbp=fffff8800d17db60
     r8=fb00000930975847  r9=84000000000003e0 r10=fffff68000015930
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiGetWorkingSetInfoList+0x589:
    fffff800`0341e93d 458b0424        mov     r8d,dword ptr [r12] ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003416d32 to fffff8000347dc00
    
    STACK_TEXT:  
    fffff880`0d17d598 fffff800`03416d32 : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0d17d5a0 fffff800`0347bd2e : 00000000`00000000 00000000`00000000 fffffa80`01871e00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x454f5
    fffff880`0d17d700 fffff800`0341e93d : 00000000`05008001 00000000`00000000 fffffa80`000000a0 fffff880`00000000 : nt!KiPageFault+0x16e
    fffff880`0d17d890 fffff800`03758be8 : 00000000`00000000 00000000`00000001 fffffa80`0e614060 00020bea`00020410 : nt!MiGetWorkingSetInfoList+0x589
    fffff880`0d17d980 fffff800`0347ce93 : 00000000`0000019c fffffa80`0f17c640 00000000`00000000 00000000`0118e508 : nt!NtQueryVirtualMemory+0x696
    fffff880`0d17da70 00000000`7731154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0118e4e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7731154a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+454f5
    fffff800`03416d32 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+454f5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+454f5
    
    BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+454f5
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 6
    WINDOWS 7 ULTIMATE x64
    Thread Starter
       #3

    HEY,
    Sorry for the late reply. It's been so crazy with all the work. Anyways , i'll get to the point. Memtest showed no negative results. But when i run the driver verfier, my laptop crashed on starting. It happened everytime i started my laptop. So i think there is a problem in a start up driver. Here are the minidumps, Please help!!
      My Computer


  4. Posts : 6
    WINDOWS 7 ULTIMATE x64
    Thread Starter
       #4

    Hey,
    Sorry for the late reply. I have been very very busy. I am really sorry. But i'll get to the point now. Memtest showed no negative results so I know its a software problem. The driver verifier resulted in multiple crashes. My laptop crashed everytime it started. I am attaching the minidumps. Hope that helps.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Code:
    fff880`03bc48f8  fffff880`020f5228Unable 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
     dtsoftbus01+0x5228
    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

    Let us know the results.
      My Computer


  6. Posts : 6
    WINDOWS 7 ULTIMATE x64
    Thread Starter
       #6

    It still is crashing. I am attaching the latest dump files. The last one is at 7/9. Please do check it.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    Your crash dumps are not showing any finite probable cause.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  8. Posts : 6
    WINDOWS 7 ULTIMATE x64
    Thread Starter
       #8

    I think that my synaptics pointer driver is causing the crashes. If that is the case, How do i solve it?
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    Synaptec drivers usually does not cause BSODs. If it is really the case as you think, update it from Drivers | Synaptics.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:29.
Find Us