Error code 0001 when trying to start SFP

steffensen · Post by **steffensen** » Sat Nov 11, 2006 5:41 am

Does anyone know what code 0001 means?
All of the sudden one day, i got this error when trying to start up SFP, wich means it wont start.
When i try to re-install SFP, nothing happens after clicking the setup.exe.
Rebooting doesnt make any change, reinstalling XP doesnt either.
It all worked just fine just a couple of days ago, and i havent changed anything in my system since.

Im gonna take the cards out and clean the contacts, but if that doesnt work, im not sure what to do! Can it be one of my cards all of the sudden went broken?

Help--

steffensen · Post by **steffensen** » Sat Nov 11, 2006 7:39 am

Update:
I took out the cards and cleaned the contacts- no difference.
I switched PCI slots- no difference.
I tried one card at a time, on different PCI slots- no difference.

This is out of my understanding now.

Mr Arkadin · Post by **Mr Arkadin** » Sat Nov 11, 2006 8:44 am

i think i had this problem years ago (sorry, memory's a bit hazy) and i ended up having to send it back to CW for repair (i think they just exchanged it in the end at no charge - and it was out of warranty, nice chaps). i think they tend to charge nowadays.

steffensen · Post by **steffensen** » Sat Nov 11, 2006 9:13 am

I see. Its strange if both my cards went broken at the same time tho.
And actually, sometimes, SFP works. Not often, but after a few hunderds tries or so..

I have my doubts about my mobo, i wonder if it can cause this behaviour.

Gonna mail Ralf later on.. hopefully he have some clue bout this.

Mr Arkadin · Post by **Mr Arkadin** » Sat Nov 11, 2006 9:20 am

To be honest it was an age ago, and i'm not sure if it wasn't in fact an Error 000. And yes, if you've tested both cards independently then i would say the odds are against both of them dying at the same time (unless they had a nasty voltage shoved up them or something).

astroman · Post by **astroman** » Sat Nov 11, 2006 9:22 am

did you reset your PC completely ?
e.g. disconnect (!) the powercord from the wall outlet, switch the PSU on and off and wait a couple of minutes ?
Mr. A is probably right with his guess that 0001 means 'hardware error', but the procedure above is worth a try - it has mysteriously worked in countless cases

the background is that a PSU is never completely switched off as long as connected to a poweroutlet, and there's a huge number of buffering capacitors in the PSU and on the mobo which keep some chip's (messed) state even beyond standard reset procedures.

good luck, Tom

astroman · Post by **astroman** » Sat Nov 11, 2006 9:30 am

steffensen wrote:...
I have my doubts about my mobo, i wonder if it can cause this behaviour...

in that case inspect the capacitors, the round things 0.25" diameter and 0.5" height (roughly), mounted vertically.
they usually have a metallic surface with something that looks like an engraved cross on top - is any such surface bulky and not plane ?
if yes, these things can mess up quite something - and produce the most irritating error messages, MSI was once (in)famous for a series of mobos using a damaged charge of these parts.

cheers, Tom

steffensen · Post by **steffensen** » Sat Nov 11, 2006 11:22 am

I have switched the PSU off, but never took out the cord. Will try that!
So 0001 means hardware related, i see, good to know. Now i at least have some clue...
Imo, its either the mobo or the cards, and as said, both cards dying on me at the same time sounds a bit strange, as i havent had any electricity spikes or anything like that.

One other strange thing that happens after the PC have been shut down for more than 1 minut or so, is that it takes a long time (sometimes not at all actually..) til' the computer finds my boot disk.
Considering that the disk is brand new, this also makes me think of the mobo.

Im gonna check my mobo after those capacitors Tom, thanks for the tip.
Ill get back when ive checked them.

katano · Post by **katano** » Sat Nov 11, 2006 6:59 pm

could also be a faulty ram...

steffensen · Post by **steffensen** » Sun Nov 12, 2006 4:22 am

RAM? I would never have guessed such a thing..

I tried resetting my comp now, and i got new error messages, as well as the old ones (above^).

Here are some jpg's of the new ones.

Worth to mention, is that i for a few hours managed to get SFP started last night. But it only took a few hours til it went down again.

spacef · Post by **spacef** » Sun Nov 12, 2006 6:03 am

the messages in the above post appear normally when you try to start SFP while SFP is already running.
I have this regularily when i start DP forgetting to switch sfp off.

What you have is probably different, but it is worth checking if there is not a hidden sfp loaded somewhere in the pc (see in processes if scope.exe is running).

otherwise i have no idea

good luck

steffensen · Post by **steffensen** » Sun Nov 12, 2006 6:34 am

Hey spacef,
Im sorry to say its not running, but thanks for the tip!

Music Manic · Post by **Music Manic** » Sun Nov 12, 2006 8:29 am

Yes i have this on my other computer.
Simply push the card in the PCI slot and rebooted then it was recognised.
Is your computer set up as PC standard in device manager?

steffensen · Post by **steffensen** » Sun Nov 12, 2006 8:51 am

No its ACPI. Perhaps i should try Standard PC ? Been years since i used that mode..

and yes as said above, i have even switched PCI slots for my cards, also using only one card at a time, but still the same thing.

I really appreciate u guys chipping in with ideas to try out, as im really out of ideas myself. Thanks!

Music Manic · Post by **Music Manic** » Sun Nov 12, 2006 8:55 am

I had it on ACPI on another board and it only recognised 2 out of 3 cards.

astroman · Post by **astroman** » Sun Nov 12, 2006 8:55 am

if it's the Ram (good point, Katano) or the Caps, the error messages will be more or less arbitrary and make no sense. No chance to test a different mobo ?

btw I've had a couple of bad (or non-matching) Rams w. CoreDuos, you can clearly experience the superiority of the unix flavours of operating systems in such cases....

bullsh*t, it first worked a little bit and then turned into a rude way by writing it's (messed) buffers to the harddisk, like someone had scratched the surface with a screwsdriver. Re-format and Re-install applied...
Under the 'unprofessional versions' 8 and 9 of the OS these things simply couldn't happen (as it would get stuck before...)

sorry for the ot, but back to Ram: have you tried to reset access specs to bios defaults ?

cheers, Tom

steffensen · Post by **steffensen** » Sun Nov 12, 2006 10:06 am

Ill try to remove and replace some of my RAM's, i have several.
Ive got no other mobo to test with tho, would be very smooth solution.

Reset the BIOS default settings, ok, im on it.

Post by **garyb** » Sun Nov 12, 2006 12:51 pm

sounds like you may have lost a card. try each card by itself. the one that won't initialize is the bad one. contact cwa for service, sorry...

elektrolurch · Post by **elektrolurch** » Sun Nov 12, 2006 1:31 pm

@ steffensen:
3 ears ago I got the same strange messages after 4 weeks. CW changed the board and this one worked fine for 1 year. Then the same message came back (in another PC!). CW changed this board again and now is seems to be ok.
Good luck!

steffensen · Post by **steffensen** » Sun Nov 12, 2006 1:31 pm

hi gary,
as u can read above, i have done that. same error on both cards tho, wich makes it all very strange.