Regular BSOD seemingly while idling

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    Windows 7 ultimate x64
       #1

    Regular BSOD seemingly while idling


    Hey guys

    Getting a BSOD error that happens on a regular occasion. Has happened nearly everyday this month and isn't uncommon for it to BSOD just after the first one. Seems to be the same driver that is causing the issue and I don't know where to start. Attached are my minidumps
      My Computer


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

    Hello Kable72.

    Install Service pack 1.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack Center - Microsoft Windows

    Enable Driver Verifier.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {20, fffff8800c701c40, fffff8800c702bc0, 5f88361}
    
    GetPointerFromAddress: unable to read from fffff8000330c0e0
    GetUlongFromAddress: unable to read from fffff8000330c198
    GetUlongFromAddress: unable to read from fffff8000327a1b0
    Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+1a64 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000020, a pool block header size is corrupt.
    Arg2: fffff8800c701c40, The pool entry we were looking for within the page.
    Arg3: fffff8800c702bc0, The next pool entry.
    Arg4: 0000000005f88361, (reserved)
    
    Debugging Details:
    ------------------
    
    GetUlongFromAddress: unable to read from fffff8000327a1b0
    
    BUGCHECK_STR:  0x19_20
    
    POOL_ADDRESS:  fffff8800c701c40 Nonpaged pool
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  sidebar.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800032076d3 to fffff800030d55c0
    
    STACK_TEXT:  
    fffff880`063ad8c8 fffff800`032076d3 : 00000000`00000019 00000000`00000020 fffff880`0c701c40 fffff880`0c702bc0 : nt!KeBugCheckEx
    fffff880`063ad8d0 fffff800`03486536 : fffff8a0`00b545f0 fffff880`063adca0 fffff880`69634d43 00000000`000004ef : nt!ExAllocatePoolWithTag+0x1a64
    fffff880`063ad980 fffff800`033adf4e : 00000000`00000016 fffff880`063adb48 fffffa80`09d32300 fffff800`00000016 : nt!CmpCallCallBacks+0x4f6
    fffff880`063ada50 fffff800`030d4813 : fffffa80`0b603060 fffff800`00000007 00000000`028466d8 00000000`02e554f0 : nt!NtQueryKey+0x44c
    fffff880`063adbb0 00000000`772cf81a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`028466b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772cf81a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExAllocatePoolWithTag+1a64
    fffff800`032076d3 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ExAllocatePoolWithTag+1a64
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f857d
    
    FAILURE_BUCKET_ID:  X64_0x19_20_nt!ExAllocatePoolWithTag+1a64
    
    BUCKET_ID:  X64_0x19_20_nt!ExAllocatePoolWithTag+1a64
    
    Followup: MachineOwner
    ---------
    In such a situation, it is better to 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.

    ► upload your MSINFO32.nfo file.

    1. Click on the start button
    2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
    3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
    4. Give the time for processing, it will save a .nfo file on your desktop.
    5. Zip it, and upload it following the instruction.

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


  3. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #3

    Hey sorry been REALLY busy with work recently. Attached is the .nfo and driver verifier has been activated.
      My Computer


  4. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #4

    okay when I activated Driver Verifier, it had crashed twice before windows had successfully loaded. I assume 2 dump files will be sufficient?
      My Computer


  5. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #5

    2 BSOD since this morning.
      My Computer


  6. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #6

    bump
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {23e, fffff880015b6324, fffff980085c8ee0, 0}
    
    Unable to load image 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+1324 )
    
    Followup: MachineOwner
    ---------
    Uninstall Daemon tools.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff800030c2bd6, fffff880063c9850, 0}
    
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )
    
    Followup: MachineOwner
    ---------
    Do some disc checks.

    1. Update your SSD's Firmware (skip it, if it is not a SSD)
    2. Re-seat the sata and power.
    3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
    4. Seatool for dos: SeaTools | Seagate download
      Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

    Let us know the results.
      My Computer


  8. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #8

    Uninstalled Daemon tools and running the chkdsk now. Hopefully be done by the time I'm home at lunch time. Will let you know, thanks :)
      My Computer


  9. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #9

    Chkdsk finished running, running the SeaTools now. Will let you know :)
      My Computer


  10. Posts : 20
    Windows 7 ultimate x64
    Thread Starter
       #10

    SeaTools ran and passed on the LongTest
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 04:14.
Find Us