Clean Install Problems

[MaDDN3ss]

Clean Install Problems --- SOLVED!!

Hi,

I'm hoping someone here has an answer for me. I've probed through the forums but I can't locate a similar problem.

Here is my problem. I'm trying to install the latest Windows 7 RC 64-bit downloaded from MS but keep getting a BSOD. This is a clean install. All drives have been partitioned, wiped clean, formatted etc.. several times now, LOL.
I have tried in RAID, not in RAID, and with only 1 HDD installed.

I boot to the DVD, Windows installs the 100mb temporary files and starts. Just when it switches to the light blue screen with the dove on it I get a BSOD with the following message:

A problem has been detected....

Disable or remove any newly installed hardware and drivers. Disable or remove any newly installed software. If you need to use Safe mode to remove or disable compnents, restart your computer- Press F8 to select advanced startup options, and then select safe mode.

Technical information:

*** STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF8000CEL265B)


Current system:
eVGA 790i Ultra SLI mobo
Intel E6300
Patriot Viper PC3-12800 (2x 2GB)
XFX 8500GT
2x WD800 74 GB Raptor SATA HDD
2x Seagate 500GB HDD
LG DVDRW

 

[Night Hawk]

Welcome to the Se7enforums! MaDDN3ss

The MS information for that particular type of error is quite specific when pointing to a hardware possible and likely or software problem of some type. The "STOP: 0x0000007F" part is seen as far back as Windows 2000 due to having an NT core.

"This error message can occur if either of the following conditions exists:

• Your computer has hardware or software problems (hardware failure is the most common cause).
• You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).

The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:

• Low-level hardware corruption, such as corrupt memory (RAM)
• Mismatched memory modules
• A malfunctioning motherboard

To determine an approximate cause, examine the parameters at the top of the STOP screen:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP
The most important parameter is the first one (0x0000000X) which may have several different values. The cause of this trap can vary, depending on the value of this parameter. All traps that cause a STOP 0x7F can be found in any Intel x86 microprocessor reference manual as they are specific to the x86 platform. Here are some of the most common ones:"
General causes of "STOP 0x0000007F" errors

How you are trying to install 7 by dvd? You may have seen a bad burn to disk as possible cause if everything on the system is in prime condition and there are no memory faults or other hardware problems being seen.

 

[MaDDN3ss]

Thanks for the response.

I know that it's not a bad disk as I have installed Win7 on a previous system with that disk.

Both the RAM and mobo are brand new so that shouldn't be the problem but not ruling it out. I will be pulling one module out this evening to see if that does anything.

 

[zigzag3143]

madn3ss

Are you running a raid?

ken

 

[TGSoldier]

Both the RAM and mobo are brand new so that shouldn't be the problem but not ruling it out.

You're right. Don't rule it out. Just because equipment is new, does not mean it is 100% functional.

 

[BishopLord]

I don't know why, but something about this: Patriot Viper PC3-12800 (2x 2GB) : grabbed my attention as the culprit. I understand that the EVGA SLi board you bought is capable of using DDR3 memory, but something about this memory stick bothers me, especially when pairing it with the E6300.

 

[Night Hawk]

You might to run memtest for a good stretch first to see any large number of errors are seen. That won't always show bad memory when a good number of errors are seen. But it will show if something is ? having a problem.

 

[jimbo45]

Hi there
In all the years I've been running computers ==> from as far back as Win /286 -- even before Windows 3.0 and the first really useable business version 3.11 I can honestly say I've NEVER EVER had a memory module fail.

Whilst its not impossible I would suggest your odds of winning the lottery 2 weeks in a row are better than a memory failure in a PC.

I'd look for another solution if I were you.

Cheers
jimbo

 

[pbcopter]

Where can I enter that lottery. I just replaced a pair of Corsair Dominator modules after one went bad. MemTest verified it and the new pair work fine. They were in my system for one month.

 

[Tews]

I'd like to buy that ticket too! Never rule out any component just because it traditionally has a low failure rate... you cant afford to do that... also, dont be too quick to rule out your DVD just because you were able to install it on a different machine... machines are as different as women ... hope Im not being sexist here .. does anyone see Joan lurking about??

 

[Night Hawk]

A good deal of the problems people run into are either a bad dimm or when adding a mix of simms, dimms, sodimms, whatever some type of mismatch. I've also seen where a weak battery on a rather new board saw memtest report a ton of errors for two separate sets of dimms later to be found in perfect working condition.

The key word is never rule anything out entirely! You first need to isolate the problem each step at a time.

 

[MaDDN3ss]

Thought I'd give you all an update as now my problem is solved!!
Thanks for you advice.

I had two issues..
1.) One stick of my RAM was bad. Ran Memtest and it proved faulty. Got it replaced by the computer store.

Tried to install Win7 again and it hung but I got a different message..

2.) I was dumb. For some reason I hooked my DVD-RW to the internal e-SATA port on the motherboard. I switched it to the standard SATA ports and all worked flawlessly.


Thanks again guys.
Now running Win7 X64 in RAID0 on my Raptors.

 

[Tews]

Glad to hear you got it running again!

 

[Night Hawk]

Glad to hear you have that all sorted out. At least now you'll know enough to take things a little slower the next time around to see working results. It's all part of the learning process once you get into custom building and the like!

 

[MaDDN3ss]

Well the sad thing is this is about the 6th system I've built. Plus I usually end up overclocking my systems and tweaking them until they are "just right" . When they crash I know that it's probably because I pushed it too far.

The problem with a new build this is I don't take my time as now it seems "old hat".
I have never really ran into any issues on a new build so I got frustrated easily this time around and didn't think it out.

Again thanks for everyone's help on this. Looks like I found a good community of people here so I figure I'll stay a bit.

 

[chev65]

Thought I'd give you all an update as now my problem is solved!!
Thanks for you advice.

I had two issues..
1.) One stick of my RAM was bad. Ran Memtest and it proved faulty. Got it replaced by the computer store.

Tried to install Win7 again and it hung but I got a different message..

2.) I was dumb. For some reason I hooked my DVD-RW to the internal e-SATA port on the motherboard. I switched it to the standard SATA ports and all worked flawlessly.


Thanks again guys.
Now running Win7 X64 in RAID0 on my Raptors.

Looks like someone just won the lottery twice LOL. Memory is by far the most likely piece of hardware to fail. It takes some people awhile to figure that out.