STOP errors maybe related to faulty cache memory? NEED HELP
Dear All, My cmputer has tripped out on me. Every time i try to start Windows Xp setup it gives me a STOP error with a different message depending on my hardware/bios settings. Right now I have a minimal set of hardware (hard drive, DVD drive, and video card).
Dear All,
My cmputer has tripped out on me. Every time i try to start Windows Xp setup it gives me a STOP error with a different message depending on my hardware/bios settings. Right now I have a minimal set of hardware (hard drive, DVD drive, and video card). I get stop errors like crazy when i try to set up or boot XP.
Sometimes it says IRQ_NOT_LESS_THAN_OR_EQUAL_TO other times i get an acpi.sys error, and sometimes even a PCIIDEX.sys error! HELP! I need to do my micro assembly homework. this is URGENT!
Note: as instructed to do so by the STOP error, i disabled my cache memory and setup began, but it is really REALLY slow. I want to be able to use my cache memory!
My cmputer has tripped out on me. Every time i try to start Windows Xp setup it gives me a STOP error with a different message depending on my hardware/bios settings. Right now I have a minimal set of hardware (hard drive, DVD drive, and video card). I get stop errors like crazy when i try to set up or boot XP.
Sometimes it says IRQ_NOT_LESS_THAN_OR_EQUAL_TO other times i get an acpi.sys error, and sometimes even a PCIIDEX.sys error! HELP! I need to do my micro assembly homework. this is URGENT!
Note: as instructed to do so by the STOP error, i disabled my cache memory and setup began, but it is really REALLY slow. I want to be able to use my cache memory!
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
If I read your previous post you are saying these precise parts were functioning and the CPU is made for, and was running 10,5 x 133 so it can function - unless some hardware part has broken. I would narrow down the possible source of the problem by:
1) clear the CMOS to be sure no Bios setting is causing this.
2) reformat and reinstall XP to see if something went wrong there
If that doesn't help you have to test the CPU on a different Mbo to see if its still OK, and run the Mobo with a diff CPU to see if has blown.
Oh, one more idea - could the CPU be overheating?
H
1) clear the CMOS to be sure no Bios setting is causing this.
2) reformat and reinstall XP to see if something went wrong there
If that doesn't help you have to test the CPU on a different Mbo to see if its still OK, and run the Mobo with a diff CPU to see if has blown.
Oh, one more idea - could the CPU be overheating?
H
Thanx for the reply.
I have just reset te BIOS.Ofcoarse it defaulted to 100MHZ/100MHZ (1050MHZ).When I set it to 133MHZ/133MHZ it did the same thing!
I have also tried reformatting / re setting up several times, BUT the setup will not even start orcontinue unless I have it set at 1GHZ.
As for the CPU overheating, I doubt it. I have ran that CPU formonths without a single hitch like this, so even though overheating IS possible, it is highly unlikely.
I am gonna try borrowing a RAM chip from a freind. If i STILL have trouble, then maybe my processor and/or motherboard have gone defective!
I'm just pissed that I can only run at 1GHZ when I paid hard-earned money for a 1.4GHZ,andi know the 1.4ghz configuration worked before!
If someone has any ideas please do not hesitate to share them!
PS: Sorry guys if I seem to reply with a sharp tone. I am just frustrated. Also,I use CAPITAL LETTERS for emphasis, NOT for shouting!
I have just reset te BIOS.Ofcoarse it defaulted to 100MHZ/100MHZ (1050MHZ).When I set it to 133MHZ/133MHZ it did the same thing!
I have also tried reformatting / re setting up several times, BUT the setup will not even start orcontinue unless I have it set at 1GHZ.
As for the CPU overheating, I doubt it. I have ran that CPU formonths without a single hitch like this, so even though overheating IS possible, it is highly unlikely.
I am gonna try borrowing a RAM chip from a freind. If i STILL have trouble, then maybe my processor and/or motherboard have gone defective!
I'm just pissed that I can only run at 1GHZ when I paid hard-earned money for a 1.4GHZ,andi know the 1.4ghz configuration worked before!
If someone has any ideas please do not hesitate to share them!
PS: Sorry guys if I seem to reply with a sharp tone. I am just frustrated. Also,I use CAPITAL LETTERS for emphasis, NOT for shouting!
You anger is understandable, your system should run as designed.
Do I understand this correctly, you say the BIOS defaulted to a FSB of 100 after you resetted CMOS and reverted back after you changed the FSB manually to 133 ? That implies that the CPU is not identified properly. Does your BIOS tell what CPU is found ? Can you set the CPU manually also ? If so, set the multiplier to 10,5 and the FSB to 133. Check that your RAM latency is at 2,5 (or 3). If you can set the multiplier manually in BIOS, try lower multipliers (8,9,10) and the FSB still at 133 to see if that works. If you have any settings between 100 and 133 for the FSB, try them also.
Also, some boards (my Abit KG7 for one) are picky about which slot the DDR-RAM is poulated from, could it be that you have switched slot for your stick lately?
Just another check; you did reset the BIOS by the book? Power off, powercord out, short the jumper for a few seconds. Taking the battery out for 30-60 minutes does the same thing.
Your temps would be good to know. The heat conducting tape/sticker grows old sometimes, and the heatsink and fan collect dust. Also, if you've had the CPU out of its slot lately you could have inadvertedly caused a bad contact between CPU and heatsink. I'd guess your bios has a "health" screen where you can see the CPU temp, for an not O/C Athlon 1400, you should be looking at a temp of max 40-50 C idle, case open. What are your temps? As you are in the BIOS, please post your voltages too.
BTW, ...put a floppy drive in the system. If you can boot with 133 Mhz at all (doesn't sound like it) boot from a good ol' DOS floppy. One thing is for sure, if you can't run DOS, you're very unlikely to be able to run XP, and this way you can better differentiate between a hardware failure and a WIN failure.
I take it you bought the Athlon from a reputable vendor and then you are likely to be OK. But, be aware, there has been many reports of ppl selling overclocked CPU's as the real thing. If (or maybe rather when...) you decide to replace the heat conducting material, you'll anyhow first need to clean the CPU carefully. Write down all the text on the CPU, this is the only positive way to identify which CPU you have.
H.
Do I understand this correctly, you say the BIOS defaulted to a FSB of 100 after you resetted CMOS and reverted back after you changed the FSB manually to 133 ? That implies that the CPU is not identified properly. Does your BIOS tell what CPU is found ? Can you set the CPU manually also ? If so, set the multiplier to 10,5 and the FSB to 133. Check that your RAM latency is at 2,5 (or 3). If you can set the multiplier manually in BIOS, try lower multipliers (8,9,10) and the FSB still at 133 to see if that works. If you have any settings between 100 and 133 for the FSB, try them also.
Also, some boards (my Abit KG7 for one) are picky about which slot the DDR-RAM is poulated from, could it be that you have switched slot for your stick lately?
Just another check; you did reset the BIOS by the book? Power off, powercord out, short the jumper for a few seconds. Taking the battery out for 30-60 minutes does the same thing.
Your temps would be good to know. The heat conducting tape/sticker grows old sometimes, and the heatsink and fan collect dust. Also, if you've had the CPU out of its slot lately you could have inadvertedly caused a bad contact between CPU and heatsink. I'd guess your bios has a "health" screen where you can see the CPU temp, for an not O/C Athlon 1400, you should be looking at a temp of max 40-50 C idle, case open. What are your temps? As you are in the BIOS, please post your voltages too.
BTW, ...put a floppy drive in the system. If you can boot with 133 Mhz at all (doesn't sound like it) boot from a good ol' DOS floppy. One thing is for sure, if you can't run DOS, you're very unlikely to be able to run XP, and this way you can better differentiate between a hardware failure and a WIN failure.
I take it you bought the Athlon from a reputable vendor and then you are likely to be OK. But, be aware, there has been many reports of ppl selling overclocked CPU's as the real thing. If (or maybe rather when...) you decide to replace the heat conducting material, you'll anyhow first need to clean the CPU carefully. Write down all the text on the CPU, this is the only positive way to identify which CPU you have.
H.
You say that you think CPU heat probs are unlikely, but concede they may be a possibility, so why not eliminate that possibility - check the temps. You could use whatever hardware monitoring prog came with your mobo, or MBM5, or you could try SpeedFan. It's a great little prog that does what most hardware monitoring progs do, but also monitors your HDD temp as well [assuming your drive(s) have a temp. sensor, & the prog can recognise it]. Also its system tray icon displays the temp of whichever sensor you've told it to, so is easier to keep an eye on it.
Disclaimer: I have no affiliation with the chap who wrote it, I just think it's a really cool little prog.
Disclaimer: I have no affiliation with the chap who wrote it, I just think it's a really cool little prog.
The error messages you have been receiving are timing related as well as driver related. Your peripherals are not being recognized correctly at 133FSB. You see this on some systems that have been overclocked and some one component be it a controller, memory stick, a pci card or the AGP, or even the processor can't reckon with the higher FSB. Some component cannot keep up with the higher instruction rate. This could be as simple as the DVD drive not having DMA support or it could be what both Harry and Alien have astutely indicated as possible heat problems
Harry and Alien suspect overheating. While you have made it abundantly clear that system is not overclocked, you are running the FSB higher which is going to produce more heat. As you have pointed out this system has run fine for six months without a hitch and it is rated for the speed you have been running it at. But, if there are heat problems, even if very slight, it is known that certain components degrade and cannot tolerate a higher FSB after a period of time, even though they ran flawlessly previously.
Let us know how your tests come out.
Harry and Alien suspect overheating. While you have made it abundantly clear that system is not overclocked, you are running the FSB higher which is going to produce more heat. As you have pointed out this system has run fine for six months without a hitch and it is rated for the speed you have been running it at. But, if there are heat problems, even if very slight, it is known that certain components degrade and cannot tolerate a higher FSB after a period of time, even though they ran flawlessly previously.
Let us know how your tests come out.
Sampson: It could also be that he might have accidently knocked his PC & the HSF might have been jarred slightly out of place - just enough to reduce the effectiveness of the cooling, so that @ 1Ghz it would be just enough, but @ 1.4 Ghz it might not be enough.
Another thing that occured to me shassouneh, is whether or not you have any surge protection for your PC, as 1 big surge/spike might have somehow partially damaged something, or smaller surges over time can cause accumulating damage to your system. I have no idea if this is an issue in your case, but just thought I'd mention it.
Another thing that occured to me shassouneh, is whether or not you have any surge protection for your PC, as 1 big surge/spike might have somehow partially damaged something, or smaller surges over time can cause accumulating damage to your system. I have no idea if this is an issue in your case, but just thought I'd mention it.
Quote:
I Know for a fact the motherboard has a 266MHZ FSB.
I'd just like to take this oppurtunity to point out the fact that it isn't exactly a 266Mhz FSB but rather a 133Mhz one that transfers two bits per clock cycle (also called "Double Data Rate" or DDR for short.). While the end result is exactly the same as a bus that operates at 266Mhz but only transfers one bit bper clock cycle calling it a "266Mhz" bus is much like saying an Athlon XP 1800+ runs at 1.8Ghz.
I Know for a fact the motherboard has a 266MHZ FSB.
I'd just like to take this oppurtunity to point out the fact that it isn't exactly a 266Mhz FSB but rather a 133Mhz one that transfers two bits per clock cycle (also called "Double Data Rate" or DDR for short.). While the end result is exactly the same as a bus that operates at 266Mhz but only transfers one bit bper clock cycle calling it a "266Mhz" bus is much like saying an Athlon XP 1800+ runs at 1.8Ghz.
Hey Admiral,
there are no Mobos or CPU's or RAM running a true 266 FSB as you describe it. They all do 133 FSB counting one upwards and one downwards on the sinus curve.
So - whats your point ?
H.
there are no Mobos or CPU's or RAM running a true 266 FSB as you describe it. They all do 133 FSB counting one upwards and one downwards on the sinus curve.
So - whats your point ?
H.
Dear All,
Thank you for your extensive support and feedback. Allow me to give you some updates / data as Dirty Harry pointed out.
1.) Average IDLE CPU temperature (with case open) and as reported by BIOS: 38 C [i beleive in "open case technology" so the case is always open].
2.) I cannot manually set the multiplier. The BIOS ONLY allows me to change the RAM cycle speed (100 or 133 MHZ) and the processor cycle speed (100 or 133 MHZ). to get at 1.4GHZ, I have to have them both set at 133MHZ
4.) The Voltage (of the CPU) again, as reported by the BIOS and with an open case: 1.8 Volts
5.) RAM Latency: I tried ALL of 2T, 2.5T and 3T. Not a da** bit of a difference
6.) RAM Slots. I have two DDR ram slots and two SDRAM slots. I tried switching the RAM chip back and forth between the two DDR slots. No difference whatsoever.
7.) The processor has NOT been fiddled with, meaning I haven't moved it since I installed it. So I am pretty confident its not a CPU-contact thing.
Now allow me to describe the general behaviour of the computer:
Windows XP will now ONLY boot at 1.4GHZ. If i set it at 1GHZ, it would just hang after the hidden "starting windows xp" stuff.
When the machine does boot, it runs anywhere from 10 to 20 minutes before giving a STOP error. If I run anything heavey (e.g Return to Castle Wolfenstein), I get a stop error IMMEDIATELY.
Now allow me to give you my hardware specs (just in case they may be needed):
Motherboard: ECS K75SA Athlon/Athlon XP motherboard. Built in LAN card and sound card
Processor: Genuine AMD Athlon 1.4GHZ
RAM: DDR 2100 256MB chip
Video Card: Nvidia GeForce 2 MX400 AGP 4x 64MB
Sound Card: SBPCI 512 PCI
Hard Drive: IBM Deskstar 60GB 7200 rpm
For More details on my hardware / system information, please click the link below. (NOTE: OPEN IT IN YOUR WEB BROWSER! DO NOT RIGHT CLICK/SAVE TARGET AS). THEN you can save it. Its a ZIP file that contains a text file which describes my exact system!
OPEN ME IN A WEB BROWSER
Thank you for your extensive support and feedback. Allow me to give you some updates / data as Dirty Harry pointed out.
1.) Average IDLE CPU temperature (with case open) and as reported by BIOS: 38 C [i beleive in "open case technology" so the case is always open].
2.) I cannot manually set the multiplier. The BIOS ONLY allows me to change the RAM cycle speed (100 or 133 MHZ) and the processor cycle speed (100 or 133 MHZ). to get at 1.4GHZ, I have to have them both set at 133MHZ
4.) The Voltage (of the CPU) again, as reported by the BIOS and with an open case: 1.8 Volts
5.) RAM Latency: I tried ALL of 2T, 2.5T and 3T. Not a da** bit of a difference
6.) RAM Slots. I have two DDR ram slots and two SDRAM slots. I tried switching the RAM chip back and forth between the two DDR slots. No difference whatsoever.
7.) The processor has NOT been fiddled with, meaning I haven't moved it since I installed it. So I am pretty confident its not a CPU-contact thing.
Now allow me to describe the general behaviour of the computer:
Windows XP will now ONLY boot at 1.4GHZ. If i set it at 1GHZ, it would just hang after the hidden "starting windows xp" stuff.
When the machine does boot, it runs anywhere from 10 to 20 minutes before giving a STOP error. If I run anything heavey (e.g Return to Castle Wolfenstein), I get a stop error IMMEDIATELY.
Now allow me to give you my hardware specs (just in case they may be needed):
Motherboard: ECS K75SA Athlon/Athlon XP motherboard. Built in LAN card and sound card
Processor: Genuine AMD Athlon 1.4GHZ
RAM: DDR 2100 256MB chip
Video Card: Nvidia GeForce 2 MX400 AGP 4x 64MB
Sound Card: SBPCI 512 PCI
Hard Drive: IBM Deskstar 60GB 7200 rpm
For More details on my hardware / system information, please click the link below. (NOTE: OPEN IT IN YOUR WEB BROWSER! DO NOT RIGHT CLICK/SAVE TARGET AS). THEN you can save it. Its a ZIP file that contains a text file which describes my exact system!
OPEN ME IN A WEB BROWSER
shassouneh,
Obviously you've done something to be able to get it to boot at 1.4GHz when last night it would only run stable at a 100FSB. It would be helpful to know how you accomplished that.
Issue 1 Heat:
This is what I could find out on the web that others have encountered with this mobo and their advice: "Check your CPU heatsink and make sure it is spec. up to support your processor. Certain older coolers can support up to TB 1.2G. This sort of heatsink will not be good enough for your athlonXP or 1.33G and above processors."
"The other possibility is due to the chipset's heatsink. If you remove the heatsink, you will notice that a double sided tape is used instead of thermal paste. The double sided tape is a bad conductor of heat and it will trap the heat of the chipset (that is why when you touch the heatsink, it feels cool). Remove the tape and apply thermal paste onto the surface of the heatsink and attach the heatsink by using two droplets of super glue on two diagnoal corners of the chipset (it might be difficult for you to remove the heatsink, so do it carefully)."
-----------------
You said you don't have a floppy. I counted at least two CD's and one DVD device on your sysinfo.txt One CD seems to be to be a scii. On the net there seemed to be an issue about DMA support for these devices for your mobo. Apparently for no reason a device that had DMA support reverts to PIO. A device like a CD-RW which expects DMA support and only has PIO can randomly crash a computer. So, we'll make this
Issue 2 DMA support
There were two sets of opinions about how to enable DMA support. Both groups seem to think that simply enabling it through XP didn't resolve the DMA support. One group said, "you do need to run SISIDE.EXE to make sure that all of the drives are in the correct DMA mode. Siside.exe does not produce any output when executed. Be aware that It's not enough to set 'DMA if Available' in the device manager, you need to use the utility." The other group did not like using SISIDE.EXE and had this solution, "1st you have to set everything to PIO mode under device manager 'IDE ATA/ATAPI Controllers'. Now After you have set both channels to PIO mode, reboot.When the system boots backup, change everything back to UltraDMA mode just like you did before. Reboot,and presto!"
Issue 3 XP shutdown
Some experienced problems in that shutdown proceded so hastily that some settings were not saved or became corrupted. This was given as a suggestion: "Some people suggest that modifying the HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Session Manager\Memory management\ClearPageFileAtShutdown to a value of 1 could help because one is giving a 1-2 secs delay for Windows to properly write HDD cache to disk."
There were issues with the USB ports. Some had them configured properly, they just didn't work, yet XP reported them as just fine.
There were issues with IRQ sharing especially with SB soundcards. Too many to go into now.
There were several reports of those who had run their setup for months and then added a new device like a CD who started to have issues like the one's you've been having. Then, again, one fellow replaced his battery and took care of things.
When the machine was running at 100FSB did it ever give you a stop message?
When the machine freezes after 15-20 minutes does it give a stop message? Would you have a screensaver coming up about that time?
Is the stop message different when you try to play something as opposed to letting it fail by itself?
I know this is a nightmare for you, maybe something will pan out.
Obviously you've done something to be able to get it to boot at 1.4GHz when last night it would only run stable at a 100FSB. It would be helpful to know how you accomplished that.
Issue 1 Heat:
This is what I could find out on the web that others have encountered with this mobo and their advice: "Check your CPU heatsink and make sure it is spec. up to support your processor. Certain older coolers can support up to TB 1.2G. This sort of heatsink will not be good enough for your athlonXP or 1.33G and above processors."
"The other possibility is due to the chipset's heatsink. If you remove the heatsink, you will notice that a double sided tape is used instead of thermal paste. The double sided tape is a bad conductor of heat and it will trap the heat of the chipset (that is why when you touch the heatsink, it feels cool). Remove the tape and apply thermal paste onto the surface of the heatsink and attach the heatsink by using two droplets of super glue on two diagnoal corners of the chipset (it might be difficult for you to remove the heatsink, so do it carefully)."
-----------------
You said you don't have a floppy. I counted at least two CD's and one DVD device on your sysinfo.txt One CD seems to be to be a scii. On the net there seemed to be an issue about DMA support for these devices for your mobo. Apparently for no reason a device that had DMA support reverts to PIO. A device like a CD-RW which expects DMA support and only has PIO can randomly crash a computer. So, we'll make this
Issue 2 DMA support
There were two sets of opinions about how to enable DMA support. Both groups seem to think that simply enabling it through XP didn't resolve the DMA support. One group said, "you do need to run SISIDE.EXE to make sure that all of the drives are in the correct DMA mode. Siside.exe does not produce any output when executed. Be aware that It's not enough to set 'DMA if Available' in the device manager, you need to use the utility." The other group did not like using SISIDE.EXE and had this solution, "1st you have to set everything to PIO mode under device manager 'IDE ATA/ATAPI Controllers'. Now After you have set both channels to PIO mode, reboot.When the system boots backup, change everything back to UltraDMA mode just like you did before. Reboot,and presto!"
Issue 3 XP shutdown
Some experienced problems in that shutdown proceded so hastily that some settings were not saved or became corrupted. This was given as a suggestion: "Some people suggest that modifying the HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Session Manager\Memory management\ClearPageFileAtShutdown to a value of 1 could help because one is giving a 1-2 secs delay for Windows to properly write HDD cache to disk."
There were issues with the USB ports. Some had them configured properly, they just didn't work, yet XP reported them as just fine.
There were issues with IRQ sharing especially with SB soundcards. Too many to go into now.
There were several reports of those who had run their setup for months and then added a new device like a CD who started to have issues like the one's you've been having. Then, again, one fellow replaced his battery and took care of things.
When the machine was running at 100FSB did it ever give you a stop message?
When the machine freezes after 15-20 minutes does it give a stop message? Would you have a screensaver coming up about that time?
Is the stop message different when you try to play something as opposed to letting it fail by itself?
I know this is a nightmare for you, maybe something will pan out.
Dear Sampson,
First of all allow me to express my gratitude for you helping me out and being ever so patient with me. Let me clear up an important few points here.
1.) I only haver TWO CD devices, one is a PlexWriter 8/4/32 (8432A), and the other a DVD drive. Both are running on the IDE channels.
2.) The stop message I get 15 to 20 minutes after the system has booted up differs! For example, when Nero was running (not burning enaything) the stop error was IRQL_NOT_LESS_OR_EQUAL. Other times its something else like just a series of hexadecimal numbers.
3.) Heating Issues. Even though it seems like an appealing idea that the heatsink isn't installed or mounted right, i HIGHLY doubt it, since the system was working PERFECTLY without a single hitch at 1.4GHZ.
4.) @ 1GHZ (100MHZ FSB) the system works PERFECTLY! However (as described in my previous post) the system will not even boot at 1GHZ any more. Windows will just HANG so I'm stuck at 1.4GHZ and a maximum of 20 to 30 minutes of NON heavy work (again, running a game as demanding as RTCW will IMMEDIATELY cause a stop error).
5.) I have an SB PCI 512 sound card. My onboard sound card has been disabled in the BIOS.I have 5 PCI ports available, and putting the sound card in any of them doesn't help at all regardless of which slot I put the card in.
6.) My mouse is a logitech USB wireless optical mouse. Its running at the USB port right now. To convince myself that its not a mouse issue, I ran it on a PS2 port (using an adapter that came with the mouse). Heck i even completely removed the mouse (and took out the batteries) and plugged in an old-school PS2 mouse. None of what I did with the mouse configuration did anything. The system STILL behaves in exactly the same way.
7.) I tried the trick you described about PIO/DMA and restarted, etc.. No effect at all. The system STILL behaves in the same way.
It seems the BEST way to test the system is runn to Return to Castle Wolfenstein since its a demanding application, and it works just fine with the 1 GHZ configuration, but IMMEDIATEY causes a stop error in the 1.4GHZ configuration.
Again, Thanx to everyone for all the support and feedback. I really do appreciate it
First of all allow me to express my gratitude for you helping me out and being ever so patient with me. Let me clear up an important few points here.
1.) I only haver TWO CD devices, one is a PlexWriter 8/4/32 (8432A), and the other a DVD drive. Both are running on the IDE channels.
2.) The stop message I get 15 to 20 minutes after the system has booted up differs! For example, when Nero was running (not burning enaything) the stop error was IRQL_NOT_LESS_OR_EQUAL. Other times its something else like just a series of hexadecimal numbers.
3.) Heating Issues. Even though it seems like an appealing idea that the heatsink isn't installed or mounted right, i HIGHLY doubt it, since the system was working PERFECTLY without a single hitch at 1.4GHZ.
4.) @ 1GHZ (100MHZ FSB) the system works PERFECTLY! However (as described in my previous post) the system will not even boot at 1GHZ any more. Windows will just HANG so I'm stuck at 1.4GHZ and a maximum of 20 to 30 minutes of NON heavy work (again, running a game as demanding as RTCW will IMMEDIATELY cause a stop error).
5.) I have an SB PCI 512 sound card. My onboard sound card has been disabled in the BIOS.I have 5 PCI ports available, and putting the sound card in any of them doesn't help at all regardless of which slot I put the card in.
6.) My mouse is a logitech USB wireless optical mouse. Its running at the USB port right now. To convince myself that its not a mouse issue, I ran it on a PS2 port (using an adapter that came with the mouse). Heck i even completely removed the mouse (and took out the batteries) and plugged in an old-school PS2 mouse. None of what I did with the mouse configuration did anything. The system STILL behaves in exactly the same way.
7.) I tried the trick you described about PIO/DMA and restarted, etc.. No effect at all. The system STILL behaves in the same way.
It seems the BEST way to test the system is runn to Return to Castle Wolfenstein since its a demanding application, and it works just fine with the 1 GHZ configuration, but IMMEDIATEY causes a stop error in the 1.4GHZ configuration.
Again, Thanx to everyone for all the support and feedback. I really do appreciate it
Now, one thing at a time. Don't try to tinker with Bios, hardware and windows settings at the same time.
- Its unlikely a heat issue if your CPU temp is 38C (unless you burn your finger on the heatsink).
- Its unlikely a BIOS setting, because you've resetted BIOS by the CMOS jumper.
Where does this leave you ? I'd put my next research efforts on the "faulty hardware" theory.
Remove all components, put back only the very basics including floppy and see if you can boot. Then test mobo / cpu / ram separately.
H.
- Its unlikely a heat issue if your CPU temp is 38C (unless you burn your finger on the heatsink).
- Its unlikely a BIOS setting, because you've resetted BIOS by the CMOS jumper.
Where does this leave you ? I'd put my next research efforts on the "faulty hardware" theory.
Remove all components, put back only the very basics including floppy and see if you can boot. Then test mobo / cpu / ram separately.
H.
shassouneh,
Cute name - Crashproof
Drive C:
Description Local Fixed Disk
Compressed No
File System FAT32
Size 14.64 GB (15,719,546,880 bytes)
Free Space 5.12 GB (5,494,857,728 bytes)
Volume Name WINDOWS
Volume Serial Number 103E17E9
Drive D:
Description Local Fixed Disk
Compressed No
File System FAT32
Size 23.64 GB (25,387,204,608 bytes)
Free Space 23.61 GB (25,347,031,040 bytes)
Volume Name STORAGE
Volume Serial Number 086717F4
Drive E:
Description Local Fixed Disk
Compressed No
File System FAT32
Size 2.93 GB (3,144,085,504 bytes)
Free Space 2.93 GB (3,143,942,144 bytes)
Volume Name CRASHPROOF
Volume Serial Number 065A17F6
Drive F:
Description CD-ROM Disc
Drive G:
Description CD-ROM Disc
Drive H:
Description Removable Disk
Drive I:
Description CD-ROM Disc
Drive M:
Description Network Connection
Provider Name \\linuxsux\mp3z
This is how your system sees your configuration. It counts 3 partitions on your hard drive and 3 CD Roms. Does that compute?
Cute name - Crashproof
Drive C:
Description Local Fixed Disk
Compressed No
File System FAT32
Size 14.64 GB (15,719,546,880 bytes)
Free Space 5.12 GB (5,494,857,728 bytes)
Volume Name WINDOWS
Volume Serial Number 103E17E9
Drive D:
Description Local Fixed Disk
Compressed No
File System FAT32
Size 23.64 GB (25,387,204,608 bytes)
Free Space 23.61 GB (25,347,031,040 bytes)
Volume Name STORAGE
Volume Serial Number 086717F4
Drive E:
Description Local Fixed Disk
Compressed No
File System FAT32
Size 2.93 GB (3,144,085,504 bytes)
Free Space 2.93 GB (3,143,942,144 bytes)
Volume Name CRASHPROOF
Volume Serial Number 065A17F6
Drive F:
Description CD-ROM Disc
Drive G:
Description CD-ROM Disc
Drive H:
Description Removable Disk
Drive I:
Description CD-ROM Disc
Drive M:
Description Network Connection
Provider Name \\linuxsux\mp3z
This is how your system sees your configuration. It counts 3 partitions on your hard drive and 3 CD Roms. Does that compute?
Hmm,weird. No it doesn't compute. I have A DVD drive a Burner (Cd rom),
so I have 2 CD ROM drives. The removable media is an external parralel port ZIP drive.
I am looking into the defective hardware theory! wish me luck
By the way, "crashproof" is a name i came up with since i would use that partition to dump any data i want to back up before an emergency format, hence its almost like "crash proofing" my system
ALSO NOTE: The sysinfo file above will be updated soon to reflect my NEW hardware configuration (the troublesome one). Check for the date of the file. Currently the date on the file is Apr 4th.
so I have 2 CD ROM drives. The removable media is an external parralel port ZIP drive.
I am looking into the defective hardware theory! wish me luck
By the way, "crashproof" is a name i came up with since i would use that partition to dump any data i want to back up before an emergency format, hence its almost like "crash proofing" my system
ALSO NOTE: The sysinfo file above will be updated soon to reflect my NEW hardware configuration (the troublesome one). Check for the date of the file. Currently the date on the file is Apr 4th.
Good luck, concentrate on getting the sys up full speed on a DOS floppy !
H.
H.
Also in your sysinfo.txt it shows your hard disk to have six partitions. They are not accounted for in the portion I pasted in above. If they do exist and overlap with all of these "CD roms" this is where your STOP 0x00000023 error comes into play. The system is identifying a partition as a CD rom or viceversa.
Maybe it is time to look at a new controller card.
Maybe it is time to look at a new controller card.
6 partitions:
C: (windows partition)
D: (storage partition)
E: ("crashproof" partition)
/: Linux roor partition
/swap: Linux Swap partition
/boot: Linux boot partition.
So the 6 partitions are well justfified. Again I shall update that sysinfo file soon, so keep checking it
C: (windows partition)
D: (storage partition)
E: ("crashproof" partition)
/: Linux roor partition
/swap: Linux Swap partition
/boot: Linux boot partition.
So the 6 partitions are well justfified. Again I shall update that sysinfo file soon, so keep checking it
Quote:
4.) This is a FRESH INSTALL of Windows XP. Meaning I already DID format and fdisk my hard drive.
OK, I took alook at your sysinfo file out of curiosity, altough I've already stated that you should leave Windoze out of the loop before you know your hardware is OK.
Your sysinfo says you have a floppy drive, and on a fresh install of XP you have TweakUI, Nero, Real Player etc etc installed ? You also seem to have plenty of programs loading with Windows. Just outta curiosity, how come your sysinfo is identifying your CPU correctly "Family 6 Model 4 Stepping 4" and saying it is running at the correct speed "AuthenticAMD ~1394 Mhz" and dated two weeks ago ?? I hope you have done a reformat & reinstall since this sysinfo was run... in which case this file doesn't describe your current system at all.
Once more, do your self a favour and don't even try to boot into XP before you get the system booted full speed from a DOS disk. If your current XP install doesn't work then you should try a barebone XP installation from scratch with the bare minimum of hardware connected. No extra cards, no printers, nothing extra.
H.
4.) This is a FRESH INSTALL of Windows XP. Meaning I already DID format and fdisk my hard drive.
OK, I took alook at your sysinfo file out of curiosity, altough I've already stated that you should leave Windoze out of the loop before you know your hardware is OK.
Your sysinfo says you have a floppy drive, and on a fresh install of XP you have TweakUI, Nero, Real Player etc etc installed ? You also seem to have plenty of programs loading with Windows. Just outta curiosity, how come your sysinfo is identifying your CPU correctly "Family 6 Model 4 Stepping 4" and saying it is running at the correct speed "AuthenticAMD ~1394 Mhz" and dated two weeks ago ?? I hope you have done a reformat & reinstall since this sysinfo was run... in which case this file doesn't describe your current system at all.
Once more, do your self a favour and don't even try to boot into XP before you get the system booted full speed from a DOS disk. If your current XP install doesn't work then you should try a barebone XP installation from scratch with the bare minimum of hardware connected. No extra cards, no printers, nothing extra.
H.
Quote:
Hey Admiral,
there are no Mobos or CPU's or RAM running a true 266 FSB as you describe it. They all do 133 FSB counting one upwards and one downwards on the sinus curve.
So - whats your point ?
H.
My point was that it's not actually a 266Mhz bus and it really shouldn't be referred to as such much like you shouldn't refer to an AMD Athlon XP 1800+ as being an 1800Mhz processor.
Hey Admiral,
there are no Mobos or CPU's or RAM running a true 266 FSB as you describe it. They all do 133 FSB counting one upwards and one downwards on the sinus curve.
So - whats your point ?
H.
My point was that it's not actually a 266Mhz bus and it really shouldn't be referred to as such much like you shouldn't refer to an AMD Athlon XP 1800+ as being an 1800Mhz processor.
Yes, you are right - but not all of the world is listening.
The marketing guys in the DDR dept just love the 266 stuff.
H.
The marketing guys in the DDR dept just love the 266 stuff.
H.
