If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Problem with XP 1700 @ XP 2400 - Documented
Solved this problem finally
Before infinite loop my setup was; Athlon XP 1700 o/c XP 2000 @ 133mhz fsb Crucial 256MB PC2100 MICRON 256MB PC2100 MSI Geforce 4 Ti4200 8X ABIT AT7 MAX KT333 In the ever increasing desire to o/c further I decided to sell both the PC2100 and buy a stick of 512MB PC2700 as I knew the system was not stable running at 166mhz fsb (XP 2400 oc) and thought it becuase of the RAM not being rated for 166fsb. When I got the PC2700 I immediately started running it at 166mhz FSB but it was still not stable I thought at the higher speeds my CPU wasn`t being cooled enough (my cooler wasnt rated for XP 2400) and bought a Thermaltake Heatsink/Fan to replace the cheap coolermaster I was running - I was pretty sure this would give me the stability at 166fsb 2ghz while I was waiting for it to arrive I decided to push up the fsb to see what the max fsb the PC2700 RAM would POST at - I got it up to 185fsb and it POSTED a couple of times then it could no more - mysterious I thought. So I gave up on the high fsb and went back to 133mhz fsb and XP 2000 but I started getting spontaneous reboots did some reading on google and ended up restoring my software build from backup the spontaneous reboots were gone no permanent damage or so I thought. The CPU Cooler arrived next day and I was still unable to get stability at 166fsb and now I started noticing the infinite loop error but as I`d not had stability at 166fsb before I figured it was just the same stability problem I`d always had only at 166fsb. However when I went back down to 133fsb and XP 2000 the infinite loop persisted I started to get worried maybe it was the CPU I went back down to default clock XP 1700 and still I had the infinite loop problem. Now my system was not stable at any CPU / FSB clock! Then I read about the infinite loop problem on here and other places and thought what if I`d damaged my PSU somehow during my attempts at high fsb overclock as I seemed to recall getting more problems since then - spontaneous reboots which I got rid off but then the infinite loop seemed to arrive back then. I replaced the Q-TEC 550W with a brand new Q-TEC 400W as I knew I`d originally had stability with the Q-TEC 550W in the system when it was new so I still had faith in the brand and figured I had damaged it somehow. Well the 400W made no difference and I still had the infinite loop. So then I went on a long journey of discovery involving days/weeks of testing with fresh builds and Prime 95 untill finally I swapped the memory with a stick of PC2100 in my other PC and the infinite loop was gone. Then it dawned on me that I had damaged the memory by running at 185mhz fsb not the PSU. I sent the PC2700 ram back for replacement and and am now running a stable XP 2000 system - its still unstable at 166fsb but I don`t have the infinite loop anymore. So for me it was faulty memory they`re are other types of memory problems which are also becuase of faulty memory that I`ll agree but the infinite loop it one of them IMO. These other memory problems are similar in that they are both intermittent thats what makes them so difficult to solve. See my post on google groups http://tinyurl.com/w3t0 Therefore I believe if you have infinite loop its becuase either your memory is faulty or misconfigured - my memory was faulty plain and simple the recommended configuration for avoiding infinite loop is CPU @ 133fsb Memory @ 133fsb and CPU @ 166fsb Memory @ 166fsb - I had the recommended configuration and I had infinite loop - untill I got rid of the memory that incidently wouldn`t even POST in my other board. *UPDATE* I mentioned in the above passage that I had no stability at 166fsb and that the stability problems were not to do with the infinite loop - well tonight I went back and tried 166fsb again and the error @ 166fsb is the infinite loop - however my system is totally stable at 133fsb with no inifinite loop. Way way back however I did have a stable XP 1700 @ XP 2400 at 166fsb on this system then I decided to re-install and thats when all my stability problems at 166fsb started. Now the interesting part - when I re-installed the system when it was stable 166fsb I did so to restore a backup image of XP this backup image was installed with the APIC mode enabled in the BIOS therefore I was unable to set it to disable because XP would not load so I left it enabled - if you see my post from nlel1975 of a few months back you can see the problems I had with BIOS settings - I reckon a lot of these problems were becuase I had APIC enabled. I have tonight taken the plunge and re-installed XP with APIC disabled while I have lost my 2 year old XP install my system is now stable again at 166fsb no infinite loop! So infinite loop is caused by; APIC mode enabled at 166fsb Bad/Faulty RAM at any fsb CPU / Memory out of fsb sync Check your system for stability with Prime 95 http://www.mersenne.org/freesoft.htm This applies to this this issue; Event ID 108 The driver nv4disp.dll for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates. Keywords: Monitor into standby |
#2
|
|||
|
|||
What a load of repeatedly posted guff Nick, what were you thinking?
SB |
#3
|
|||
|
|||
|
#4
|
|||
|
|||
"Nick Le Lievre" wrote in message ... "Sir Basil" sir.basilYOUR HEAD FROM YOUR wrote in message ... What a load of repeatedly posted guff Nick, what were you thinking? SB Just to put the record straight the google record that is. Never would of thought APIC mode would cause so many headaches. Nick, What program do you use to restore a backup image of XP? I once o/c'd too high and XP wouldn't boot, even though the system posted ok. Thanks, Grady ------------ AMD 2400+ cpu@2145mhz (13x 165) ASUS A7V8X KT-400 1x Corsair 512 XMS3500 @343mz, 2.5-3-3-6 WD120OJB Xaser-II case 5x Coolermaster 80mm case fan SLK-800 w/80mm Coolermaster hsf Antec 550w Radeon 9700pro Win XP Home |
#5
|
|||
|
|||
On Fri, 28 Nov 2003 22:01:07 -0500, "Grady"
wrote: "Nick Le Lievre" wrote in message ... "Sir Basil" sir.basilYOUR HEAD FROM YOUR wrote in message ... What a load of repeatedly posted guff Nick, what were you thinking? SB Just to put the record straight the google record that is. Never would of thought APIC mode would cause so many headaches. Nick, What program do you use to restore a backup image of XP? I once o/c'd too high and XP wouldn't boot, even though the system posted ok. Thanks, Grady ------------ AMD 2400+ cpu@2145mhz (13x 165) ASUS A7V8X KT-400 1x Corsair 512 XMS3500 @343mz, 2.5-3-3-6 WD120OJB Xaser-II case 5x Coolermaster 80mm case fan SLK-800 w/80mm Coolermaster hsf Antec 550w Radeon 9700pro Win XP Home |
#6
|
|||
|
|||
On Fri, 28 Nov 2003 22:01:07 -0500, "Grady"
wrote: "Nick Le Lievre" wrote in message ... "Sir Basil" sir.basilYOUR HEAD FROM YOUR wrote in message ... What a load of repeatedly posted guff Nick, what were you thinking? SB Just to put the record straight the google record that is. Never would of thought APIC mode would cause so many headaches. Nick, What program do you use to restore a backup image of XP? I once o/c'd too high and XP wouldn't boot, even though the system posted ok. Thanks, Grady ------------ AMD 2400+ cpu@2145mhz (13x 165) ASUS A7V8X KT-400 1x Corsair 512 XMS3500 @343mz, 2.5-3-3-6 WD120OJB Xaser-II case 5x Coolermaster 80mm case fan SLK-800 w/80mm Coolermaster hsf Antec 550w Radeon 9700pro Win XP Home hmm..i have been running my XP 2100 at 166x14 = 2324 mhz for months now with no problem |
#7
|
|||
|
|||
"Grady" wrote in message
... "Nick Le Lievre" wrote in message ... "Sir Basil" sir.basilYOUR HEAD FROM YOUR wrote in message ... What a load of repeatedly posted guff Nick, what were you thinking? SB Just to put the record straight the google record that is. Never would of thought APIC mode would cause so many headaches. Nick, What program do you use to restore a backup image of XP? I once o/c'd too high and XP wouldn't boot, even though the system posted ok. Thanks, Grady ------------ AMD 2400+ cpu@2145mhz (13x 165) ASUS A7V8X KT-400 1x Corsair 512 XMS3500 @343mz, 2.5-3-3-6 WD120OJB Xaser-II case 5x Coolermaster 80mm case fan SLK-800 w/80mm Coolermaster hsf Antec 550w Radeon 9700pro Win XP Home I use GHOST to image my hard drive - XP was booting its just I was gettting spontaneous reboots while the o/s was up restoring the backup and the reboots were gone but I stuggled with the device driver got stuck in infinite loop error where the monitor intermittently goes into standby during memory intensive operations in all BIOS configurations from then on - including the default CPU BIOS settings. I later discovered the memory stick was faulty and believe this damage was done at the time of the high fsb although I have no concrete proof. I had the memory replaced and had a stable system w/o infinite loop at XP 1700 o/c XP 2000 @ 133fsb (with conservative BIOS settings) for 5 months overclocking at 166fsb always resulted in infinite loop last Saturday I re-installed XP with APIC Mode disabled suspecting this was causing the infinite loop at 166fsb and have been running XP 1700 @ XP 2400 @ 166fsb stable ever since. When I first got my XP 1700 in March I was running it at XP 2400 stable (I must of had APIC disabled) then I decided to restore an old backup which required I had APIC enabled so I must of enabled it - then I must of had it enabled on all subsequent re-installs when I was trying to get stability at 166fsb again - on top of this I also had a bad stick of ram which also produced the infinite loop error under normal operating conditions. It was a nightmare. |
#8
|
|||
|
|||
"Grady" wrote in message
... "Nick Le Lievre" wrote in message ... "Sir Basil" sir.basilYOUR HEAD FROM YOUR wrote in message ... What a load of repeatedly posted guff Nick, what were you thinking? SB Just to put the record straight the google record that is. Never would of thought APIC mode would cause so many headaches. Nick, What program do you use to restore a backup image of XP? I once o/c'd too high and XP wouldn't boot, even though the system posted ok. Thanks, Grady ------------ AMD 2400+ cpu@2145mhz (13x 165) ASUS A7V8X KT-400 1x Corsair 512 XMS3500 @343mz, 2.5-3-3-6 WD120OJB Xaser-II case 5x Coolermaster 80mm case fan SLK-800 w/80mm Coolermaster hsf Antec 550w Radeon 9700pro Win XP Home I use GHOST to image my hard drive - XP was booting its just I was gettting spontaneous reboots while the o/s was up restoring the backup and the reboots were gone but I stuggled with the device driver got stuck in infinite loop error where the monitor intermittently goes into standby during memory intensive operations in all BIOS configurations from then on - including the default CPU BIOS settings. I later discovered the memory stick was faulty and believe this damage was done at the time of the high fsb although I have no concrete proof. I had the memory replaced and had a stable system w/o infinite loop at XP 1700 o/c XP 2000 @ 133fsb (with conservative BIOS settings) for 5 months overclocking at 166fsb always resulted in infinite loop last Saturday I re-installed XP with APIC Mode disabled suspecting this was causing the infinite loop at 166fsb and have been running XP 1700 @ XP 2400 @ 166fsb stable ever since. When I first got my XP 1700 in March I was running it at XP 2400 stable (I must of had APIC disabled) then I decided to restore an old backup which required I had APIC enabled so I must of enabled it - then I must of had it enabled on all subsequent re-installs when I was trying to get stability at 166fsb again - on top of this I also had a bad stick of ram which also produced the infinite loop error under normal operating conditions. It was a nightmare. |
#9
|
|||
|
|||
Tell me about it.
I got 2 brand new ram sticks to build 2 new computers, one of the sticks had random errors. Sometimes it would not boot other times it would work ok, it could prime sometimes and fail others. This system was not overclocked and was brand new, the good thing about it the other identical system was fine. I just tried the ram in it and the problem moved with the ram ;-P. "Nick Le Lievre" wrote in message ... "Grady" wrote in message ... "Nick Le Lievre" wrote in message ... "Sir Basil" sir.basilYOUR HEAD FROM YOUR wrote in message ... What a load of repeatedly posted guff Nick, what were you thinking? SB Just to put the record straight the google record that is. Never would of thought APIC mode would cause so many headaches. Nick, What program do you use to restore a backup image of XP? I once o/c'd too high and XP wouldn't boot, even though the system posted ok. Thanks, Grady ------------ AMD 2400+ cpu@2145mhz (13x 165) ASUS A7V8X KT-400 1x Corsair 512 XMS3500 @343mz, 2.5-3-3-6 WD120OJB Xaser-II case 5x Coolermaster 80mm case fan SLK-800 w/80mm Coolermaster hsf Antec 550w Radeon 9700pro Win XP Home I use GHOST to image my hard drive - XP was booting its just I was gettting spontaneous reboots while the o/s was up restoring the backup and the reboots were gone but I stuggled with the device driver got stuck in infinite loop error where the monitor intermittently goes into standby during memory intensive operations in all BIOS configurations from then on - including the default CPU BIOS settings. I later discovered the memory stick was faulty and believe this damage was done at the time of the high fsb although I have no concrete proof. I had the memory replaced and had a stable system w/o infinite loop at XP 1700 o/c XP 2000 @ 133fsb (with conservative BIOS settings) for 5 months overclocking at 166fsb always resulted in infinite loop last Saturday I re-installed XP with APIC Mode disabled suspecting this was causing the infinite loop at 166fsb and have been running XP 1700 @ XP 2400 @ 166fsb stable ever since. When I first got my XP 1700 in March I was running it at XP 2400 stable (I must of had APIC disabled) then I decided to restore an old backup which required I had APIC enabled so I must of enabled it - then I must of had it enabled on all subsequent re-installs when I was trying to get stability at 166fsb again - on top of this I also had a bad stick of ram which also produced the infinite loop error under normal operating conditions. It was a nightmare. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
This problem has baffled everyone... | Nick G | General | 46 | May 22nd 04 04:01 AM |
Infinite Loop Ti4200 & Overclocking XP 1700 | Nick Le Lievre | Overclocking AMD Processors | 1 | November 28th 03 02:55 AM |
AT7 MAX XP 1700 Thoroughbred Ti4200 PC2700 Overclocking | Nick Le Lievre | Overclocking AMD Processors | 0 | November 27th 03 06:09 PM |
XP 1700 JUIHB Overclocking BIOS AT7 Ti4200 freeze 166fsb 3d mark infinite loop | Nick Le Lievre | Overclocking AMD Processors | 0 | November 27th 03 06:08 PM |
Freezing, lock up, unresponsive problem. | James | General | 5 | September 5th 03 02:54 PM |