BSODs with multiple error codes on fresh install

Page 1 of 3 123 LastLast

  1. Posts : 11
    Windows 7 Professional 64-Bit
       #1

    BSODs with multiple error codes on fresh install


    Iím having some BSOD issues. I assembled this PC for a friend based on the Tomís Hardware 500$ Gaming PC from Q4 2012. The only piece of hardware that was different was the optical drive. System Builder Marathon, Q4 2012: $500 Gaming PC : Squeezing More Bang From The Same Buck

    Specs:
    CPU: Intel Pentium G850 (Sandy Bridge)
    Motherboard: ASRock H77 Pro4/MVP: LGA 1155, Intel H77 Express
    RAM: G.Skill Value Series 8 GB (2 x 4 GB) DDR3-1333 F3-10600CL9D-8GBNT
    Graphics: PowerColor AX7850 1GBD5-DH: Radeon HD 7850 1 GB
    Hard Drive: Western Digital WD3200AAKX: 320 GB, 7200 RPM SATA 6Gb/s Hard Drive
    Power Supply: Antec VP-450 450W
    Optical Drive: LITE-ON IHAS124-04

    After a few weeks she started getting a lot of BSODs, so I took it back and did a fresh install of Win 7 and updated all the drivers. The machine continues to get a lot of BSODs (with varying error codes) and I've been unable to figure out exactly what I can do to cause them (I got one while writing this post), but they typically happen when itís idle or at low load. At one point I had enabled driver verifier and could force the system to freeze-up (with video corruption), but couldn't get a BSOD with a minidump.

    I've scanned through the forums and have tried many of the troubleshooting methods that are listed, but I am happy to start at square-one to figure out the cause of this. I've enclosed a zip file from the diag tool to get started. Iím sure there is something I overlooked and would appreciate any assistance.
      My Computer

  2.    #2

    Code:
    BugCheck 4A, {73532e09, 2, 0, fffff880080f3c60}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
    Code:
    Usual causes:  Device driver
    This bugcheck indicates that a driver was returning from a system function call to user mode, when the IRQL level was higher than PASSIVE_LEVEL, as we can see from the parameters the current IRQL level was 2.

    Code:
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`05a6f000 fffff880`065e2000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Mar 29 02:27:04 2013 (5154FBF8)
        CheckSum:         00B25604
        ImageSize:        00B73000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Update to the latest WHQL driver available here - Latest AMD Catalyst Video Driver for Windows 7

    WHQL
    Release Date: April 24th 2013
    Version: 13.4
    In Device Manager: 12.104
    1. Download Driver
    2. Start Type: Device Manager
    3. Expand Display Adapters
    4. Right-Click Driver Name, Uninstall
    5. Reboot
    6. Run Driver Sweeper
    7. Reboot
    8. Install Downloaded Driver

    Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

    Driver Sweeper:
      My Computer


  3. Posts : 11
    Windows 7 Professional 64-Bit
    Thread Starter
       #3

    I followed the instructions above and while the driver date in device manager still shows 3/28/13 the Driver version matches up with the latest WHQL release. Should I install the beta drivers?

    I also received a few more BSODs in the meantime and I've uploaded another zip.
      My Computer

  4.    #4

    Code:
    BugCheck 19, {22, de00000000000000, 0, 0}
    
    GetPointerFromAddress: unable to read from fffff80003313100
    GetUlongFromAddress: unable to read from fffff800033131c0
    GetUlongFromAddress: unable to read from fffff80003281a38
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72e6 )
    Code:
    Usual causes:  Device driver
    The bugcheck indicates that a pool header is corrupt, this indicates there is a problem with the Windows memory allocation, drivers are the most the common cause for this bugcheck, however, RAM and hard-drive corruption can also be contributing problems.

    Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

    Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

    Test each RAM stick and every motherboard DIMM slot available.

    Arc said:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
    Run some hard-drive diagnostics and follow these steps:

    Find your hard-drive manufacturer and run their tests.

    Additional Tests:

    Post a screenshot of Crystal Disk Info summary:

    writhziden said:
    If you have an SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
    Check for any file system errors and bad sectors using Option #2 of:

    Use this command with Disk Check:

    Code:
    chkdsk C: /f /r
      My Computer


  5. Posts : 11
    Windows 7 Professional 64-Bit
    Thread Starter
       #5

    Memtest - I tested both sticks of RAM individually in each of the slots they're in and didn't get any errors.

    HDD - The Western Digital Lifeguard Diagnostic passed. I got another BSOD shortly after completing that diagnostic.

    Chkdsk - No file system errors or bad sectors

    CrystalDiskInfo - Included Screenshot

    The latest BSOD I received was during a full malwarebytes scan, so I'm going to see if I can replicate that again. I've included another diag zip.
      My Computer

  6.    #6

    Code:
    BugCheck 3B, {c0000005, fffff80003173d37, fffff88007374c50, 0}
    
    Probably caused by : memory_corruption ( nt!MiIdentifyPfn+317 )
    Code:
    Usual causes:  System service, Device driver, graphics driver, memory
    There's seems to be many graphics driver and graphics card related routines within the raw call stack, the drivers are being blamed, however, this could suggest a faulty graphics card.

       Warning
    Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

    Use GPU-z to monitor your GPU temperature, remember, to use the Log to File option seen in the screenshot (see download link website).

    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

       Information
      My Computer


  7. Posts : 11
    Windows 7 Professional 64-Bit
    Thread Starter
       #7

    After about 20 minutes into the Furmark test, I got a BSOD. I attached another zip. The GPU temp was holding steady at around 69C and the framerate was around 11 with a max of 15. Should I go ahead and enable driver verifier?
      My Computer


  8. Posts : 11
    Windows 7 Professional 64-Bit
    Thread Starter
       #8

    After enabling Driver Verifier, Windows would freeze at the welcome screen (with a lot of video corruption) every time I booted into windows. I booted into safe mode and turned off DV.
      My Computer

  9.    #9

    Code:
    BugCheck 1E, {ffffffffc0000005, fffff800030b5d79, 0, ffffffffffffffff}
    
    Probably caused by : memory_corruption ( nt!MiCheckForConflictingVadExistence+1d )
    Code:
    Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    What do you mean by video corruption? The screen going funny and distorted?

    Code:
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=1524]
    BiosMajorRelease = 4
    BiosMinorRelease = 6
    BiosVendor = American Megatrends Inc.
    BiosVersion = P1.50
    BiosReleaseDate = 12/06/2012
    SystemManufacturer = To Be Filled By O.E.M.
    SystemProductName = To Be Filled By O.E.M.
    SystemFamily = To Be Filled By O.E.M.
    SystemVersion = To Be Filled By O.E.M.
    SystemSKU = To Be Filled By O.E.M.
    BaseBoardManufacturer = ASRock
    BaseBoardProduct = H77 Pro4/MVP
    BaseBoardVersion =
    There most likely seems to be graphics related issue so far, either the drivers or the card itself, have you checked for a BIOS update? Many BIOS version updates will contain greater hardware stability and compatibility.

    Do you have a onboard graphics card or a spare graphics card to switch to?
      My Computer


  10. Posts : 11
    Windows 7 Professional 64-Bit
    Thread Starter
       #10

    I have updated the BIOS to the most recent version (1.50). There is onboard video (which I currently have disabled). I could try removing the AMD card and use that for a while. I also have a spare Nvidia card kicking around somewhere as well.

    Should I just use it normally for a while to see if the issue persists?

    Thanks so much for all your help on this so far. I really appreciate it.
      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 23:52.
Find Us