Bevo
Nah
+718|6779|Austin, Texas
Ran the full test, it passed
King_County_Downy
shitfaced
+2,791|6856|Seattle

Well, once you've narrowed down HD, PSU, RAM, OS/Drivers, etc... the only thing left is the mobo, right?

Sucks dude.

I don't know what esle to suggest.
Sober enough to know what I'm doing, drunk enough to really enjoy doing it
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

King_County_Downy wrote:

Well, once you've narrowed down HD, PSU, RAM, OS/Drivers, etc... the only thing left is the mobo, right?

Sucks dude.

I don't know what esle to suggest.
I don't think we've completely narrowed down to memory or board yet. He needs to run each dimm in each slot for a least one pass. However, it does seem like it is your board.
Bevo
Nah
+718|6779|Austin, Texas

King_County_Downy wrote:

Well, once you've narrowed down HD, PSU, RAM, OS/Drivers, etc... the only thing left is the mobo, right?

Sucks dude.

I don't know what esle to suggest.
Well I don't know, HAVE I narrowed everything down? I checked the RAM but not in every slot, I "checked" the HDD but who knows maybe it missed something, I reinstalled the OS once but it could have become corrupt again for whatever reason...

I just got an error for displayfusion while rebooting again,

"Error while setting value blah blah blah"
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt"

Is this referring to the RAM or the HDD? Also, my control panel seems to be frozen with almost nothing running on my computer, does that point towards anything?
Bevo
Nah
+718|6779|Austin, Texas
Switched the RAM to the other two slots like sonder suggested a long time ago and it appears to be working.

I'll have to give it a week or so and if I see no issues I guess I'll RMA the mobo.
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bevo wrote:

Switched the RAM to the other two slots like sonder suggested a long time ago and it appears to be working.

I'll have to give it a week or so and if I see no issues I guess I'll RMA the mobo.
Run memtest with that config too. At least one full pass w/o errors and we could be pretty certain the memory controller on the board is prob hosed.
Bevo
Nah
+718|6779|Austin, Texas

SonderKommando wrote:

Bevo wrote:

Switched the RAM to the other two slots like sonder suggested a long time ago and it appears to be working.

