Windows 7 Getting BSoD

[Darthrob81]

I was getting blue screen of death mostly when leaving my comp on to download games overnight. Was also getting corrupted files here and there so i decided to get a new hard drive. Installed and first night BSoD. Have included file with all the info. Help would be much appreciated!!!

 

[usasma]

Only 113 Windows Updates installed. Most systems have 130 to 140 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

Lot's of Norton drivers in the memory dump, please try this to rule out Norton:

Anti-Virus Removal:
Please do the following:
- download a free anti-virus for testing purposes: Link Removed If using Windows 8, enable Windows Defender and the Windows Firewall instead.
- un-install the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free anti-virus (if using Win8, enable Windows Defender), then check to ensure that the Windows Firewall is turned on.
- perform a full system scan to ensure that no malware has snuck onto your system while the anti-virus was malfunctioning.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Death Adder driver dates from 2007 - these are known to cause BSOD's on Windows systems. Please visit the Razer website and download a fresh copy of the latest Win7 compatible driver for your Death Adder.

Please uninstall the Western Digital software. The 2008 drivers (which you have) are known to cause BSOD's on some Win7 systems.

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! :

Must be updated or removed:
dadder.sys Thu Aug 2 05:33:03 2007 (46B1A4CF)
DeathAdder Mouse driver
Link Removed

Must be removed:
wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver[br]2008 driver version has known BSOD issues in Win7
Link Removed

