"Resource conflict - allocation error" - No idea w

[kidpaprika]

Help!

I have a T23 and this morning it stopped booting. It gets past the IBM screen but then the following message appears:

"ERROR
Resource Conflict - Allocation error static node # 02

ERROR
Resource Conflict - Allocation error static node # 06

Press <F1> to Setup"

I have tried rebooting lots of times, and tried fiddling with various settings on the setup screen, but there's nothing obvious, and nothing I do seems to help.

Can anyone please help me?

[Deb Suran]

Anyone? My goddaughter's A22 now beeps twice and gives her an intermittent "Allocation error static node #02" error.

[sharpc8690]

Maybe the cmos's battery is drained or the board is bad.

[tfflivemb2]

Wow, talk about pulling up old threads.

Anyone know anything about this? I just bought a T23 with what I thought was going to be a bad board, as the result of loose PCBs.

I have the following error:
Resource Conflict - Allocation error static node # 02

[tfflivemb2]

WOO-HOO!!!

Nevermind, it was a bad CMOS battery, then I had to discharge all of the capacitors by removing both batteries, unplugging it, AND pressing the power button several times and holding it down the 10th time. Then I let it sit for a while, and then viola!!

It booted right into Windows XP!!!!

Not bad for $125:
T23 (2647-4MU)
1.133GHz
30GB HD
256MB ram
DVD drive
EDIT: Battery with only 34 cycles!!
14.1" LCD

Unfortunately, it has cracked bezel that wasn't disclosed at time of purchase on eBay, though who can complain if the system works now!!

[tom_k]

"Resource Conflict - Allocation Error static node # xx"

was bypassed by hitting [esc] :)

Background :
i got several T23 (2648-DG1) ,
one had crc error 175 , other one unknown svp .
causse my ic-prog was faulty (unknown at that time)
i couldn`t read out svp , also don`t have writing sw,
so i sent them to a friend who is capable to do that job.
One of the T23`s , (plz don`t ask which one ,crc or svp, for they`re all DG1s)
returned with mentioned error , at 1st boot showing: ... node # 00.
I found this thread + tried tfflivemb2`s way , but this only changed it to node # 07 , then to # 05 .
I also did "simply turn the computer off and back on again"
as told in: BIOS Update (Diskette) - ThinkPad 570, but no effects.
So i decided to try something else , spontaneously hitting escape ! o: ... :):):),
hope some of you can imagine my feeling .

Many Thanks to all posters , and of course the board !!!

@all :
Dont give up if it doesnt work for you , also generally ,
as this thread shows there often different ways to reach the aim !

tom_k
___
T23 98se.... 2x512MB 250Wh etc

[simple1]

allocation error #5
esc key worked for me
tp t23 type: 2647-4mu
simple1

[aechague]

Same problem in Thinkpad R32, after disconect CMOS Batt. "resource conflict #02... resource conclict --#05"
Same solution: Press ESC key
Wtf was that error?

[rkawakami]

Welcome to thinkpads.com!

I don't believe that I've ever received this error on any one of my Thinkpads. My guess would be that it has something to do with BIOS being temporarily confused. I would suggest that any time after you have removed or replaced the CMOS battery, that you go into the BIOS and perform the "Load Setup Defaults" action.

[LABIS]

Solved!
I have a R32 and a R51, i left in storage the R32 for long time, i had "Bad Checksum - CMOS Time and Date Error" and "Resource conflict allocation error".
"Resource"= Devices on the computer - "Allocation"= Ram Memory
So, in our case the Ram Memory is in a conflict with another device during startup.
Errors:
1) "Resource conflict - allocation error #"xx"
2) "Bad CMOS checksum"
3) "Check Date and time" (The computer doesn't keep the new Time and Date on the next startup,especially if you disconnect the laptop from the AC Power)

Other Symptoms :
1) When you connect the AC Power Supply to the Laptop it turns ON momentary by itself for 1-2 seconds and it turns OFF again or remain ON without to procced further
2) When you press the Power button to turn it ON it stays 1-2 seconds ON and it turns OFF again or it doesn't procced further.
(Stays ON but with a Black Screen)
3) You press more time the Power Button the second time (struggling to stay ON) and it will start to work but the Bios errors will appear.
4) Each time you see the IBM screen stay for long time on the startup means that the Laptop is checking the Memory at the backround (you can press Esc and see that) but also means that the BIOS detected a problem (the Memory Test usually will not show any problem)

