Numerous BSODs after updating hardware


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    Numerous BSODs after updating hardware


    I recently upgraded just about all of my computer's hardware. Since then, i've been having seemingly random crashes and BSODs that I just cant quite figure out.

    I originally thought it had something to do with the drivers of my PC as i did a copy of my old harddrive to the new SSD I aquired but after a full format and reinstall of Windows 7 Home Premium x64, I was still getting BSODs. Some of my error reports pointed to faulty video card hardware, so I reinstalled my older Nvidia Geforce 550 Ti instead of the EVGA Geforce GTX 660. Unfortunately, the blue screens and crashes are still happening.

    I'm at a loss as to where to go from here, so i'm here to ask for help!

    Thanks.

    Here is the zip requested by the posting instructions: Attachment 297399

    *Edit* Forgot to say that i've run a couple memtests and they've all passed with no errors so far.
    Last edited by Zanndar; 14 Dec 2013 at 17:27. Reason: forgot some info
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Follow this:
    Arc said:
    Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features.
    Then Uninstall the driver from device manager.

    1. Right click on "my computer" icon and click "manage" on the context menu.
    2. It will open the "computer management" window.
    3. Select "Device Manager" in the left pane, It will list all the existing devices up.
    4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
    5. Select one Intel device item under it, right click, uninstall.
    6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
    7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.
    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.
    Arc said:
    Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.
    Code:
    nvlddmkm.sys Mon Nov 11 19:24:05 2013 (5280DA75) 
    nVidia Video drivers 
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

    If you are overclocking any software, please stop and uninstall the software below:

    gdrv.sys Fri Mar 13 09:22:29 2009 (49B9D175)
    Gigabyte Easy Saver - mobo power utility driver
    Driver Reference Table - gdrv.sys

    AppleCharger.sys Tue Feb 19 10:17:09 2013 (5122FCC5)
    GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - uninstall to test
    Driver Reference Table - AppleCharger.sys

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
    XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
    Driver Reference Table - xusb21.sys

    Reduce items at start-up: Startup Programs - Change

    Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

    Run Disk Check on your Hard Drive(s): Disk Check

    Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

    ESET online scanner: Free Online Virus Scanner | ESET

    Check for heating issues using Speccy or HWmonitor

    Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

    If this does not provide stability. Test RAM.

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.


    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.


    Code:
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sun Dec 15 00:52:32.836 2013 (UTC + 6:00)
    System Uptime: 0 days 0:02:11.617
    BugCheck 1E, {ffffffffc0000005, fffff80003082ac5, 0, ffffffffffffffff}
    Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  svchost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sun Dec 15 00:20:29.211 2013 (UTC + 6:00)
    System Uptime: 0 days 0:00:19.992
    BugCheck 50, {ffffffffffffffd0, 1, fffff800030e0dac, 0}
    *** WARNING: Unable to verify timestamp for UsbCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for UsbCharger.sys
    Probably caused by : UsbCharger.sys ( UsbCharger+164d )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Dec 14 21:16:36.570 2013 (UTC + 6:00)
    System Uptime: 0 days 10:08:04.351
    BugCheck 3B, {c0000005, fffff80003086ba9, fffff88007048030, 0}
    Probably caused by : win32k.sys ( win32k!NtUserGetForegroundWindow+17 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  DATA.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Dec 14 08:56:38.346 2013 (UTC + 6:00)
    System Uptime: 0 days 2:06:30.127
    BugCheck 1000007E, {ffffffffc0000005, fffff800030c3504, fffff88009c22528, fffff88009c21d80}
    Probably caused by : cdd.dll ( cdd+95a5 )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      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 06:56.
Find Us