Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Problem Event: BlueScreen

Aug 31, 2010 8:19PM PDT

My laptop keeps crashing every time I turn it on. This is the message I get in Safe Mode:

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

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

Files that help describe the problem:
C:\Windows\Minidump\090110-18423-01.dmp
C:\Users\Ross\AppData\Local\Temp\WER-35739-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


It will also crash if I choose Safe Mode with Networking, so I can't get online from my laptop.

Help would be appreciated!!!

Discussion is locked

- Collapse -
Details
Aug 31, 2010 9:15PM PDT

Sony Vaio, VGN-20EF, Windows 7

- Collapse -
The Story
Sep 1, 2010 2:26AM PDT

The bluescreen of death happened this morning for the first time. It happened after I'd turned on the laptop at the password screen and continued doing this each time I tried to start Windows normally. At first I was able to open using Safe Mode - then this stopped working. F8 gave me the option to go back to a time when the computer was last running normally - sorry, can't remember the exact name of the option - and this worked. I guess the problem's solved, but I'd like to know what caused it in case it happens again. I'll be spending this evening backing up everything!

- Collapse -
Causes.
Sep 1, 2010 4:03AM PDT

Range from malware to an incompatible item to some update that failed.

Microsoft does not provide great forensics for this and unless you have a software detective to hire and start the work the causes are usually unknown.

Look at your posting. The clues are not here. For example if you wrote you run RegMax cleaner or such then you would have moderators write "don't use that."

Sorry that it's that way.
Bob