Possible causes:
1) Bad CMOS Battery (The Battery is not neccesary to be empty so to make problems, i will explain details below)
2) Bad Ram Memory chip (To me happened the R51 not to work on Startup after long time storage and without reason)
3) BIOS temporary confused (Because of the bad CMOS Battery or Bad Ram Memory Chip or Both)

First Actions - Solutions:
1) I replaced the CR2032, i checked the voltage, 0.3v the old one, 3.19v the new one, "BUT" it was a second brand Battery
2) I tried other Ram Memory Chips, Temporary it worked when still connected to the AC but the Date and time error remained. When disconnected from the AC Power, all three errors appeared again.
After a lot of tries only the Date and time error remained constantly at every startup.
3) I updated the BIOS
4) I tried pressing Esc multiple times during startup ->entering BIOS ->"Discard Changes and Exit", it worked but the problems appeared again when startup with the AC Power disconnected (i use the R32 for my car Diagnostics, work with battery is mandatory)

Second Actions - Solutions:
I checked again the new CMOS Battery (CR2032, Lithium) , voltage, 3.19v again. This time i replaced it with a known Brand Battery...
As i read online even a new Battery can cause problems, YES! (Bad resistance, Bad Pulse, drain voltage on load)
* i connected the battery with a LED diode, worked fine but voltage drained to 2.65v when connected, disconnected 3.19v.
2.65v for a CR2032 means the Battery is Dead. 3.19v disconnected means the Battery is "cheating", drains under load or is a bad quality battery with Bad Pulse or Resistance and can cause issues to the CMOS.
So, ALWAYS replace with a known Brand or the Original.
After the second Battery replacement things went fine, no CMOS Checksum - Date and Time Error, no Resource Conflict.
The new Ram Memory Chips remained till the System to stabilize.

Procedure:
a) I disconnected AC Power, Laptop Battery, CMOS Battery (CMOS battery disconnection is not always neccesary but now yes)
b) I pressed the Power Button multiple times, i left it pressed for about 4-5 minutes.
c) I connected the CMOS Battery, AC Power, turned ON, BIOS-> Time and Date-> Save Settings->Restart
Worked fine, no Errors, (no Esc during startup), Windows loaded, Shut Down, installed the Laptop Battery, JOB DONE!

Result:
ALL good, i disconnected the AC Power, i left it for 20-30minutes OFF, Startup with Battery only, All Complete and in order.
I tried to put back the old Ram Memory Chips, they still work, the Laptop startup with no Errors (but i keep an eye on them to make sure that they work properly, i don't need mulfunctions during update the ECU of my Car! )

My Conclusion after all the above:
The "Bad CMOS Checksum - Date and Time Error" was normal at the first startup after the storage (CMOS Battery 0.3v) but i don't remember if the "Resource Conflict Error" appeared on the first startup or after the first Battery replacement....
The fact that the errors remained (especially the Time and Date, remained constantly) has to do with the first New bad Battery quality, that's 100% sure.
Possible the old Battery or the New Bad Quality Battery (or Both ) made the BIOS Confused and the system lost it's stability, common issue with ThinkPads when something is going on.

* Procedures a) and b) but also c) (in very special cases) usually save the day when your ThinkPad doesn't Start at all or stays on Black screen or on the Startup Screen. My R51 was COMPLETELY DEAD after storage, i disconnected the HDD, the Memory Chips, i did the above procedure a) and b) and came back to life (the problem appeared to be a damaged RAM Chip that caused the temporary Death *

I love my ThinkPads more than my newer laptops and i will keep them as i am alive, i know that you love your ThinkPad also but they have issues sometimes and we have to fix them, that's the reason of my Post, to Share.
I hope I helped, thanks for sharing

* ThinkPads never Die!