Must be removed. Can reinstall (if needed) once the system is stabilized:
AiCharger.sys Wed Oct 20 08:00:33 2010 (4CBED9E1)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sun Feb 10 12:14:12.231 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021013-5647-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 17:34:19.027[/B]
Probably caused by :[B]memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )[/B]
BugCheck [B]50, {fffff683fbfffd98, 0, fffff80002ea99d7, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff683fbfffd98, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ea99d7, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3417[/B]
  BIOS Version                  0908
  BIOS Release Date             11/16/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  9 09:16:47.659 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020913-5522-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 10:28:47.455[/B]
Probably caused by :[B]memory_corruption ( nt!MiUpdateWsle+122 )[/B]
BugCheck [B]50, {fffff680040ab1f0, 0, fffff80002ef72d2, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff680040ab1f0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ef72d2, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: [B]X64_0x50_nt!MiUpdateWsle+122[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3417[/B]
  BIOS Version                  0403
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  8 12:01:24.887 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020813-8190-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 17:02:46.104[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
BugCheck [B]1A, {41790, fffffa800615d7a0, ffff, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800615d7a0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3410[/B]
  BIOS Version                  0403
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Sun Feb 10 12:14:12.231 2013 (UTC - 5:00)**************************
[COLOR=RED][B]dadder.sys                  Thu Aug  2 05:33:03 2007 (46B1A4CF)[/B][/COLOR]
[COLOR=RED][B]wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
EuGdiDrv.sys                Tue Sep 15 03:13:53 2009 (4AAF3EB1)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
ICCWDT.sys                  Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys                    Mon Aug 23 21:53:02 2010 (4C7325FE)
[COLOR=RED][B]AiCharger.sys               Wed Oct 20 08:00:33 2010 (4CBED9E1)[/B][/COLOR]
ndisrd.sys                  Fri Aug 12 06:14:50 2011 (4E44FD1A)
ASUSFILTER.sys              Tue Sep 20 11:46:33 2011 (4E78B559)
asmtxhci.sys                Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys                Wed Nov  2 23:00:32 2011 (4EB203D0)
iaStor.sys                  Tue Nov 29 22:39:19 2011 (4ED5A567)
RTKVHD64.sys                Tue Dec 13 05:24:54 2011 (4EE727F6)
iusb3hub.sys                Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3xhc.sys                Fri Jan 27 04:35:28 2012 (4F226FE0)
iusb3hcs.sys                Fri Jan 27 04:37:23 2012 (4F227053)
Rt64win7.sys                Fri Feb  3 08:00:02 2012 (4F2BDA52)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
AtihdW76.sys                Tue Nov  6 16:41:51 2012 (5099841F)
atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  9 09:16:47.659 2013 (UTC - 5:00)**************************
IDSVia64.sys                Thu May 12 10:19:05 2011 (4DCBEC59)
BHDrvx64.sys                Thu May 12 17:05:27 2011 (4DCC4B97)
SYMDS64.SYS                 Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMNETS.SYS                 Sat Nov 12 16:11:53 2011 (4EBEE119)
Ironx64.SYS                 Mon Nov 14 21:00:53 2011 (4EC1C7D5)
SYMEVENT64x86.SYS           Tue Nov 22 13:30:48 2011 (4ECBEA58)
SYMEFA64.SYS                Fri May 18 21:29:56 2012 (4FB6F794)
ccSetx64.sys                Wed Jun  6 23:00:55 2012 (4FD01967)
SRTSPX64.SYS                Mon Jul  2 14:20:37 2012 (4FF1E675)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb  8 12:01:24.887 2013 (UTC - 5:00)**************************
SYMNETS.SYS                 Tue May  3 21:10:14 2011 (4DC0A776)
SYMEVENT64x86.SYS           Wed May  4 23:16:30 2011 (4DC2168E)
Ironx64.SYS                 Fri May 13 20:08:04 2011 (4DCDC7E4)
SYMEFA64.SYS                Mon May 16 20:33:48 2011 (4DD1C26C)
SRTSPX64.SYS                Fri May 20 21:49:23 2011 (4DD71A23)
[/font]

Link Removed
Link Removed
Link Removed
EuGdiDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Darthrob81]

Windows update says I have everything clicking it multiple times. The firmware on the ssd is up to date. Updated the mouse and took off those other drivers. Going to see how it goes. One thing. Tried memtest 86 and it gives me lots of errors and freezes on test 8 with 4 sticks in. If i do sticks one at a time they pass in every slot. With 2 they also pass, but with 4 it fails.

 

[usasma]

Are there any BIOS updates available for your motherboard?

Is your motherboard capable of handling that number of sticks in that size? You can look that up at RAM Memory Upgrade: Dell, Mac, Apple, HP, Compaq. USB drives, SSD at Crucial.com

Have you tried setting the timings/settings/voltages that are recommended by the RAM manufacturer? In other words, try NOT using the Auto setting for RAM.

What is the make and model of your motherboard?

 

[Darthrob81]

The bios is the most current version. My board is a p8z77-v lk asus. The board wanted to auto put the ram to 1333 when it says 1600. I had changed that but didn't fix. Voltages and timings are correct

 

[usasma]

Can you run Prime95 ( Link Removed ) on the sticks individually? Let each test run for a minimum of 4 to 6 hours (24 is better) - to see if you get any errors.

Also, try running Driver Verifier according to these instructions: Link Removed

There were similar problems with BIOS's and mobo's back when Vista first came out - but I haven't seen many of these since. You may want to check with the memory manufacturer to see what they recommend.

 

[Darthrob81]

I ran memtest 86 more extensively and the sticks fail in the first slot but pass in the other three. Should I still do the other prime95 test or is memtest 86 reliable enough? Should I just count that slot as dead on my mobo?

 

[Darthrob81]

Tried putting 2 sticks in the slots that the manual recommended, which didn't include the slot that was getting errors. Left on for a bit and came back to blue screen, then wouldn't load for a couple of tries.

 

[usasma]

MemTest86+ tests the RAM, Prime95 stresses the RAM.
It's possible for memory to pass the MemTest86+ and then fail Prime95
I suggest running both tests just to be sure.

 

[GeneralHiningII]

Do you have any other sticks available to try out on your motherboard?

Adding on to John's first post/analysis:

Two dumps point to Steam.
Have you tried:
Reinstalling Steam.
Verifying Game Caches of each Game.
Also try (sounds bad, but it may be the cause) reinstalling your games.
-------- It says memory management errors on Steam - open Task Manager (ctrl+alt+delete, start task mgr) and under the "Processes" tab, see how much memory "Steam.exe" is using.
Also, on the bottom of the Task Manager window, see how much of your CPU and Physical Memory is being used, when playing a game, Steam on idle, etc.

The first dump shows svchost.exe - memory management again.

Svchost.exe manages your services - whichever service needs to access a server/internet, svchost controls that.
Try this:
in start menu's search bar - search "msconfig".
Under the "startup" tab - uncheck ALL of the services (except any that are crucial - examples of crucial ones: antivirus, firewall///examples of unnecessary ones: Adobe Update, Google Update)
Restart computer and see if the problem still repeats

Of course, once you've tried all these, collect some NEW BSODS and upload them again.


\\
//
Edit:

I just looked through the thread one more time - it seems you are running Vista. The instructions I gave you apply to Win7, but you should still be able to perform them in Vista, with slight tweaks. Sorry for any inconvenience
\\

 

[Darthrob81]

I am running windows 7. I was running steam at the time of a couple of crashes, but I doubt that its the problem. I have just recently installed everything on the computer after buying two new hard drives because of this issue. It was happening before two. So not only has steam been reinstalled already, but the hard drives have been changed out as well. I'll download the prime 95 but they weren't passing memtest86. 4 sticks fail and the first slot fails.

Looking at task manager steam idling is 1-10% and memory 1.89gb Haven't tried playing a game since i redid the comp.
Will check the services and see what that does.

Edit: Honestly after looking through the list of services i'm not sure which ones i should take or leave.

 

[GeneralHiningII]

Well if you were running Steam at the time of the crashes, it could be a possibility. AND, seeing as we don't have any other evidence pointing to any other program (yet), for now we'll blame Steam.

Uninstall Steam (if you have any BIG games installed, maybe copy them on to a separate drive and leaving it there) for now, and see if you still get any crashes.

With my steam: idles at about 22,000K - when playing a game, 23~. So I'm still thinking that Steam's an issue right now.


As for services:
This is more of a test to see which ones are causing problems/hogging memory - if none of them/one of them reports an error, then we just remove that service and enable the rest.

If you're having troubles, upload a screenshot and I can give recomm.'s on which to take/leave.