Page 1 of 1
runtime error 32 at 00903AF9
Posted: Sat Oct 07, 2006 10:08 am
by MKJ
im getting random dialogs informing me of a runtime error 32 at [some code or another].
its quite annoying and i cant seem to find any solution for it; i tried a rollback to about a month ago but to no avail.
what gives?
(winxp pro sp2)
Posted: Sat Oct 07, 2006 11:13 am
by ek
whats the code, google it.
Posted: Sat Oct 07, 2006 11:18 am
by MKJ
tried that, get nothing. tried googling runtime error 32 and i get a bunch of german & taiwanese forums as well as regcleaner advertisements :/
Posted: Sat Oct 07, 2006 12:26 pm
by DiscoDave
Is there anything you do that provokes this error message to pop up? or is it completly random.
If i got that error message my first instinct would be to run memtest+.
Posted: Sat Oct 07, 2006 1:52 pm
by MKJ
totally random. i can let the machine idle for a few hours and thre will be about 5 of them waiting for me to click away.
Posted: Sat Oct 07, 2006 2:22 pm
by DiscoDave
I'd say memtest first, and if that reports nothing unusual do a windows re-install. If it still happens after a windows re-install you can assume its a hardware problem.
Posted: Sat Oct 07, 2006 3:30 pm
by MKJ
im due for a reinstall anyways, so i'll try that first. not now though, about the worst timing ever, but pretty soon i will.
am i to understand that if the memtest fails it means one of my banks is fried?
Posted: Sat Oct 07, 2006 6:04 pm
by DiscoDave
Depends on the nature of the error I think. I had memtest errors once and I fixed them by increasing the voltage to my RAM, but that was a weird one....
Posted: Sat Oct 07, 2006 6:20 pm
by zolborg
DiscoDave wrote:I'd say memtest first, and if that reports nothing unusual do a windows re-install. If it still happens after a windows re-install you can assume its a hardware problem.
??????????I wouldn't jump into a re-install over this at the drop of a hat. Not likely RAM either, but you never know.
If you need a reinstall anyway, go for it, but it's a last resort, not a first.
Posted: Sat Oct 07, 2006 7:08 pm
by MKJ
zolborg wrote:DiscoDave wrote:I'd say memtest first, and if that reports nothing unusual do a windows re-install. If it still happens after a windows re-install you can assume its a hardware problem.
??????????I wouldn't jump into a re-install over this at the drop of a hat. Not likely RAM either, but you never know.
If you need a reinstall anyway, go for it, but it's a last resort, not a first.
anu other suggestions are welcomed
