Now I was just able to run a full scan with no reboot.. odd
Either way I'm just awaiting a new mobo now.. Gonna install that and do a fresh install of XP
Either way I'm just awaiting a new mobo now.. Gonna install that and do a fresh install of XP
thats what I assume.. as soon as the new mobo gets here I'm installing it and formatting... shiiit... I should format before I even install the new mobo
Odd things here too... my system is almost stable... I barely get BSOD's now, but they show up still, sooner or later. Perhaps it's not the memory and in 333mhz it functions properly, but now my Windows instalation is compromised... who knows. Well I'm about to sell my memories, so I'm going to buy 2 sticks of Kingston or Samsung RAM now. Hope this helps.
You can create a smaller partion and redo the OS. Will speed up the installation and you can have the remainding space and create a secondary partition to hold the data. You can always use partition magic or server magic for servers to resize the size of the drive letters. If the OS crap out, just redo it. Better yet, you can clone an image of the OS using Ghost. If it ever goes bad, put it back to the previous state and you know if that's either software or hardware issue.
My system is now STABLE.
One/two of two things solved the problem:
1 - The mobo's optimal settings for my memory were CAS 3.0 for 400mhz and CAS 2.5 for 333mhz, and I were using 333mhz. So I choose "by spd" and it set CAS 3 with 333mhz.
2 - I used the program Driver Cleaner 2 to erase all my ATI catalyst drivers(read somewhere it was causing problems), and then installed the new(at the time) 4.3 version. I have a Radeon 9500 @ 9700.
Now that 4.4 is out, I changed to omega drivers again - HUGE increase in performance... w/o overclocking.
By stable I mean more than two days straight without a single blue screen, lock, or any problem, running lots of heavy software. Even went into graphic driver problems with an old game and windows recovered beautifully, 6 times(I was trying different settings).
So, the most likely solution for the nforce2 + elixir DDR400 memory problem is to run it at 333mhz, with by spd setting. I think this happens with other cheap brand too, like Spectek. Hope anyone who has the same problem find his/her way here
One/two of two things solved the problem:
1 - The mobo's optimal settings for my memory were CAS 3.0 for 400mhz and CAS 2.5 for 333mhz, and I were using 333mhz. So I choose "by spd" and it set CAS 3 with 333mhz.
2 - I used the program Driver Cleaner 2 to erase all my ATI catalyst drivers(read somewhere it was causing problems), and then installed the new(at the time) 4.3 version. I have a Radeon 9500 @ 9700.
Now that 4.4 is out, I changed to omega drivers again - HUGE increase in performance... w/o overclocking.
By stable I mean more than two days straight without a single blue screen, lock, or any problem, running lots of heavy software. Even went into graphic driver problems with an old game and windows recovered beautifully, 6 times(I was trying different settings).
So, the most likely solution for the nforce2 + elixir DDR400 memory problem is to run it at 333mhz, with by spd setting. I think this happens with other cheap brand too, like Spectek. Hope anyone who has the same problem find his/her way here
Just replaced the mobo and I'm still getting "Cpu unworkable or has changed" error on bootup... arghhhh....
guess the next thing to do it get a replacement cpu
guess the next thing to do it get a replacement cpu
try turning CPU INTERFACE off, and all other OC's...
I read somewhere that our mobo has an issue with 10x multi for cpu clock and cpu interface, or some other multiplicator... maybe that'll solve. There's a user modified BIOS of an old version that worked this out, but then you get an old bug with SATA RAID... if you don't use it, I can search for this BIOS for you.
I read somewhere that our mobo has an issue with 10x multi for cpu clock and cpu interface, or some other multiplicator... maybe that'll solve. There's a user modified BIOS of an old version that worked this out, but then you get an old bug with SATA RAID... if you don't use it, I can search for this BIOS for you.
Everything seems to be good so far.... been running for about 12 hours now with no blue screens or anything..
Hopefully it stays this way
Hopefully it stays this way
Ok, I just got my first COMPLETLEY random blue screen.. Can someone possibly look at the dump for me and try to figure out what caused it?
thanks a lot
thanks a lot
Anyone? This is driving me crazy... blue screens all the time for no reason.. Usually happens when I'm running several programs at once
Seems that I said too much, too early
Well problems WERE gone, till I sold my memory at last...
Since mem prices are flying high, I couldn't buy 2 good modules here in Brazil(much higher price), and got a friend's samsung 512mb DDR400. He was using 2 of these in a system equal to mine in almost everything, just one difference, I have one more HD that's plugged into SATA with serillel.
I then put it in 400mhz and had happiness for 2 days. Then, the same BSOD returned from the dead!!! I didnt make a single change in the system in these 2 days. Now it freezes a lot.
Tried going for 333, no luck, just as bad. Well, in my case, it's not memory, because this module was working in my friend's pc. The disk warnings in event viewer had reappeared, and although they happen in the pagefile located in my PATA drive, I updated all my PATA and SATA drivers. No luck AGAIN. Since I read a lot about SATA RAID problems, I decided to put the HD in PATA and disable SATA.
Now I'm happy for about 1 hour. Let's see what happens
You would do good to disable SATA too, if you can... seems there are bugs in bioses 20+ with it and lots of others in previous versions.
Well problems WERE gone, till I sold my memory at last...
Since mem prices are flying high, I couldn't buy 2 good modules here in Brazil(much higher price), and got a friend's samsung 512mb DDR400. He was using 2 of these in a system equal to mine in almost everything, just one difference, I have one more HD that's plugged into SATA with serillel.
I then put it in 400mhz and had happiness for 2 days. Then, the same BSOD returned from the dead!!! I didnt make a single change in the system in these 2 days. Now it freezes a lot.
Tried going for 333, no luck, just as bad. Well, in my case, it's not memory, because this module was working in my friend's pc. The disk warnings in event viewer had reappeared, and although they happen in the pagefile located in my PATA drive, I updated all my PATA and SATA drivers. No luck AGAIN. Since I read a lot about SATA RAID problems, I decided to put the HD in PATA and disable SATA.
Now I'm happy for about 1 hour. Let's see what happens
You would do good to disable SATA too, if you can... seems there are bugs in bioses 20+ with it and lots of others in previous versions.
I've tried 3 different sticks of memory now, changed my motherboard, new power supply, everything... I dunno what else to try
I got a BSOD when replying here
Changing from SATA to PATA changed the BSODs from 7A to 1D. Still going to check what's that.
No disk warnings yet.
I sought help at Abit's forums and discovered that my vcore was 1.63v and not so much stable, when it should be 1.65v, stable. I tried upping it to 1.7v in BIOS and the system did not boot. Using the reset buttom solved
I'm still getting the BSOD's, so this didn't solve the problem.
The guys there told me to use memory timings at 11-3-3-2.5 instead of 7-3-3-2.5, but I dont think this'll help also, since my friend's system(equal to mine) ran at 6-3-3-2.5. They also told me my files may be corrupt and a clean install would do good, but I'm no inclined to do this right now
I want to try all that I can before that.
Try asking there too! abit.com.tw -> usa -> forums -> nvidia chipsets
Changing from SATA to PATA changed the BSODs from 7A to 1D. Still going to check what's that.
No disk warnings yet.
I sought help at Abit's forums and discovered that my vcore was 1.63v and not so much stable, when it should be 1.65v, stable. I tried upping it to 1.7v in BIOS and the system did not boot. Using the reset buttom solved
I'm still getting the BSOD's, so this didn't solve the problem.
The guys there told me to use memory timings at 11-3-3-2.5 instead of 7-3-3-2.5, but I dont think this'll help also, since my friend's system(equal to mine) ran at 6-3-3-2.5. They also told me my files may be corrupt and a clean install would do good, but I'm no inclined to do this right now
I want to try all that I can before that.
Try asking there too! abit.com.tw -> usa -> forums -> nvidia chipsets
Thinking about the corruption and my disk errors in the pagefile, I deleted and re-created the pagefile itself again. Things are smooth since then(about 12h running).
If I get another BSOD, I'll reinstall norton. If I get another, I'll uninstall ProtoWall. If I get one more, I'll just sell my PC
Now I bought a pair of Corsair value 1gb kit(2x512) CAS2.5. Should arrive in 12-16 days. Hope it works!!
BTW nags, have you looked at your eventviewer?? Start -> run -> EventVwr.msc
See if there's anything odd there.
If I get another BSOD, I'll reinstall norton. If I get another, I'll uninstall ProtoWall. If I get one more, I'll just sell my PC
Now I bought a pair of Corsair value 1gb kit(2x512) CAS2.5. Should arrive in 12-16 days. Hope it works!!
BTW nags, have you looked at your eventviewer?? Start -> run -> EventVwr.msc
See if there's anything odd there.
hmmm.. I've never used this before and not 100% sure how to read it, but I'm showing massive amounts of errors
in eventviewer, go to the system tab
what kind of errors are you getting there?? you can double-click them for a little more detailed information.
also, get AIDA32 and see if your HD is reporting any SMART errors...
what kind of errors are you getting there?? you can double-click them for a little more detailed information.
also, get AIDA32 and see if your HD is reporting any SMART errors...
Almost forgot to say... I now think(again) my system is stable. Been running all day long, plus those 12h... about 36h straight. It must have been the serillel, I found another user that went into trouble with this adapter. RUN FROM IT
Maybe one day I'll try it again with my friend's serillel...
Maybe one day I'll try it again with my friend's serillel...
herre's one of them
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/16/2004
Time: 11:25:21 PM
User: N/A
Computer: NAGSXP
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf849619, parameter3 ed94b7f4, parameter4 00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 38 34 39 36 31 39 bf849619
0040: 2c 20 65 64 39 34 62 37 , ed94b7
0048: 66 34 2c 20 30 30 30 30 f4, 0000
0050: 30 30 30 30 0000
Please write down ALL your system specs here.
See if you PSU is enough here: http://www.jscustompcs.com/power_supply/
This error leads to the same of our BSOD's: hardware or drivers. Since you already replaced most of the hardware, I think it's either incompatibility(from memory) or some driver. Try a clean install with minimal configuration, just one stick of ram(see in your mobo's manual if there's a preferred slot when you use 1 module), one HD(cable select) and the video card. Maybe cdrom too so you can install things, but don't install anything unless it's absolutely necessary. Then update to XP SP1, install most updated chipset drivers and vidcard drivers. Run Prime95 for a day and see what happens... if it's good, create a system restore point and install one more hardware. Go on this way. If it turns bad, restore the system to the previous state and now you know what's causing you trouble.
Before all that, run memtest86(latest version, bootable CD) if you hadn't yet.
I had a really weirdo problem some years ago, caused by pure stupidity hehehe. The cooler I was using was VERY heavy, and it was stressing the mobo, so I put some other screw holders(this is not the correct name, but was the best I could think of) to support it better. Problem was that they were creating shorts!! Just putting some tape solved the problem, but I've gone through A LOT to find out that this was the cause
So think of these things too, maybe you didn't install something right. Remember Murphy's Law
See if you PSU is enough here: http://www.jscustompcs.com/power_supply/
This error leads to the same of our BSOD's: hardware or drivers. Since you already replaced most of the hardware, I think it's either incompatibility(from memory) or some driver. Try a clean install with minimal configuration, just one stick of ram(see in your mobo's manual if there's a preferred slot when you use 1 module), one HD(cable select) and the video card. Maybe cdrom too so you can install things, but don't install anything unless it's absolutely necessary. Then update to XP SP1, install most updated chipset drivers and vidcard drivers. Run Prime95 for a day and see what happens... if it's good, create a system restore point and install one more hardware. Go on this way. If it turns bad, restore the system to the previous state and now you know what's causing you trouble.
Before all that, run memtest86(latest version, bootable CD) if you hadn't yet.
I had a really weirdo problem some years ago, caused by pure stupidity hehehe. The cooler I was using was VERY heavy, and it was stressing the mobo, so I put some other screw holders(this is not the correct name, but was the best I could think of
) to support it better. Problem was that they were creating shorts!! Just putting some tape solved the problem, but I've gone through A LOT to find out that this was the cause So think of these things too, maybe you didn't install something right. Remember Murphy's Law
That page shows I should have a 330watt Power supply... I'm running an Antec Trupower 550..
I've dont basically everything you say and I just can't seem to pinpoint the problem
its a p4 2.4 800mhz fsb
1gb memory
basic agp radeon vid card
onboard sound
abit vt7 mobo
I've dont basically everything you say and I just can't seem to pinpoint the problem
its a p4 2.4 800mhz fsb
1gb memory
basic agp radeon vid card
onboard sound
abit vt7 mobo
Dude I thought you had a NF7
did you do a clean install?? added hardware and software one by one?? doing this you should pinpoint the problem!!! Hardware FAILURE you probably dont have. Hardware incompatibility could be. But I think it's a driver or software related problem.
what has become of that cpu unworkable error??
are you getting random BSOD's or they're always the same? write them down and put here.
please put ALL your system configuration here, but with detailed information about all your hardware, like vendor, model, etc. Also tell me your windows version and programs installed that run in background.
My PC is not stable as I thought, I had BSOD's again with that norton file, 2 times. I've heard so much about problems with symantec products that I'll uninstall it all and see if this solves it.
did you do a clean install?? added hardware and software one by one?? doing this you should pinpoint the problem!!! Hardware FAILURE you probably dont have. Hardware incompatibility could be. But I think it's a driver or software related problem.
what has become of that cpu unworkable error??
are you getting random BSOD's or they're always the same? write them down and put here.
please put ALL your system configuration here, but with detailed information about all your hardware, like vendor, model, etc. Also tell me your windows version and programs installed that run in background.
My PC is not stable as I thought, I had BSOD's again with that norton file, 2 times. I've heard so much about problems with symantec products that I'll uninstall it all and see if this solves it.
Theres not much to say about my system then what I already listed. One memory stick is a Kingston 512 and the other Elixir. I've tried either one at the same time and still got them
The BS's are SO random and so infrequent that its hard to pinpoint anything. It's actually been probably 4 days since I've got a blue screen
The BS's are SO random and so infrequent that its hard to pinpoint anything. It's actually been probably 4 days since I've got a blue screen
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter