Solved Windows 7 BSOD

[Jim Tol]

Hello,

I recently build a pc which initially worked fine, but after a short while bsods started appearing. When they appeared, they came in big numbers, not making my system stable for more than 30 minutes tops. After some tinkering (updating drivers, adjusting bios values) with some settings however I always managed to get my system stable for a couple of days before the bsods starting again. This has been so the past month, so I finally come here out of desperation. Any help on this would be greatly appreciated.

I recently replaced my ram memory but it turned out that it was not the memory that caused the blue screens. However, I seem to get less blue screen when I use only one strip of 2GB memory instead of two.

My system specs are:
Windows 7 Ultimate x64, Full Retail
Processor: AMD Phenom II X6 1055T Processor 2.80 GHz
Memory: 2x 2GB DDR3-1333G
Video Card: Asus Eah-5670, 512 MB
Motherboard: MSI 870A-G54 - Socket AM3 - ATX


I hope that I have provided you with enough information. I have attached the dmp files in the rar archive. Any help on this issue is greatly appreciated!

Best,

Jim

 

[usasma]

7 memory dumps, 5 different BSOD error codes, 4 different causes blamed.
this is the beginning of a pattern that may indicate a hardware/compatibility problem.

There are no Windows Updates on your system. Please visit the Windows Updates site and get all the updates for your system (a minimum of 55 for some systems, many more for others).

The drivers for this device aren't installed:

Universal Serial Bus (USB) Controller PCI\VEN_1033&DEV_0194&SUBSYS_75991462&REV_03\FFFFFFFFFFFFFFFF00 The drivers for this device are not installed.

Please visit the PC Manufacturer's website and download the motherboard/chipset drivers for your system.

It is possible that the following older drivers may be causing your problems.
Please either REMOVE or Update the older drivers listed below.

HOW TO FIND DRIVERS:
DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

The most common drivers are located on this page: Driver Reference
If you can't find the driver, post back and we'll see what we can find.

Here's the older drivers that were found in the memory dump files:

[font=lucida console]
Rtnic64.sys  Mon Mar 31 01:39:38 2008 (47F0791A)
 - Realtek Ethernet NIC driver
 - [url=http://www.carrona.org/dvrref.html#Rtnic64.sys]Driver Reference[/url]

FLASHSYS64.sys Fri Feb 15 03:00:23 2008 (47B54697)
 - MSI driver file, most likely associated w/MSI Live Udpate
 - [url=http://www.carrona.org/dvrref.html#FLASHSYS64.sys]Driver Reference[/url]
[/font]

Lot's of errors relating to your Norton Internet Security in the MSINFO32 file and in the memory dumps. Please do the following:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall 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: KB Article Not Found
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

You have had either Daemon Tools or Alcohol 120% installed on your system. If it's not uninstalled yet, please do so now - it is a known cause of BSOD's on Win7 systems. Also, once the program is uninstalled, please run this free tool to remove the offending sptd.sys file: DuplexSecure - FAQ - Remove 64 bit sptd.sys

If that doesn't stop the BSOD's, then please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 21 15:44:50.839 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:27.119
Probably caused by : SRTSP64.SYS ( SRTSP64+7b198 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0687b198 fffff880`08cfa680 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 21 08:03:07.375 2010 (UTC - 5:00)
System Uptime: 0 days 1:02:28.408
Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+286 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
Bugcheck code 0000000A
Arguments fffff6fb`40080008 00000000`00000000 00000000`00000000 fffff800`02bacb76
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 21 06:59:58.661 2010 (UTC - 5:00)
System Uptime: 0 days 0:07:28.941
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  sppsvc.exe
Bugcheck code 0000000A
Arguments fffff680`00081958 00000000`00000000 00000000`00000000 fffff800`02a93a37
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 18 13:07:32.948 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:54.008
Probably caused by : rdbss.sys ( rdbss!RxSpinUpRequestsDispatcher+c6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`0c39cf98 00000000`00000002 00000000`00000001 fffff800`02a82c9c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 18 13:04:51.262 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:13.322
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffff300`092faf18 00000000`00000001 fffff880`02e9810e 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 18 05:15:50.739 2010 (UTC - 5:00)
System Uptime: 0 days 0:04:47.066
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339e3 )
BUGCHECK_STR:  0x1a_3452
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
Bugcheck code 0000001A
Arguments 00000000`00003452 00000000`060c3000 fffff700`010a4210 fb000000`0b419c66
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 18 05:02:45.230 2010 (UTC - 5:00)
System Uptime: 0 days 0:14:11.557
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  taskmgr.exe
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`00034b05 00000000`00000000 00000000`00034c05
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[Jim Tol]

Thanks alot for your response! I have updated the drivers you mentioned, hoping no more crashes will occur. It is however weird that my files indicated that there were no windows updates installed on my system, since the crashes I made sure to check for and install updates every day. So, apart from two which crashed when I tried to install them all windows updates should have been there...

Also, yesterday a new problem arrived. I was getting 0xC0000005 crashes when I ran different programs (games and programming environments). They usually stated that the memory at a certain pointer could not be read, I therefore assusmed that there still was a problem with my RAM memory. I checked both my memory banks with my memtest which gave no errors. However, the system did become more stable, which means no more 0xC0000005 crashes, when using just one of the two banks. Which made me almost sure that there was a problem with the other bank.

I am however still in doubt because the memtest gave no problems at all which could indicate that the problem was in the software all along. Which is weird because both banks are exactly the same so they should be affected the same by the installed software. Ill try both banks again today to see if I can nail it down.

Thanks again for your help, Ill keep you posted wheter it is running fine or crashing

 

[CarlTR6]

Did you uninstall Norton as John suggested above? that can be a source of memory corruption especially since it was mentioned in the dumps ans msinfo. If you have not done so, bite the bullet ans uninstall it.

 

[Jim Tol]

Yes I uninstalled it. System is more stable now! The problems with my memory continued however. One strip of my ram memory is working correctly, the other one gives errors at certain points (especially when playing games). I guess my problems were partly driver related and partly hardware related, this made it hard to track down. Thanks for all the help!

 

[CarlTR6]

You are welcome.