I'll have to give it a week or so and if I see no issues I guess I'll RMA the mobo.
Run memtest with that config too. At least one full pass w/o errors and we could be pretty certain the memory controller on the board is prob hosed.
With both sticks in? Memtest86 doesn't seem to like when I do that.
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver
Well technically you should be able to run both.. If you can run each stick individually successfully in each slot then i would def think your memory controller is boned since it won't run dual channel without fucking up. Your banks should be color coded, when a DIMM is in matching colored slots you're running dual channel mode (fyi, if ya didn't know). So, if they pass individually we will know Its the board for sure.
Bevo
Nah
+718|6779|Austin, Texas
well who knows, more than 1 at a time never worked in my old PC either, but I'm pretty sure that mobo was fucked too.

I got a bluescreen last night while shutting down May be back at square 1
blademaster
I'm moving to Brazil
+2,075|6904
yeah been having similar issues with my desktop I think I read it may be at least in my case due to a specific sound driver....
Bevo
Nah
+718|6779|Austin, Texas
Got this one this morning

There was a problem starting C:\Program Files(x86)\NOS\bin\getPlus_Helper.dll

and then not 10 seconds after I posted this I got a bluescreen.

ed: gotten this same issue the last 3 times ive booted.

Last edited by Bevo (2010-04-22 08:12:17)

bugz
Fission Mailed
+3,311|6570

Do you know what NOS is and why it tries to run at startup?
13urnzz
Banned
+5,830|6756

he installed nitrous oxide for a performance boost.
Bevo
Nah
+718|6779|Austin, Texas

ebug9 wrote:

Do you know what NOS is and why it tries to run at startup?
not a bloody clue

but xfire also seems to have forgotten my username and password too

I'm so fucking confused.
King_County_Downy
shitfaced
+2,791|6856|Seattle

Disconnect your DVD/CD drives. I've had a bad DVD drive fuck with me for weeks before I figured out. Just a thought...
Sober enough to know what I'm doing, drunk enough to really enjoy doing it
Bevo
Nah
+718|6779|Austin, Texas

King_County_Downy wrote:

Disconnect your DVD/CD drives. I've had a bad DVD drive fuck with me for weeks before I figured out. Just a thought...
Okies, disconnected.

Next thing to do is wipe my old HDD and try booting from there I suppose.
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bevo wrote:

King_County_Downy wrote:

Disconnect your DVD/CD drives. I've had a bad DVD drive fuck with me for weeks before I figured out. Just a thought...
Okies, disconnected.

Next thing to do is wipe my old HDD and try booting from there I suppose.
I would wait on that.  The point of disconnecting the drives is to boot at a minimalist state (only essential hardware) I would disconnect those, put in one stick of ram, use on board video if you can, and remove any sound cards or peripherals.  For example, you want to boot with maybe just CPU, PSU, HDD w/ OS, and RAM.  Then see if it is stable.  If so, then add components until you crash again. 

BUT, at this point I got a feeling that your board is hosed.
Bevo
Nah
+718|6779|Austin, Texas
The common link seems to be "xyz" failing. Whether it's programs or (I guess bluescreens mean) the OS. And it seems that this decision is made at startup.

I don't know if that points to mobo or not. I'll start trying bare minimum soon.
Bevo
Nah
+718|6779|Austin, Texas
Stripped to bare minimum.

Booting up for 10 minutes, waiting for bluescreen, rebooting when none is found.

Joy.
Jaekus
I'm the matchstick that you'll never lose
+957|5437|Sydney
I really hope you can get to the bottom of this. It's starting to bug me as to what it is, so I can only begin to imagine what it's like for you.
Bertster7
Confused Pothead
+1,101|6840|SE London

King_County_Downy wrote:

Well, once you've narrowed down HD, PSU, RAM, OS/Drivers, etc... the only thing left is the mobo, right?

Sucks dude.

I don't know what esle to suggest.
Why has no one suggested CPU yet?

This sort of behaviour from the system is in line with the sort of issues you can get from a dodgy CPU. DOA CPUs are less common than most of the other parts suggested, but it could still be that.
Jaekus
I'm the matchstick that you'll never lose
+957|5437|Sydney
I had a CPU that went faulty, but it kept overheating. The only bluescreen issue I had was my BIOS.

I'm no expert by any stretch so just forget I said anything.
SonderKommando
Eat, Lift, Grow, Repeat....
+564|6918|The darkside of Denver

Bertster7 wrote:

King_County_Downy wrote:

Well, once you've narrowed down HD, PSU, RAM, OS/Drivers, etc... the only thing left is the mobo, right?

Sucks dude.

I don't know what esle to suggest.
Why has no one suggested CPU yet?

This sort of behaviour from the system is in line with the sort of issues you can get from a dodgy CPU. DOA CPUs are less common than most of the other parts suggested, but it could still be that.
I did earlier.  seeing as teh BSOD is referencing an IRQ error.
Bevo
Nah
+718|6779|Austin, Texas
Have yet to get a bluescreen, but will probably try at least another 10 boots.

If I do start getting bluescreens though, how would I know if it was the processor or the mobo?
Bertster7
Confused Pothead
+1,101|6840|SE London

SonderKommando wrote:

Bertster7 wrote:

King_County_Downy wrote:

Well, once you've narrowed down HD, PSU, RAM, OS/Drivers, etc... the only thing left is the mobo, right?

Sucks dude.

I don't know what esle to suggest.
Why has no one suggested CPU yet?

This sort of behaviour from the system is in line with the sort of issues you can get from a dodgy CPU. DOA CPUs are less common than most of the other parts suggested, but it could still be that.
I did earlier.  seeing as teh BSOD is referencing an IRQ error.
So you did - I've only been skimming this thread....

And looking at those errors, I'd say CPU or Mobo. Unfortunately the most awkward parts to test properly.

Bevo wrote:

Have yet to get a bluescreen, but will probably try at least another 10 boots.

If I do start getting bluescreens though, how would I know if it was the processor or the mobo?
By swapping them out with ones that you know work and prolonged testing.

Last edited by Bertster7 (2010-04-23 11:55:33)

Board footer

Privacy Policy - © 2025 Jeff Minard