• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Does anyone know what this error means plz see post

D

DOOPYLOOPY

Senior member
Setupapi.dll

X Assertion Failure at line 403 in file
D:\nt\private\windows\setup\setupapi\diutil.c: pDeviceInfoSet->DeviceInfoCount > 0

Call DebugBreak()?

YES NO

I picked YES.

Does anyone know what this will do to my system at all?
 
Ok like a good battleship player I'll say: "Where you trying to install something for a device and the device has some problem with it?"

Water?
 
Ok these are the circumstances leading to that message.

I had my modem turned on when i shut the computer down. Then i went to turn it off after the computer had shutdown and the computer started to turn itself back on. So i immediately hit the power off switch for 4 secs and thought nothing of it.

I think i turned it off in the middle of its memory check or something like that. Because when i next tried to turn it on it wouldn't get past checking memory...

The first time it stopped part of the way through it's count. Another time it would write out part of the "Del to enter setup, Esc to skip test" before hanging. A couple of times it went straight to the BIOS itself and said the previous poweron attempt didn't work and it advised me that i could change some frequency settings. But i couldnt' use the keyboard at all because it was unresponsive so I had to just turn it off. I tried many times to restart the machine and a couple of times it didnt' even display anything on my screen. It even went all the way through a couple of times to Windows but then it promptly had an explorer not responding error and would hang immediately after I put in my login. During one of the times it went all the way into Windows the error that i originally posted came up.
And i picked yes. I wrote the error down because it seemed really weird to me because my D drive is my CD/DVD drive and i didn't have a CD or anything in the drive at the time.

However, a couple of days ago I turned it on and it started working again fully. Or so I thought, since playing with it a lot more it seems a LOT more unstable. Different programs may crash at different times and sometimes the machine will just hang. Sometimes i have to restart it other times i can wait and it seems to reanimate itself.

It was working perfectly until i turned it off right after it had restarted and before POST i think.
WHAT IS THIS????

I'm fairly certain i've screwed the memory something shocking and the best way is to get a new 128mb dimm. Do you concur? What do you all think?

EDIT: I have now gotten new memory and the computer has still paused twice when i have been at the desktop. But then it continued on again. Also it has crashed me when i have been in Soldier of Fortune and has kicked me out of Tribes repeatedly since i put the new RAM in.

The RAM is a brand called Winword I don't recognise it. My previous brand was Hyundai which i did recognise and had a label stating it was 128mb pc133.

Because of that error that I had originally posted do you think i need to reinstall Windows or perhaps just those games?

Any help would be greatly greatly appreciated.

I find it strange that it is kicking me back to the desktop from Tribes since i put the new memory in. I think i might go back and say i want the RAM i paid for ie get another stick of Hyundai RAM.

Perhaps reinstalling to?
:frown:

water
 
should my VIA 4-1 drivers be installed?

I thought they already were?

but i just checked the Installed programs and it says nothing about them.
 
... it seems that you're a little nervous with this whole thing.

Maybe your bios got changed with your first problem. Have you checked it to see if everything is ok?

If you can't find anything wrong with your bios and the occasional crashes bother you so much then save your data and reinstall windows.

Crashes have become a way of life in Windows and unless I'm crashing more than once a day I'll not pay attention anymore.(taht's for W2k, for W98 I'd say more than three a day)

I don't know what a 4-1 drviers are, BX man here, but it sounds like a plausible thing to try.

Do the easiest stuff first. If nothing works, take the whole computer apart, put it back together, reformat the HD and reinstall the OS. Always stopping at every step to see if the last change solved the problem.

I myself hate to reinstall all my programs, so the OS is always the last thing I mess with.
 
You must log in or register to reply here.
Back
Top