Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Recent spate of BSoDs with various error codes after 2 clean years


30 Nov 2011   #1

Windows 7 Home Premium 64bit
 
 
Recent spate of BSoDs with various error codes after 2 clean years

Hi folks. Until recently, I had gone approximately two years without an unexplained BSOD while using the computer in question heavily. I've now gotten 6 in the last few weeks, displaying a number of different bugcheck codes. A quick timeline:

11/30/11 - BSOD, bugcheck code 0x1000007e
11/21/11 - BSOD, bugcheck code 0x00000050
11/11/11 - BSOD, bugcheck code 0x0000003b
11/08/11 - BSOD, bugcheck code 0x0000001e
11/07/11 - BSOD x2, bugcheck codes 0x0000001e and 0x0000003b
10/02/11 - BSOD, bugcheck code 0x0000001e - First recent, unexplained BSOD
7/19/11 - BSOD, bugcheck code 0x0000003b - Occured very shortly after installing new RAM, discovered that BIOS settings had defaulted to wrong values and corrected.
10/29/09 - BSOD, bugcheck code 0x0000001e - This was my last BSOD before the ones detailed above. I have no recollection of the cause, but I was pretty pleased with the 2 year gap.

Other potentially relevant information:
As I mentioned, I added RAM in July of this year, going from 2 to 4 sticks of 2gb DDR3 running at 1333.

I had been running somewhat outdated ATI video drivers (May 2011, iirc) until I updated after the 11/11 BSOD looking for a fix. Other than that, the only software change I can think of is installing BlueScreenView, which obviously happened after the issues started.

Scans with Microsoft Security Essentials and Malwarebytes Anti-Malware have come back clean.

Memtest has been left to run overnight repeatedly, completing at least a half dozen passes without finding any errors.

I don't recall precisely what was going on at the time of each BSOD, but at least 2 of the recent ones have occured while watching Netflix streaming video, and 2 more have occured while playing games (Defense Grid and Sanctum, if it matters).

System info:
Windows 7 Home Premium x64
Shipped with Vista Home x64 in July of '09, completed "fresh install" upgrade to Windows 7 sometime around October of '09
Processor: Phenom II x3 720
Video card: HIS Radeon HD 4850
Memory: 4x2GB DDR3 1333

Attached ZIP file contains the diagnostics requested in the sticky at the top of this forum. Thanks for your time reading this and any guidance will be very much appreciated!

My System SpecsSystem Spec
.

30 Nov 2011   #2

Win 8 Release candidate 8400
 
 

Many different causes and when this is the case it is usually hardware. The first thing I would check would be RAM but since yours appears to have passed I would move on to a driver.

Quote:
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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.
My System SpecsSystem Spec
03 Dec 2011   #3

Windows 7 Home Premium 64bit
 
 

Thanks for replying, zigzag.

I did as you suggested. It's been about 40 hours since I activated the verifier without any BSODs. Should I shut it off now or let it keep going? My last 3 blue screens have come about 10 days apart, so I wonder how large a sample is needed.

Your warnings to back everything up reminded me of one other possibly meaningful change that I forgot about. In an effort to be more diligent about backups, sometime around mid-September (a couple weeks before the first BSOD) I installed SyncToys and mapped a shared drive on another computer on my network to sync to. That computer is off 99% of the time, and only really gets turned on when I'm updating my backups. My amateur research suggests that several of those error codes can be the result of a lack of available disk space. There's plenty of space on my primary hard drive, but is it possible something's trying to write to the unavailable drive on the network for some reason and then causing a freak out when it can't do so? Or is this likely to be completely unrelated?
My System SpecsSystem Spec
.


04 Dec 2011   #4

Windows 7 Home Premium 64bit
 
 

Another crash-free 24 hours with the verifier running. Ironic that I come here to complain because I'm getting BSODs and now I can't get one when I'm looking for it!

Any suggestions on where to look now? Barring instructions to the contrary I'll discontinue the verifier tonight, as I'd rather not continue to leave the computer running overnight.
My System SpecsSystem Spec
04 Dec 2011   #5

Windows 7 Home Premium 64 Bit
 
 

Just continue running as normal and post back when you get another BSOD. I would think verifier is not going to cause the problem, so maybe it is just the network syncing you mentioned. If you continue to get one once a week, try running without the sync program for a couple weeks and see if it repeats itself. You can always backup your computer using the usual external drive usb connection.

Edit: Another thing to check is:
1. Click Start Menu
2. Type eventvwr into Search programs and files and press enter
3. Go to Windows Logs, Application
4. Look for any Errors that occurred around the time of your last BSOD.
My System SpecsSystem Spec
Reply

 Recent spate of BSoDs with various error codes after 2 clean years




Thread Tools



Similar help and support threads for2: Recent spate of BSoDs with various error codes after 2 clean years
Thread Forum
BSODs with different error codes, all of them include ntoskrnl.exe BSOD Help and Support
Seemingly random BSODs. Not sure of error codes. BSOD Help and Support
Frequent BSODs on a number of different error codes BSOD Help and Support
Random BSODs, various error codes BSOD Help and Support
Unpredictable BSODs Various error codes New Build BSOD Help and Support
Numerous BSODs with various error codes BSOD Help and Support
Microsoft apologizes for spate of recent Online Services outages News

Our Sites

Site Links

About Us

Find 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 11:45 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33