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

BSOD when I start my computer

Cyco

Diamond Member
OK, here's the deal, I formatted my drive, did a clean install of Windows Me (I know I know, but it's what I have and I can't afford 2000 or XP at this time) Now I turn my puter on, I get the following message "An exception 0E has accured at 0028:C006115D in VxD VNETBIOS(01) + 00000B8D. This was called from 0028:C023F58B in VxD VMN(0C) + 0000058B. It may be possible to continue normally. etc." My puter freezes, and I have to do a hard reset. I then get the Safe Mode selection menu, and am able to get in by using step by step confirmation and saying no to vnetbios.vxd. I've updated my Via 4in1, can't think of anything else to do. My MB is MSI K7T Turbo-R, and have a 900MHz T-Bird. Don't know if any more info is usefull. Any suggestions?
 
OK, here's the deal, I formatted my drive, did a clean install of Windows Me

did you upgrade or just reinstall?

when you formatted did you repartition?

did you fdisk/mbr at the dos prompt?i usually do this three times

did you change any hardware?

try fdisk and repartitioning

then fdisk/mbr

then reformat and load os

hope this helps

 
I had the same kind of error once when i tried to install on one of my rigs 🙁
The culprit for me was too aggressive memory timings with my memory.
I was trying to run my memory at 133mhz with the FSB set at 100mhz for my Tualatin Celeron.
Once i changed the memory to run synchronously (same mhz as CPU - 100mhz) the problem went away and i was able to complete the install without a prob.
May i recommend you try lowering the speed of your memory/memory timings.
 
I just noticed you are running a 100mhz (200 DDR) FSB TBird.
Is your memory set to run FSB+33mhz?
Are you using a Via chipset?
My chipset is the 694T Pro (MSI 6309T), and when i fill my dimm slots with 512mb ECC dimms it wont run FSB + 33 without an error like yours above.
 
yep, I know you already said it......you know how aweful ME is..........but I have to say it. 🙂

ME was without a doubt the biggest mistake MS ever made with an OS. It's horrible. Upgrading your OS when you can afford to do it, will say "bye-bye" to 99.9% of your current problems.

Since it's a new install it can't be your network settings or NIC, so I would agree that's it may be your memory timings.....or just ME. 🙂
 
Hehe, another ME fan 😀
In MS's defence though 😉, I have a friend i set ME up for over a year ago and he swears its been the most reliable OS he's ever used, even moreso than NT4 he uses at work! :/ hmmm?
He must have had that install going for nigh on 18 months i guess without issue - though he aint a twiddler like me, so that may have something to do with it? 😀
Im gueesing its a luck of the draw thing with ME with regards to hardware/driver compatibilty stability kinda thing maybe?
 
Just a thought, incase im a dumbass 😀

What PCI slot is your NIC in?
Have you tried popping in slot 2 or 3 incase it doesnt like to share its IRQ/Interrupt?
 
Hey guys, thanks for all your suggestions! I went off line for awhile while I thought things out and checked on a few items. It turns out that my drivers for my soundcard needed to be reinstalled (Santa Cruz Turtle Beach) Dunno if it was coincidence or what. Guess computers (especially with Me- the OS) are weird like that. Once again, thanks!
 
did you fdisk/mbr at the dos prompt?i usually do this three times

I have rarely found this to be necessary. With that aside, I fail to see the need to re-write it 3 times, does your drive not listen?

 
Back
Top