Got first Blue Screen of Death

[Shephard]

I just got my first blue screen of death on my new computer. I haven't had one of these since Windows XP.

All I was doing was formatting a hard drive. no games, no overclock.

these are the errors.

Problem Event Name: BlueScreen

BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002C96280
BCP3: FFFFF880031DFDC8
BCP4: FFFFF880031DF620

 

[WaitingForNehalem]

Run memtest86+ over night, see if you get any errors.

 

[Shephard]

nooooo don't tell me it's the golden samsung ram. I will be very mad if it is.

can I run the sticks together? I have 8gb, but they didn't come as a pair. 1x4 and 1x4.

 

[Vectronic]

Check your event viewer, might be more informative (and a lot easier than diging through log files and memory dumps).

Doubt it's a memory issue, most likely a driver issue related to the HD you just put in... (it probably bluescreened right as it finished formatting. drive was unmounted for formatting, then mounted again, Windows looked for drivers... crash).

 

[Shephard]

what exactly am I looking for in the event viewer?

There are 9 errors and 1 critical for today.

 

[Vectronic]

Whichever seems relevant of those 9, and around the time of the crash.

 

[Shephard]

from newest to oldest

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002c96280, 0xfffff880031dfdc8, 0xfffff880031df620). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 020213-4664-01.

Session "Microsoft-Windows-Setup" stopped due to the following error: 0xC000000D

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The previous system shutdown at 4:40:06 PM on ‎2/‎2/‎2013 was unexpected.

The shadow copies of volume F: were aborted because volume F:, which contains shadow copy storage for this shadow copy, was force dismounted.

Session "Microsoft-Windows-Setup" stopped due to the following error: 0xC000000D


Those errors are between 4:20-4:40pm. Any errors before that were this afternoon just when I had the computer on.

The name "xxx-PC :20" could not be registered on the interface with IP address xxxxxx. The computer with the IP address xxxxxx did not allow the name to be claimed by this computer

 

[Vectronic]

None of those are specifically related to the crash, however it seems I was right that it happened when the new hard drive was re-mounted.

Seems your PC was trying to make a back-up (or register for back-ups, "System Volume Information" etc) the new drive for back-ups, got dismounted when you formatted, when it remounted again... s**t + fan.

Not entirely sure about the resolution, could have been a one time hiccup, could be more persistent.

You might want to look into those "Microsoft-Windows-Setup" errors though, they can be meaningless, but it could be something important.

 

[Shephard]

when googling 0XC000000D it comes up with Microsoft Security Essentials? I don't have that.

 

[Vectronic]

I meant expand the error in Event Viewer and look at the details.

0xC000000D *should* mean invalid parameter, however... it's the invalid parameter to *what* that matters.

It's possible that Windows detected the E: drive (and it's boot configuration) and was trying to figure out WTF was going on because now the PC is claiming to have 2 primary partitions, 2 boot configs, etc.

That shouldn't have made it crash though, but there are quite a few things that are unknown.

 

[Shephard]

SessionName Microsoft-Windows-Setup

FileName C:\Windows\Panther\setup.etl

ErrorCode 3221225485

LoggingMode 5

 

[Vectronic]

Yeah, deleting that file/folder seems to be the "cure", though not for everyone.

(was doing other stuff, hence delay)

 

[Shephard]

ok is running memtest worth doing? for how long for 2 sticks?

 

[theevilsharpie]

Problem Event Name: BlueScreen

BCCode: 1000007e [This means that something unexpected went wrong with system-level code that Windows was running in a way that Windows couldn't handle]
BCP1: FFFFFFFFC0000005 [This means that Windows crashed because it expected some data to be in memory at a certain spot, but it wasn't there]
BCP2: FFFFF80002C96280
BCP3: FFFFF880031DFDC8
BCP4: FFFFF880031DF620

See in-line comments. This is almost certainly malfunctioning RAM.

 

[Shephard]

if that's true I will be mad. I passed on many good ram deals just for the Samsung golden to come back in stock. Finally it did, I order, and now it's out of stock again.

please guide me to the proper way to run memtest. I have not done it in years.

1 stick at a time or is 2 ok. 4 hours or 12 hours?

 

[red454]

Use this for more details on the blue screen. It gives details on the crash dump and can help narrow down the source (hardware, drivers, etc.)

http://www.resplendence.com/whocrashed

 

[Ferzerp]

Errr, didn't this guy have a "how to overclock" thread a few days ago?

And no one goes there when he sees instability?

 

[Shephard]

Errr, didn't this guy have a "how to overclock" thread a few days ago?

And no one goes there when he sees instability?

I didn't touch the ram.

Memtest results.

I ran newest version on USB stick. All settings default.

Run time - 13 hours 25 minutes 53 seconds.
Cached 8079M
RsvdMem 2828K
MemMap e820
Cache On
ECC off
Test Std
Pass 12
Errors 0

Pass Complete, no errors.

Think that's good enough to assume it's not ram?

 

[rgallant]

RELOAD WINDOWS
looks like after a quick look at this thread your P4 set up has issues
-like you moved the system restore to a drive then reformatted it.
-really list you system spec's and os

 

[Shephard]

I fresh installed Windows to an SSD my first. I didn't clone or move anything.

all I did last night was reformat my 1tb hd which had Windows on it in another computer.

3570k
msi gd55
samsung golden 8gb

 

[ShintaiDK]

Overclocked?

 

[Shephard]

Overclocked?

no I am at stock settings right now. I only tried overclocking that one night.

 

[Shephard]

anyone else know the problem since ram seems ok.

 

[Vectronic]

Has it done it since?... It might have just been a one time thing... driver error, BSOD forced a reboot, problem solved itself.

 

[Shephard]

Has it done it since?... It might have just been a one time thing... driver error, BSOD forced a reboot, problem solved itself.

no but I am worked up now that people said it could be ram problems.

Did I run the memtest right?

I couldn't of hurt the ram if I just OC cpu.

I think the memory controller is ok because I was borrowing ram until I got mine.