BSODs and now bios hangs for a miniute then loads

Page 1 of 3 123 LastLast

  1. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
       #1

    BSODs and now bios hangs for a miniute then loads


    the bios hangs while loading usb devices for 1 or 2 minutes, then windows loads. Win loads slower than before the bios hang issue appeared (this morning).

    When win appears to load completely, I get this error message (screen shot attached).

    Also attached is the DM Log Collector.

    TIA, John
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, 85f71820, 82f7bae0, 85be8718}
    
    Unable to load image \SystemRoot\system32\DRIVERS\amd_xata.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for amd_xata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys
    *** WARNING: Unable to verify timestamp for amd_sata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
    Probably caused by : amd_sata.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp 85be8718
    Irp is active with 7 stacks 5 is current (= 0x85be8818)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [ 16, 0]   0  0 85f71820 00000000 8be79564-00000000    
    	       \Driver\amd_sata	amd_xata
    			Args: 00000000 00000000 00000000 00000002
     [ 16, 0]   0  0 85f7b020 00000000 8c408e2c-86088af8    
    	       \Driver\amd_xata	CLASSPNP!ClasspPowerUpCompletion
    			Args: 00000000 00000000 00000000 00000002
    >[ 16, 2]   0 e1 860887f0 00000000 8bc46c36-00000000 Success Error Cancel pending
    	       \Driver\Disk	partmgr!PmPowerCompletion
    			Args: 00041100 00000001 00000001 00000002
     [ 16, 2]   0 e1 86089020 00000000 00000000-00000000    pending
    	      Unable to load image \SystemRoot\system32\DRIVERS\fltsrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for fltsrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
     \Driver\partmgr
    			Args: 00041100 00000001 00000001 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-860a7488    
    
    			Args: 00000000 00000000 00000000 00000000
    [BIOS Information (Type 0) - Length 24 - Handle 0000h]
      Vendor                        American Megatrends Inc.
      BIOS Version                  1702   
      BIOS Starting Address Segment f000
      BIOS Release Date             12/22/2010
      BIOS ROM Size                 200000
    Check for an updated BIOS for the motherboard at the manufacturer site. Check and ensure Windows 7 is fully updated. Also ensure all USB devices have updated drivers.
      My Computer


  3. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #3

    Hi Golden, thanks for the offer to help.

    While there is a bios update, I must first admit I'm nervous about updating the bios. Also, to avoid updating my bios as a whole, but keeping my system healthy, I've downloaded and installed need drivers from the MB's website, so they should be current.

    Windows 7 is fully updated, and all USB devices have updated drivers.

    Let me tell you what I believe caused the bios hang while loading the USB drivers. My wife's desktop died several days ago (AMD heatsink and CPU fan), so I was removing her data from various drive to store on my machine until I get her a replacement.

    Her C:\ drive was on a SSD, so I bought a USB 3.0 to 2.5" SATA III Hard Drive Adapter Cable to help with the data transfer. She also had data on an external 3.5" drive, and in a moment of supreme stupidity, I connected this 3.5" drive to the SATA end, and put the other cable end (the usb) into a handy usb port on my machine forgetting that the usb port lacks the power necessary to spin the drive (unlike the smaller 2'5" SSD).

    Windows saw the drive as connected, but naturally couldn't read it. This is when I realized my mistake and unplugged the drive from my machine.

    I thought I lucked out, and caused no damage, but since this happened the bios hangs for a 2-3 minutes. When windows does load, I get 'unknown device' message I captured in the JPEG in my original post.

    In windows, I've tried disabling the device, and tried uninstalling it; but the bios still hangs and apparently tells windows about it which makes windows try to install the 'unknown device's" driver, which windows does with the error message I put in the screen shot in my original post.

    Sorry for the lengthy explanation, but I thought it was necessary for a complete understanding of my situation.

    While I maybe phobic about updating my bios, from at least my limited knowledge, I wonder if the bios update would get rid of the bios's attempt to load this 'phantom' driver.

    Thanks again for your interest and help.
    Last edited by jm386; 28 Jan 2016 at 14:55. Reason: corrected typo
      My Computer


  4. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #4

    My apologies Golden,

    After researching my mb's manual on the bios settings, I realized a lot has changed in the last 10 years or so and your solution does seem to be the best AND easiest.

    I had no idea I could save the current bios settings on my mb's rom before I flashed to the upgraded bios so I could always revert back to the current settings and live with the POST hang but without jeopardizing the bootabliity of my machine.

    Man, I feel like a military veteran with PTSD reacting to a car's backfire. I don't even remember the bad experience I had with updating the bios, but it sure has stayed with me.

    I will practice caution and save my current, albeit hobbled bios settings prior to upgrade flashing the bios.

    I do still remain paranoid (hey, even paranoids CAN have real enemies) enough to do this outside the windows environment with a usb thumb drive containing the bios update.

    Naturally, as luck would have it, my MB's web site is down undergoing 'enhancements' today, so I don't know how long until I can post that this thread has been 'solved', but whenever I do the bios update and find everything is ok, I will.

    Thanks again Golden
      My Computer


  5. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #5

    Ok, I've updated the bios to the latest version, but nothing has changed.

    During POST, the machine still hangs for 20 seconds 'initializing usb's , then boots nicely into windows, whereupon windows hangs for another 20 seconds, then (mouse, scanner, keyboard and other usb devices) load perhaps a minute later, which is not normal for my machine.

    I described (two posts above this one) how I had mistakenly tried to connect a 3.5" sata drive into one of the top usb ports on my case --- do you think I have permanently damaged the MB?

    Thanks again, John

    PS: Oddly enough, no more BSODs for the last several days, and no more kernal errors and NTFS error 55s. I think this is because I disconnected both my external drives (ESata and USB) to reduce the complexity of the system.

    I find this interesting since the DM log you pasted in your reply to me mentioned the amd_sata.sys
      My Computer


  6. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #6

    Here's an update with very good news ---- after a further reboot along with a overnight shut down, the machine loads the usbs just as it did prior to my problems in both POST and windows! Thanks Golden!

    I'm unsure though regarding the BSOD issues since your "Bugcheck Analysis" showed driver problems in the sata.sys, the x_sata.sys and the fltsrv.sys

    Should I mark this thread as 'solved' and start a new BSOD thread, or should we continue here?

    Thanks again.
      My Computer


  7. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #7

    Keep it here for now.

    Please do the following:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
      My Computer


  8. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #8

    OK Golden, just started Driver Verifier a few minutes ago.

    Thanks again, John
      My Computer


  9. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #9

    Well, I ran Driver Verifier for a little over 24 hrs and nothing happened. Even the system seemed to run normally, not sluggishly as expected.

    After a while of wondering if the process is running, I used Sysinternal's Process Explorers to see if verifier.exe was active. This utility did NOT show it running.

    Is this normal, or did I somehow screw up the loading of Driver Verifier. I don't know but I was meticulous, and in following the steps at the finish, the Driver Verifier utility did ask me to restart the machine, which I did.


    Can you advise?

    I forgot to mention that during this period, no BSODs occurred.
    Last edited by jm386; 04 Feb 2016 at 17:43. Reason: Forgot to mention....
      My Computer


  10. Posts : 23
    Microsoft Windows 7 Home Premium 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #10

    I just had a BSOD about an hour ago. It seemed to coincide with Acronis True Image 2014 starting up to do a scheduled disk image backup of my wife's laptop to my machine over my wired network.

    fltsrv.sys is part of Acronis True Image 2014 and in your Bugcheck Analysis I see fltsrv.sys mentioned.

    Attached is the most recent DM Log.

    John
      My Computer


 
Page 1 of 3 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 16:58.
Find Us