Windows 7 Crashes - Solution?

[VladtheImpaler]

Hope some of the technologically enlightened can help me with a solution to this issue. My new laptop with Windows 7 seems to crash every few hours and when that "Windows has recovered from an unexpected shutdown" pop-up appears upon the re-booting, it says:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: d1
BCP1: FFFFF8800647787C
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880026F9767
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021811-23805-01.dmp
C:\Users\Vladimir\AppData\Local\Temp\WER-46800-0.sysdata.xml

[Serapth]

That info really doesn't help trouble shoot the problem.

That said, I give you a 99.999% chance that your problem is one of two things.

1- a bad driver
2- bad hardware
3- a virus

The fact its a brand new machine makes 2) a very likely thing.


First off, boot into Safe Mode and see if the problems continue, if they don't its probably a driver issue. To boot into safe mode, hit F8 when prompted on loading your computer. If it boots fine, let it run for a while and see what happens.



Another question, did the problem just start? Did the computer ever work, or did it stop working? Do you have anti-virus running?

[ricosuave]

Can you get into safe mode (or regular mode) and check event viewer to see if anything is out of the ordinary?

Also, even if it is brand new, I'd check the seating of the ram chips and the hard drive connectors.

I havent heard of many blue screens under Win 7. What do you get when you google the model number of it and blue screen?

[VladtheImpaler]

Originally Posted by Serapth

That info really doesn't help trouble shoot the problem.

That said, I give you a 99.999% chance that your problem is one of two things.

1- a bad driver
2- bad hardware
3- a virus

The fact its a brand new machine makes 2) a very likely thing.


First off, boot into Safe Mode and see if the problems continue, if they don't its probably a driver issue. To boot into safe mode, hit F8 when prompted on loading your computer. If it boots fine, let it run for a while and see what happens.



Another question, did the problem just start? Did the computer ever work, or did it stop working? Do you have anti-virus running?

It started about 3 days ago, and, yes, I have anti-virus running. The computer worked just fine for the previous 6 weeks.
I will try booting in safe mode.

[cKy]

Little help to you now, but on Tuesday SP1 comes out for Windows 7. That may help the problem, or knowing MS make it 10x worse.

[Serapth]

Before you do too much, restore the "Last Known good" profile. This might undo whatever might have botched your computer.

[sclitheroe]

This is a good link explaining how to use windbg to figure out which driver is causing the bluescreen: http://www.adopenstatic.com/cs/blogs...0_-Part-2.aspx

I used windbg to determine Trend Officescan was causing bluescreens on a laptop just this week.

[TylerSVT]

System 32?

[dissentowner]

Solution? Get a Mac.

[sclitheroe]

Mac's have panic attacks too:

[dissentowner]

Originally Posted by sclitheroe

Mac's have panic attacks too:

I have never encountered this screen before in 7 years of Mac use.

[Serapth]

Originally Posted by dissentowner

I have never encountered this screen before in 7 years of Mac use.

You are seriously full of luck! My iMac has shown me that screen more times that I would like to recall. Its a vast improvement over OS9, which was a festering pile of..... but its not the second coming that many people make it out to be.

[dissentowner]

Originally Posted by Serapth

You are seriously full of luck! My iMac has shown me that screen more times that I would like to recall. Its a vast improvement over OS9, which was a festering pile of..... but its not the second coming that many people make it out to be.

Really? Guess I have been lucky.

[llama64]

Originally Posted by dissentowner

Solution? Get a Mac.

And people wonder why Mac user's are hated.

I was totally gonna post the same thing...

To the OP - that is likely caused by a mis-behaiving device driver as Serapth mentioned.

Try opening the XML file referenced in a text editor like notepad (not IE which is default I think). There might be a reference to what device/driver is causing this.

The other possibility is defective RAM - used to see this whenever the system tried to use a corrupted area of one RAM stick. But for me it was a total system failure the moment it happened - almost like I had hit the reset button.