Solved Random BSODs for quite some time now

[archimonde]

I've been having random BSODs for quite some time now, some 6 months in the past (or they appear to me to be random). However, they happen most frequently while browsing (or just having my browser open) or using multiple applications at once with the browser open. I like to have many tabs open in my browser (Chrome), sometimes even 20 or so. BSODs are, however, not restricted to Chrome and browsing. They happen almost in any circumstance. E.g. I'd stick a flash drive into the usb port and it would happen, open a video clip from a local hdd etc... I've tried reinstalling the OS but the same BSODs are still there.
I suspect on PSU, bad cpu cooling, faulty RAM or MoBo, even bad graphic drivers, so I really don't know where to start... I'd appreciate any help, and, if you need some more info, please say so, I'll provide it!

Update: Ok, it was set to Kernel Memory Dumps, I've reset it to Small Memory Dumps. I'll collect data and check again when I have it.

Update 2: I had 3 more BSODs in the last 3 days. I believe the system has collected Small Memory Dumps in these cases, so here you go, I hope these helps!

 

[koolkat77]

Welcome,
Please configure the system to collect Small Memory Dumps following this tutorial: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[archimonde]

Ok, I've updated the post with the new information. I hope it helps!

 

[koolkat77]

[FONT="Lucida Console"]Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Debug session time: Sat Jun 21 13:16:13.446 2014 (UTC + 6:00)
System Uptime: 0 days 0:13:08.506
BugCheck A, {118, 2, 1, 830c78c6}
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+98 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  TWCU.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun 20 16:53:23.578 2014 (UTC + 6:00)
System Uptime: 0 days 1:01:25.263
BugCheck 1A, {8884, 8523dd48, 8516e5a4, 502}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+8b )
BUGCHECK_STR:  0x1a_8884
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun 20 08:44:59.346 2014 (UTC + 6:00)
System Uptime: 0 days 4:15:11.406
BugCheck A, {3420000, 2, 0, 830c63b7}
*** WARNING: Unable to verify timestamp for tdrpm251.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys
Probably caused by : tdrpm251.sys ( tdrpm251+9fce )
BUGCHECK_STR:  0xA
PROCESS_NAME:  JDownloader2.e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Debug session time: Fri Jun 20 04:28:24.030 2014 (UTC + 6:00)
System Uptime: 0 days 15:22:15.090
BugCheck A, {c1270628, 2, 1, 830b51ca}
*** WARNING: Unable to verify timestamp for avgmfx86.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx86.sys
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ed )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Debug session time: Thu Jun 19 13:01:43.952 2014 (UTC + 6:00)
System Uptime: 0 days 0:34:15.622
BugCheck 1000008E, {c0000005, 83290fd4, 8abba6f4, 0}
*** WARNING: Unable to verify timestamp for tdrpm251.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys
Probably caused by : tdrpm251.sys ( tdrpm251+2b5cf )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

Remove AVG it's contributing to your BSOD;s.

Recommended antivirus software for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials Download | Free Spyware Protection
• Malwarebytes - The Free version
• Good & Free System Security

   Warning

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Daemon Tools/Alchohol is known to cause Blue Screens. Please remove it:

• How to remove sptd.sys from system
• Registry and SPTD problems

Scan with Kaspersky TDSSKiller:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• How to Repair Windows 7 System Files with System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

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

giveio.sys Thu Apr 4 08:33:25 1996 (316334F5)
ADC Analyzer/SwiftForth/Disspy - ?SpeedFan?
Driver Reference Table - giveio.sys

ASACPI.sys Fri Aug 13 08:52:52 2004 (411C2D04)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

VSTCNXT3.SYS Thu Oct 16 06:29:13 2008 (48F68AD9)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTCNXT3.SYS

VSTBS23.SYS Thu Oct 16 06:30:15 2008 (48F68B17)
Conexant HSF_HWB2 WDM driver
Driver Reference Table - VSTBS23.SYS

VSTDPV3.SYS Thu Oct 16 06:32:04 2008 (48F68B84)
Conexant SoftK56 Modem Driver
Driver Reference Table - VSTDPV3.SYS

AODDriver2.sys Tue Mar 6 14:39:27 2012 (4F55CD3F)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
Driver Reference Table - AODDriver2.sys

sptd.sys Thu Oct 31 21:26:24 2013 (527276A0)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
Driver Reference Table - sptd.sys

hssdrv6.sys Tue Mar 25 02:07:50 2014 (53309096)
Hotspot Shield Routing Driver [br] Possible BSOD cause seen in mid-2012
Driver Reference Table - hssdrv6.sys

To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Check for heating issues using Speccy or HWmonitor

Upload a screen shot:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

• RAM - Test with Memtest86+

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.

 

[archimonde]

Thnx for all of these, I'll try to follow it to the T! One question though: I've opened the case to see what's happening in there and noticed the following - sometimes the gpu fan stops spinning for a second and then resumes spinning and the system reports that the catalyst drivers (version 13.9) have stopped working and then recovered. It leads to various kinds of problems - chrome browser or just flash in chrome crashing, crashing a game etc. It reports memory issues (memory being 0MB), atidxx32.dll file problems, video driver problems such as e.g. Rendering thread exception: Fatal error! etc. So, should I proceed with the above, does this help pinpoint the problem a bit?

 

[Britton30]

It sounds as if you GPU is bad/shot/defective. The fan may be dirty too making it run intermittently.

Try using Revo to uninstall all GPU drivers, reboot and let Windows Update reinstall them.

 

[archimonde]

I've just wanted to post that I've found the culprit for the BSODs thanks to you guys & gals and to a chance discovery. I had a appcrash error similar to this:

Problem signature:
Problem Event Name: APPCRASH
Application Name: WINWORD.EXE
Application Version: 12.0.4518.1014
Application Timestamp: 45428028
Fault Module Name: WINWORD.EXE
Fault Module Version: 12.0.4518.1014
Fault Module Timestamp: 45428028
Exception Code: c0000005
Exception Offset: 000010eb
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

and I used additional information 1 & 2 to check it on the net if someone had a similar problem.It turned out that it's a mobo or ram problem in most cases so I decided to run memtest86 as you suggested. I double-checked the results from it and the errors kept repeating leading to the conclusion it was one of my ram modules. So, it was a faulty ram module.