Yet Another Unexpected Shutdown Problem

I'm new to posting, but have been reading the forum ever since I bought my new computer and upgraded 7 Started Edition (horrible) to 7 Professional. I love this place and have learned a lot from it.

I have noticed other people are getting this "Windows Recovered From An Unexpected Shutdown" problem. I just started getting them about a week ago and it's driving me insane.

Mine are weird, though. It only happens when my computer is idle. I'll either lock it and step away for a few, or let it sit un-locked for a while, and when I return, it's at the Log-in screen. When I log in, that wonderful error message greets me. Once, my computer was reverted back to the state it was in when I first upgraded to Professional. All my programs and applications were gone! Everything was gone! I had to do a system restore to get it all back.

Now, I know the upgrade to Pro isn't what's causing this because I had a friend who is a professional with this stuff do it for me, and this was about 3 weeks ago, while the errors started about a week ago.

Here are the details of my error message....

(the ******* at the bottom of the message in the user folder address is where my name was, removed for security (read: paranoid) reasons)

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 81B9D000
BCP2: 00000002
BCP3: 00000000
BCP4: 8460450F
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020910-31824-01.dmp
C:\Users\*******\AppData\Local\Temp\WER-874338-0.sysdata.xml

If anyone has ANY suggestion at all, I would appreciate it so much if you'd share it with me. This is driving me absolutely crazy!

Thanks in advance.

Did you run the minidump? If not do so. If you need help doing that, post the minidump here, so that someone can run it for you.

richc46 said:

You indicated that you know that this was not caused by the upgrade. I pose this question. Did you have to reinstall all of your programs, after the install? If no, you had an upgrade and not a clean install. Almost everyone here agrees an upgrade will not be satisfactory over the long run.

Post back, if you had an upgrade, advise and we will help you with the clean install.

If you did have a clean install we will investigate further.

What you are having is knows as the BSOD. If you had a clean install, you can follow the instructions that I will give you, to help us with the necessaryinformation.

It was a clean install. The friend of mine who installed it does this kind of stuff for a living and made sure it was installed absolutely right. Like I said, I had no problems with my PC for the two weeks after upgrading to Pro. This problem only presented itself in the 3rd week.

Shall I go ahead and follow the instructions in the link you referred me to? I will go ahead and do that for now and link you to the new thread.

seekermeister said:

Did you run the minidump? If not do so. If you need help doing that, post the minidump here, so that someone can run it for you.

I have no idea what a minidump is or how to run it. Could you please tell me about it?

^ I did.

Here's the link to my thread with the minidump file. I believe the files from all the instances of this happening are in the .rar file, but the 020910-31824-01.dmp file is, as you can tell, the most recent.

My computer is in your hands, good sir.

sixpartseven;559881

[QUOTE=seekermeister;559861 said:

Did you run the minidump? If not do so. If you need help doing that, post the minidump here, so that someone can run it for you.

I have no idea what a minidump is or how to run it. Could you please tell me about it?[/QUOTE]
Attach the file dated as shown in the error message above from \Windows\Minidump folder.

When I said to post the dumps, I didn't mean in a second thread, but I just ran the latest 3 dumps, but they are all the same and point to the ataport.sys. From what I scanned over here:

ATA Port Driver

This appears to be a driver installed by the OS, and though it encourages us to use it, I would install the manufacturer's chipset driver for the motherboard. Sometimes this must be done from Safe Mode, or Windows will balk.

I would suggest deleting the other thread. You can attach the dumps to any post that you have already made using the advanced editing feature, so that anyone can run them for confirmation.