Navigation section
Windows 7 Troubleshooting Frequent BSOD Errors: Need Assistance!
Solution
- Joined
- Jan 28, 2013
- Messages
- 2,419
Hi,
You'll have to wait for a Dump File Analyst to examine your Dump files, as I don't have the correct app to do so.
It would be helpful for the rest of us if you could include a photo of your BSOD screen. If you have a smartphone or camera-phone you can snap a pic when it occurs and post back here.
In the meantime there are some things you can do to help yourself since you have a Custom built system, you are more likely to be willing to go through some of these tests.
To test your Hard Drives, download the free SEATOOLS* drive test program from seagate.com and run BOTH short and long tests. If SEATOOLS returns any errors, your Hard Drive has failed and must be replaced. Attempt to make a Backup of all needed Personal Information such as documents, photos, music, movies, E-mail, etc. to external media before removing the drive from the PC. If you are unable to do this, remove that drive and replace it. Set that failed drive aside for further data recovery.
Reinstall Windows Win7 from your installation Media and retest. If the drive did fail, this should solve your problem.
To test your RAM sticks, download the free MEMTEST memory test program via Google. Test each stick of RAM individually for a minimum of 8 passes. If MEMTEST returns any errors you have a failed RAM stick and it must be replaced. Test ALL the RAM sticks you have and then reinsert all of them once they pass the MEMTEST, and run MEMTEST one final time with all (1-4 typicall) sticks installed. If MEMTEST returns any errors after the 8 passes, you'll need to begin replaced pairs of RAM sticks with new ones until MEMTEST completes without errors with all sticks installed.
I also noticed that you have 3 hard drives hooked up to this PC; and it appears that the Samsung 250GB SSD drive is the boot drive. You have a 2nd & 3rd drive hooked up to the same Motherboard. Basic troubleshooting dictates a test you may not have tried (a "can't see the forest for the trees" kind of thing). And this is to test your PC with only the Samsung boot drive. Does it also give you a BSOD? If it does, is it the same exact errors and code? Or is it different?
If you get no BSOD on boot without the 2 secondary drives attached, you either have a failed drive, or you have software running (such as an App that uses one of those secondary drives to run or for storage) that has failed and needs to be removed or reinstalled. With this basic configuration, it tells you that your boot drive (the Samsung SSD) and your RAM sticks are most likely ok. You can then begin further troubleshooting to test those 2 secondary drives hardware first and then software.
If you do still get a BSOD, especially the exact one you have been getting all along in this test configuration, most likely the problem is with the Samsung boot drive having failed, or one of your RAM sticks failed. You can use the above tests on the SSD drive and the RAM sticks (SEATOOLS & MEMTEST), to determine if any of that hardware is bad. If you do find a failure on the drive, it must be replaced. Same with any Memory sticks. Re-test for your BSOD. Replacing the SSD drive will of course require a Win7 reinstallation from RECOVERY MEDIA or a manual windows reinstallation. If you did find failed hardware (drive or RAM), and replaced those component(s) and now your BSOD is gone--that's now fixed! You found the problem. Of course this is somewhat unlikely as most of your system and components appear to be quite new.
If you do find faulty components and replace them and the BSOD persists, most likley it's a corrupted driver problem, often from a Windows update. You'll then need to troubleshoot your drivers, and there is a complex troulbeshooting method we can recommend for this; post back for that. Often, adding new hardware will cause BSODs; so you will have to look at any other new hardware you've added to the PC since you originally built it. Start with the drivers from those devices first. If you've added no new hardware to the PC, the next thing to look at is software. Often BSODs are caused by virus or malware attacks. You'll need to scan your boot drive for any viruses, spyware viruses, or Rootkits. Use whatever antivirus you currently have installed. If you do not have one or it is expired, I suggest you go to Trendmicro.com and use their Housecall online scanner to scan your boot drive--it is completely Free. Then I suggest you download Malwarebytes antispyware from malwarebytes.com and scan your boot drive again for spyware viruses. TrendMicro also has a free Rootkit scanner called Rootkit Buster which you should also download and run. All of these programs are free, so the only cost here is your time to obtain and run them.
If any viruses or malware are found, you must remove them or quarrantine them; and then re-test for your BSOD on the minimal 1-drive configuration I've been speaking of above. If the BSOD abates, congrats! You've repaired the damage from the virus(es). If the viruses are all removed or none were found, and retesting still shows the BSOD. You'll have to investigate via an in-depth driver troubleshooting to find it the problem device/driver and rectify it.
Lastly, after testing your drives, RAM, and for viruses/malware, and the BSOD persists, there is an easy way to figure out where the problem is. And that's a Windows OS reinstall. I would suggest that you backup all the critical data from your boot drive, then reinstall your Win7 OS from RECOVERY MEDIA or a manual Windows reinstall. If the BSOD abates, most likely it was an update that clobbered 1 or more of your drivers, and corrupted Registry keys. Rebuild your system and reattach your secondary drives; retest for BSODs once more. At this point if BSOD persists, I would replace the boot drive with a brand new drive and repeat the Win7 OS install. If BSOD abates, your boot drive had a failure that wasn't caught by testing, which can occasionally happen.
Let us know how it goes.
<<<BIGBEARJEDI>>>
You'll have to wait for a Dump File Analyst to examine your Dump files, as I don't have the correct app to do so.
It would be helpful for the rest of us if you could include a photo of your BSOD screen. If you have a smartphone or camera-phone you can snap a pic when it occurs and post back here.
In the meantime there are some things you can do to help yourself since you have a Custom built system, you are more likely to be willing to go through some of these tests.
To test your Hard Drives, download the free SEATOOLS* drive test program from seagate.com and run BOTH short and long tests. If SEATOOLS returns any errors, your Hard Drive has failed and must be replaced. Attempt to make a Backup of all needed Personal Information such as documents, photos, music, movies, E-mail, etc. to external media before removing the drive from the PC. If you are unable to do this, remove that drive and replace it. Set that failed drive aside for further data recovery.
Reinstall Windows Win7 from your installation Media and retest. If the drive did fail, this should solve your problem.
To test your RAM sticks, download the free MEMTEST memory test program via Google. Test each stick of RAM individually for a minimum of 8 passes. If MEMTEST returns any errors you have a failed RAM stick and it must be replaced. Test ALL the RAM sticks you have and then reinsert all of them once they pass the MEMTEST, and run MEMTEST one final time with all (1-4 typicall) sticks installed. If MEMTEST returns any errors after the 8 passes, you'll need to begin replaced pairs of RAM sticks with new ones until MEMTEST completes without errors with all sticks installed.
I also noticed that you have 3 hard drives hooked up to this PC; and it appears that the Samsung 250GB SSD drive is the boot drive. You have a 2nd & 3rd drive hooked up to the same Motherboard. Basic troubleshooting dictates a test you may not have tried (a "can't see the forest for the trees" kind of thing). And this is to test your PC with only the Samsung boot drive. Does it also give you a BSOD? If it does, is it the same exact errors and code? Or is it different?
If you get no BSOD on boot without the 2 secondary drives attached, you either have a failed drive, or you have software running (such as an App that uses one of those secondary drives to run or for storage) that has failed and needs to be removed or reinstalled. With this basic configuration, it tells you that your boot drive (the Samsung SSD) and your RAM sticks are most likely ok. You can then begin further troubleshooting to test those 2 secondary drives hardware first and then software.
If you do still get a BSOD, especially the exact one you have been getting all along in this test configuration, most likely the problem is with the Samsung boot drive having failed, or one of your RAM sticks failed. You can use the above tests on the SSD drive and the RAM sticks (SEATOOLS & MEMTEST), to determine if any of that hardware is bad. If you do find a failure on the drive, it must be replaced. Same with any Memory sticks. Re-test for your BSOD. Replacing the SSD drive will of course require a Win7 reinstallation from RECOVERY MEDIA or a manual windows reinstallation. If you did find failed hardware (drive or RAM), and replaced those component(s) and now your BSOD is gone--that's now fixed! You found the problem. Of course this is somewhat unlikely as most of your system and components appear to be quite new.
If you do find faulty components and replace them and the BSOD persists, most likley it's a corrupted driver problem, often from a Windows update. You'll then need to troubleshoot your drivers, and there is a complex troulbeshooting method we can recommend for this; post back for that. Often, adding new hardware will cause BSODs; so you will have to look at any other new hardware you've added to the PC since you originally built it. Start with the drivers from those devices first. If you've added no new hardware to the PC, the next thing to look at is software. Often BSODs are caused by virus or malware attacks. You'll need to scan your boot drive for any viruses, spyware viruses, or Rootkits. Use whatever antivirus you currently have installed. If you do not have one or it is expired, I suggest you go to Trendmicro.com and use their Housecall online scanner to scan your boot drive--it is completely Free. Then I suggest you download Malwarebytes antispyware from malwarebytes.com and scan your boot drive again for spyware viruses. TrendMicro also has a free Rootkit scanner called Rootkit Buster which you should also download and run. All of these programs are free, so the only cost here is your time to obtain and run them.
If any viruses or malware are found, you must remove them or quarrantine them; and then re-test for your BSOD on the minimal 1-drive configuration I've been speaking of above. If the BSOD abates, congrats! You've repaired the damage from the virus(es). If the viruses are all removed or none were found, and retesting still shows the BSOD. You'll have to investigate via an in-depth driver troubleshooting to find it the problem device/driver and rectify it.
Lastly, after testing your drives, RAM, and for viruses/malware, and the BSOD persists, there is an easy way to figure out where the problem is. And that's a Windows OS reinstall. I would suggest that you backup all the critical data from your boot drive, then reinstall your Win7 OS from RECOVERY MEDIA or a manual Windows reinstall. If the BSOD abates, most likely it was an update that clobbered 1 or more of your drivers, and corrupted Registry keys. Rebuild your system and reattach your secondary drives; retest for BSODs once more. At this point if BSOD persists, I would replace the boot drive with a brand new drive and repeat the Win7 OS install. If BSOD abates, your boot drive had a failure that wasn't caught by testing, which can occasionally happen.
Let us know how it goes.
<<<BIGBEARJEDI>>>
- Joined
- Aug 28, 2007
- Messages
- 36,160
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa800be23240, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+338a4 )
Followup: MachineOwnermost of your dump files were like the above which blames a severe memory management issue as being the cause of the bsod. You also have a Bugcheck 24 which can mean NTFS errors as well as a dump file blaming this driver:
e22w7x64.sys Wed Mar 26 15:59:01 2014: Bigfoot Killer network driver. A later version of this driver was only released a few days ago:
Link Removed
You can also download drivers from the motherboard support page too:
http://uk.msi.com/support/mb/H97-GAMING-3.html#down-driver&Win7 64
You also have another driver which could possibly cause issues:
dtsoftbus01.sys Fri Feb 21 09:49:36 2014: Daemon Tools driver. Possible BSOD issues in Win7 uninstall to test.
Test your HDD for errors using chkdsk:
Link Removed
If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/
To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.
Lastly.. Please post any further dump files and I shouldn't bother with posting a photograph as it isn't needed.