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: Very difficult to diagnose BSODs at random intervals.


19 Apr 2012   #1

Windows 7 Home Premium x64
 
 
Very difficult to diagnose BSODs at random intervals.

Hi all,

I would really appreciate some analysis on some dump files. I've had a computer running rock solid for about 18mths. I've just used ~70% of it's parts to build a new computer for my dad and since then he's been experiencing constant BSODs.

The computer is running a freshly installed over-the-counter bought OEM copy of Windows 7 Home Premium x64 which is up to date as of last week. It will run fine for an unpredictable length of time between 15mins to half a day then BSOD. Sometimes it will then get stuck into a "crash-reboot" cycle and he will have to hard power it off.

The computer is less 18mths old. The parts I have been using confidently over the last 18mths are as follows:

- MOBO: Gigabyte P55-UD4
- CPU: Intel i5 750 quad core (never overclocked).
- RAM: 2x(DDR3 2GB G.Skill 1333mhz)

The new components we installed are:

- GFX: Asus ATI HD5550
- HDD Sata 200GB Baracuda
- CD Drive: LG DVD writer on an IDE ribbon
- PSU: Antec VP450P 450w

I initially had an old install of Windows 7 on a 120GB Sata drive but when he started getting issues I installed a brand new OEM Windows 7 on the Sata 200GB and even changed the Sata cable. It ran fine for a day then started up again.

From what I could see none of the crashes pointed toward gfx drivers - however I've noticed CPUz will only tell me that it's a HD5500 series card and gives me no other info so maybe it isn't being recognised properly . The only other thing to change was the PSU - which admitedly is a budget one (but from reviews should be reasonable) from deduction it's the only thing I can put it down to.

I would REALLY appreciate if someone could take the time to look at the dumps and see if they mean anything to them because at the moment I'm now at a loss. Thanks.

My System SpecsSystem Spec
.

19 Apr 2012   #2

Win 8 Release candidate 8400
 
 


These crashes were caused by memory corruption/exception (Cx05) 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!!!

* If you have a Raid update its Driver.




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-7 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+






Driver Verifer

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

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JGriff2 & Usasma.
Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
19 Apr 2012   #3

Windows 7 Home Premium x64
 
 

Wow, thanks so much for the quick reply. I've just left my dad's but will get back to you when I have another look at it.

So just for clarity from what you've seen it's either going to be a bad stick of memory/ram port or a driver issue?

That narrows it down a lot, thanks. At least now I can stop worrying about it being the PSU.
My System SpecsSystem Spec
.


19 Apr 2012   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by NameChange View Post
Wow, thanks so much for the quick reply. I've just left my dad's but will get back to you when I have another look at it.

So just for clarity from what you've seen it's either going to be a bad stick of memory/ram port or a driver issue?

That narrows it down a lot, thanks. At least now I can stop worrying about it being the PSU.

Probably. And my money is on a driver.
My System SpecsSystem Spec
Reply

 Very difficult to diagnose BSODs at random intervals.




Thread Tools



Similar help and support threads for2: Very difficult to diagnose BSODs at random intervals.
Thread Forum
Solved Multiple BSODs (Occurs at start-up or random intervals) unknown errors BSOD Help and Support
Random BSODs at odd intervals BSOD Help and Support
Solved BSoDs on random intervals BSOD Help and Support
Intermittent BSOD, trouble resuming Windows, Difficult to Diagnose BSOD Help and Support
Drives keep disappearing and constant BSoDs (difficult) Hardware & Devices
BSODs and Restarts at random intervals BSOD Help and Support
Diagnose Random Crash 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 06:55 AM.
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