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: BSOD, Startup Repair, System Repair and other errors on nearlly new PC


21 Feb 2012   #1

Windows 7 Home Premium 64bit
 
 
BSOD, Startup Repair, System Repair and other errors on nearlly new PC

I took delivery of a new (and expensive!) PC in January but last week it started giving me constant and varied errors.

The isssues range from Blue screen, black screen, failing to load windows, startup repair needed often, system restore needed often, and when it does load windows there are various error messages.


System info:
Intel Core i5 2500K
Win 7 Home Premium 64bit

Original OS installed on the system, an OEM version
PC just a few weeks old

Any help and guidance is much appreciated...


My System SpecsSystem Spec
.

21 Feb 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

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



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.

So, 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.


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.
Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
22 Feb 2012   #3

Windows 7 Home Premium 64bit
 
 

Many thanks for your response.

I'm running Memtest86+ now. But after only a few minutes it's already showing 25000+ errors.

I've read the Memtest86+ tutorial you linked and the next stage involves open up the PC.

But as this is a brand new PC with a 2 year warranty, I think the best thing to do is contact the manufacturer?

Or is there still a chance that it is a software issue?
My System SpecsSystem Spec
.


22 Feb 2012   #4
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Quote:
But as this is a brand new PC with a 2 year warranty, I think the best thing to do is contact the manufacturer?

A new computer should not be presenting with the problems you have listed - & we volunteers should not be putting at risk the rights,YOU, the consumer has under that warranty...
Be aware that attempting any subsequent hardware troubleshooting steps may, in some cases, void your warranty.

I strongly suggest that you should seek further advice asap.
Under Warranty terms a duty of care applies.
My System SpecsSystem Spec
22 Feb 2012   #5

Win 8 Release candidate 8400
 
 

I agree completely with JMH. That many errors in memtest show there is a memory issue that is best resolved by the mfr.
My System SpecsSystem Spec
24 Feb 2012   #6

Windows 7 Home Premium 64bit
 
 

So I contacted the PC manufacturer...

They asked me to isolate which ram stick is bad by taking one stick out and running the PC, and then swapping.

So I removed one stick and the PC loaded and restarted fine with no errors, bsod or glitches. I ran memtest86+ for 40 mins and it showed no errors.

I then swapped the sticks. The pc loaded totally fine. I ran memtest8+ and it indeed showed thousands of errors within a few minutes.

This makes sense to me, one bad stick, one good stick.

The only thing that is confusing me is that even with just the (supposed) bad stick in, the pc is running fine and not giving me the endless error messages it was previously.

I've even put both sticks back in and it is running fine now. (but still gives errors under memtest86).

Previously, I would always get either a bsod, frozen black screen, startup repair, system restore issue when starting up or restaring the system.

But now its fine?
My System SpecsSystem Spec
24 Feb 2012   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mistermix View Post
So I contacted the PC manufacturer...

They asked me to isolate which ram stick is bad by taking one stick out and running the PC, and then swapping.

So I removed one stick and the PC loaded and restarted fine with no errors, bsod or glitches. I ran memtest86+ for 40 mins and it showed no errors.

I then swapped the sticks. The pc loaded totally fine. I ran memtest8+ and it indeed showed thousands of errors within a few minutes.

This makes sense to me, one bad stick, one good stick.

The only thing that is confusing me is that even with just the (supposed) bad stick in, the pc is running fine and not giving me the endless error messages it was previously.

I've even put both sticks back in and it is running fine now. (but still gives errors under memtest86).

Previously, I would always get either a bsod, frozen black screen, startup repair, system restore issue when starting up or restaring the system.

But now its fine?
Take the known good stick and put it in each mobo slot retest.
My System SpecsSystem Spec
24 Feb 2012   #8

Windows 7 Home Premium 64bit
 
 

I tested each stick, in each of the 2 slots. The bad stick is bad in both slots and the good stick is good in both slots.

(good and bad according to memtest86)

There are 4 slots in total on the motherboard; but I've only used the 2 slots that had sticks in.

Is errors in memtest86 a valid enough reason to return a memory stick? Even if the system is running fine?

Or should I expect the errors to return once I've used the system more...
My System SpecsSystem Spec
24 Feb 2012   #9

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mistermix View Post
I tested each stick, in each of the 2 slots. The bad stick is bad in both slots and the good stick is good in both slots.

(good and bad according to memtest86)

There are 4 slots in total on the motherboard; but I've only used the 2 slots that had sticks in.

Is errors in memtest86 a valid enough reason to return a memory stick? Even if the system is running fine?

Or should I expect the errors to return once I've used the system more...
If the mobo tests did what you expected them to it is the RAM. Memtest is enough to RMA the ram especially if you send them a copy of the Memtest report.

It is almost universally accepted


I pointed you back here on Microsoft Answers.


My System SpecsSystem Spec
24 Feb 2012   #10

Windows 7 Home Premium 64bit
 
 

So the old problems havent returned yet. But just noticed some flickering/flaring on the screen. See attached pic.

Could this still be the same ram fault or does it mean it could also me motherboard/graphics card related?
My System SpecsSystem Spec
Reply

 BSOD, Startup Repair, System Repair and other errors on nearlly new PC




Thread Tools




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