• 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.

Santa Cruz problem........

T

ToBeMe

Diamond Member
Anyone else ever get an error message when installing an Windows with a Santa Cruz? I'm receiving a very odd error message that leads to a nic problem I believe, the way it reads anyhow. Here is the error:

An exception OE has occurred at 0028:C006115D in VXD
VNET bios (01) + 00000B8D

This was called from 0028:C023 F58B in VXD VMM (oc) + 0000058B

The error, to me at least, is saying it's a network problem........funny thing is, there are no NICS installed.......in fact, there is nothing but the video card (Visiontek GF3) and the sound card (Santa Cruz). I have now tried this in several different systems while building them and always receive this error be it an AMD or Intel, Via, or Intel chipset, and Abit, Asus, & MSI boards!

Turtle Beach C/S says they have never heard of this and states they will most likely return the same card to me if I RMA it! They advise me to either ignore the error and continue installation, or, Install the O/S without the card and ignore the error when I do install the card, then reboot and all will be fine! Which is true, I can by pass the error and finish installation either way, but, every time I do it seems the system it is in is unstable and has sub-par sound quality!

Just thought I'd see if this is an isolated incident, or if others have had this problem.........
Thanx!🙂
 
Since this is a troubleshooting message, I recommend General Hardware or the Peripherals forums - not the highly Technical Forum.
 
Oh Thanx...........At least you bumped my thread! LOL!🙂

Let's see, since I've had it posted in GH I've gotten 3 PM's telling me to post it here because noboby there had any idea and it was to "Highly technical"!!!!😉😉
 
Well, I'm certainly not a moderator of the HT forum, so I could well be wrong, but at other places (Aces, Sharky's, etc.) troubleshooting - even highly technical troubleshooting - is not considered "on topic". It certainly seems to be a interesting problem though.

(in case you are reading this in the technical support forum and think that I'm confused... this was originally posted to "Highly Technical" and was moved here to "Technical Support&quot😉
 
Um ... pm, this is the Technical Support forum; you seem to think it's the Highly Technical forum, but that's a different place.

(Sorry, ToBoMe, but I've got no advice either. At least I bumped you, eh?)
 
LOL legless.......I think it's been moved!😉 PM was right.......I just don't know where to go with it!🙂 LOL!🙂🙂
 
Hmmm. Well, I guess I should have answered this earlier before I started talking about moving it around, but...

Anyway, if you have dial-up networking installed, you should be loading vnet.vxd (which I believe is the networking virtual device driver under Windows). You could try removing the entire TCP/IP stack and all networking. But the fact that this happens on multiple builds with multiple OS's and the fact that it is breaking a low-level device driver leads me to think that it's probably a defective card which is driving the wrong values onto the PCI bus. I'd RMA it.

Patrick Mahoney
IPF Microprocessor Design
Intel Corp.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top