ok, my full system specs are now listed in the "my system specs" thing
at the bottom of my posts.

the error codes listed are 0x07f, 0x0a, 0x00, 0x04, 0xffd0f4f0, and
0x822a0360 (excess "0"'s truncated but all error codes are 8 digits
after the "x")

i know not of this "memory hole remapping" you speak of, so i would
have to say no.

cpu core temp currently at 43.1*C according to the screen on the front
of my case. the sensor is placed in the middle of the heatsink fins.

that work for you mr. mark h?


--
tednelson83

the memory diagnostic tool reported no errors found.


--
tednelson83

On Thu, 11 Sep 2008 08:04:24 -0500, tednelson83
wrote:

ok, my full system specs are now listed in the "my system specs" thing
at the bottom of my posts.

the error codes listed are 0x07f, 0x0a, 0x00, 0x04, 0xffd0f4f0, and
0x822a0360 (excess "0"'s truncated but all error codes are 8 digits
after the "x")

i know not of this "memory hole remapping" you speak of, so i would
have to say no.

cpu core temp currently at 43.1*C according to the screen on the front
of my case. the sensor is placed in the middle of the heatsink fins.

that work for you mr. mark h?


--
tednelson83


Above is your whole post. Where is the "thing" with your specs?

OK, next step I'd try is to check if the BSOD issue occurs when running in
Safe Mode... to figure out if a 3rd party app/service is the culprit.

Bothers me that this happens after reinstall - "windows failure almost every
day since 6/25/08 when i last wiped it." I assume "wiped" means
"reinstalled." Might also mean "cleaned" up or such?

More, "reliability index id down to a 2.60" Do you see any pattern -
hardware, apps - that might cause such a low index?

Here's a thread on low RIndex issues:
http://www.nvnews.net/vbulletin/showthread.php?t=86230
For more about Reliability sco
http://technet.microsoft.com/en-us/l.../cc722173.aspx

Post back with the Safe Mode outcome.
Michael



"tednelson83" wrote in message
...

the memory diagnostic tool reported no errors found.


--
tednelson83

Excellent! Error messages!

So, let's look at the commonality:

0x7F: Hardware issue
You're overclocking incorrectly.
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 2500 MhZ processor to run at 2870 MhZ).


0x0A: Driver issue related to RAM
I don't think you're trying to install Vista, so the following probably
applies:
You experience this problem if the following conditions are true: . The
computer has an NVIDIA chipset.
. The computer has four gigabytes (GB) or more of RAM.


0x00: This is a bug check code.
This typically implies a driver did something stupid, so it was stopped.

0x04: This is a bug check code.
This typically implies a driver did something stupid, so it was stopped.

0x8xxxxxxx: Data_Bus_Error
Problem accessing memory

0xFFD0F4F0: Never seen this one.

Commonality:
Driver issue accessing memory.
Probably due to the 10% overclocking function which can cause peripheral
hardwa memory, controllers, integrated sound, etc. to suddenly
malfunction producing random BSODs. The real pointer to the overclock
problem is that they are inconsistent errors. Since most of these are memory
related, you probably resulted in a CPU speed increase without lowering your
FSB multiplier and exceeded the ability of your memory. But, this is all a
guess since your specs still haven't made it to the public. :-)

Have you still had problems since you restored nomal clocking?



"tednelson83" wrote in message
...

ok, my full system specs are now listed in the "my system specs" thing
at the bottom of my posts.

the error codes listed are 0x07f, 0x0a, 0x00, 0x04, 0xffd0f4f0, and
0x822a0360 (excess "0"'s truncated but all error codes are 8 digits
after the "x")

i know not of this "memory hole remapping" you speak of, so i would
have to say no.

cpu core temp currently at 43.1*C according to the screen on the front
of my case. the sensor is placed in the middle of the heatsink fins.

that work for you mr. mark h?


--
tednelson83

One thing I do when encountering strange or odd looking displays is to have
my digital camera handy and take a photo of the actual screen and make a
record of it. Sometimes I will post the relevant screen photos on a web
photo site so that those who are helping me solve the problem can see the
actual screen. The old adage about a picture and 1000 words is applicable
to computer problems as well! Just a thought....


"Richard Urban" wrote in message
...
Maybe if you posted the complete and accurate text in the blue screen???

--

Richard Urban
Microsoft MVP
Windows Desktop Experience


"tednelson83" wrote in message
...

ok... so how do i find out witch one? all drivers were the latest pulled
off the internet at the time of the install, and have all been checked
for newer updates. all are up to date. hardware, i haven't had these
problems in the past, ant there are no indications that any thing is
failing,so how do you narrow it down. that was a awfully vague reply.


--
tednelson83