Solved Two BSOD's in 2 weeks

*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.

Click to expand...

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/Win7 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.

Click to expand...

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