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: Two BSOD's in 2 weeks


10 Jan 2012   #1

Windows 7 Pro 64bit
 
 
Two BSOD's in 2 weeks

Hi ,

I wasn't doing anything in particular during the crash. My first crash was on Jan 4 and earlier today (i.e-Jan 10) was the second time. The only new installation I can think of was an upgrade to Firefox 9.0.1 and Skype facebook Beta.

Systems info

Current: Windows 7 Pro x64 full retail
Hardware age: 2 years
OS age : ~ 2 yrs
Original OS : Windows 7 Home

Please find attached the dump files

My System SpecsSystem Spec
.

10 Jan 2012   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by athlone View Post
Hi ,

I wasn't doing anything in particular during the crash. My first crash was on Jan 4 and earlier today (i.e-Jan 10) was the second time. The only new installation I can think of was an upgrade to Firefox 9.0.1 and Skype facebook Beta.

Systems info

Current: Windows 7 Pro x64 full retail
Hardware age: 2 years
OS age : ~ 2 yrs
Original OS : Windows 7 Home

Please find attached the dump files
Memory management. The fact that your uptime was 6+ days doesnt help.


I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
http://us.norton.com/support/kb/web_...v_type=public_
web&docurl=20080710133834EN

http://www.microsoft.com/security_essentials/

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!



1-Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
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.

I'd suggest that you first backup your data 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.
Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users



Old drivers needing updating
Code:
PCD5SRVC_x64.pkms    7/21/2008 3:12:55 PM    fffff880`054c3000    fffff880`054cf000        0x0000c000    0x4884edc7                        
purendis.sys    10/27/2008 11:31:28 PM    fffff880`02139000    fffff880`02145000        0x0000c000    0x490695a0                        
pnarp.sys    10/28/2008 12:57:00 AM    fffff880`0212d000    fffff880`02139000        0x0000c000    0x4906a9ac                        
dne64x.sys    11/10/2008 8:01:24 PM    fffff880`04553000    fffff880`0457f000        0x0002c000    0x4918d964                        
netw5v64.sys    3/26/2009 11:21:24 AM    fffff880`05637000    fffff880`05b72000        0x0053b000    0x49cbab84                        
k57nd60a.sys    4/26/2009 6:23:05 AM    fffff880`05b72000    fffff880`05bba000        0x00048000    0x49f44419                        
GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`04512000    fffff880`0451f000        0x0000d000    0x4a1151c0                        
CtClsFlt.sys    6/15/2009 12:06:41 AM    fffff880`05400000    fffff880`0542a2a0        0x0002a2a0    0x4a35d6e1                        
rimspx64.sys    6/25/2009 2:13:43 AM    fffff880`04056000    fffff880`0406d000        0x00017000    0x4a4323a7                        
rixdpx64.sys    6/25/2009 2:38:50 AM    fffff880`03fa0000    fffff880`03ff7000        0x00057000    0x4a43298a                        
rimmpx64.sys    6/25/2009 3:04:18 AM    fffff880`05620000    fffff880`05636000        0x00016000    0x4a432f82                        
IntcHdmi.sys    7/10/2009 8:45:10 AM    fffff880`05265000    fffff880`0528c000        0x00027000    0x4a5745e6
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

My System SpecsSystem Spec
10 Jan 2012   #3

Windows 7 Pro 64bit
 
 

Thanks will work on them.
My System SpecsSystem Spec
.


Reply

 Two BSOD's in 2 weeks




Thread Tools



Similar help and support threads for2: Two BSOD's in 2 weeks
Thread Forum
BSOD every few weeks, want to know cause of problem BSOD Help and Support
Solved New Lenovo - BSOD, Warrantee Replaced Motherboard, New BSOD 3 weeks BSOD Help and Support
Solved Three BSOD in the Last Three Weeks BSOD Help and Support
BSOD for the last 2 weeks BSOD Help and Support
BSOD every couple weeks! BSOD Help and Support
BSOD after a weeks rest BSOD Help and Support
6 BSoD's in 2 weeks BSOD Help and Support

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 08:39 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