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

MY SYSTEM IS SCREWED!!! BSOD on startup...very strange...please help. And you say AMD doesn't have compatibility issues?

B

beer

Lifer
OK, this afternoon I came home and played UT, and after a little while it locked up. I rebooted...it prompts me at the Client for Microsoft Networks logon...then as soon as I log on, it blue screened. I rebooted. Again.

I rebooted to safe mode. It booted fine. I noticed my device manger was COMPLETELY F-CKED UP! There were 3 video cards, 2 monitors, seven or eight hard disks, three Motherboard resources, etc. etc. I thought it was strange...I wiped the ENUM key (device manager info) in HK_local_machine clean and rebooted. It booted fine. It added all my hardware...BSOD again when it rebooted. Hmmm...........

Being that I was long overdue for a reformat, I just did it. I reformatted. I installed Wni98, my drivers, installed the AGP minport version 4.71 and the AMD Bus Mastering drivers version 1.22 (I think). I know The Win98 drivers are more stable than the AMD drivers but I have a PCI Bridge that is being read as an Unknown Device, so I thought the AMD drivers would fix it. It blue screened.

But it gets weirder. If I go into the control panel and uninstall a random piece of software (I thought it was Office 2000 so I took that off), rebooted, it loaded fine. But I rebooted AGAIN and another BSOD. So I go into the control panel and remove the AMD Bus Mastering Drivers. It reboots, finds everything, then blue screens. I reboot to safe mode, go into the Device Manager, and notice that I have five disk drives being read. Let me explain how this works:

When I have the AMD Bus Mastering drivers installed, it reads:
Generic NEC Floppy Disk
Iomega Zip 100
Maxtor <insert model number here>

When I have only the Win98 IDE drivers installed, it reads:
Generic NEC floppy disk
Generic IDE Disk type 47 (the Maxtor)
Generic IDE disk type 80 (Zip drive)

I removed the Maxtor and Iomegas, since I no longer had the bus mastering drivers installed, and it booted fine. This is where I am now.

This problem is so frustrating because I cannot find what makes it not happen reliably. There is no pattern. Furthermore, it survived a reformat, which means that it is none of my application software because right now I have Eudora, AIM, IE installed, none of which load at Startup (where it would BSOD at).

It has to be a driver somewhere. But which one? I am going to reboot after i get this off to see if removing the bus mastering drivers, and the excess leftover hard drives, did the trick. However I am not too confident.

Has anyone seen this before? FYI, the exact message is:

&quot;Fatal Exception 0E at 0028:52263030....&quot;

The address is the same every time.
Please help me.
If I don't post a follow up to this in the next few minuts, it means that removing the excess drives failed to work and I gave up. I will check this message in the morning.

I am desperate.
 
BSOD on start up most probably means you overclocked too high. Try:


a) boosting voltage
b) underclocking
 
Pull everything out of your system except HD controller and video card. If you have more than one stick of memory, take it down to one stick.

Reformat, install, and add components one by one.

It's probably either your RAM or your Vortex card. They are finicky with AMD chipset boards unless you have the very latest drivers installed.
 
Had a friend have the exact same problem just TONIGHT..

Turned out to be a bad stick of RAM.

I'd check the RAM for sure.

G|T
 
Alright guys - A status update.

First of all, I have been using this RAM in this system for about 3 weeks. The problems just suddenly happened. I think I may have installed something last night but I don't remember.

Anywhoo...I'm in Win2K now. It's all working well. I am goign to install the Minport driver and pray to God that it works.

I tried disabling the Vortex sound, since I was thinking along the same lines you are. Still BSODed.

And I don't think I am overclocking too high because it won't BSOD until after I login or cancel. IF I get it, I can run CS or whatever for hours and not crash...
 
Don't go blaming AMD because you're overclocking a processor. If it was designed for 800mhz, they would have sold it at that.

Put it at stock speed, reformat, reinstall, get it all up, then slowly overclock it if you must. You're obviously screwing something up, so take baby steps to get it working.
 
IMO its probably your Aureal Vortex 2. When I had one of these I used to get BSOD's all the time and randomly. It would come up with something like AU30 vxd fatal error blah blah blah. Ditched the Vortex 2 and got a Soundblaster Live Value, now I don't get any BSOD's, the difference is like night and day 🙂
 
Should run it at default CPU speed when you reinstall OS,get the system stable first ,then worry about overclocking later.Note it`s very easy to blame Intel or AMD,my last PC I had a problem with was Intel but it was not Intels fault,software &amp; hardware problems will for now always be a part of the PC.Btw my new AMD system is as stable if not more stable then my last Intel one.
🙂
 
blackhawk2

The old option was to get the live!.. thats what i did the first time, but now a better card to get is the Turtle Beach Santa Cruz. This card is far nicer then the aging live 🙂
I have both, but i dumped the live on my sister🙂
 
&quot;IMO its probably your Aureal Vortex 2.&quot;

you probably had a bad card.. no sweat, you could replace it with another.. it happens to ALL devices..
 
I think it was the AMD Bus Mastering drivers.
I've installed everything back and it works like a charm. Only on Win2K, I didn't install the bus mastering drivers since it read my PCI Bridge right (On Win98 it reads it as an unknown device).

I did throttle back the processor to 700 to see if that was the issue. It still happened. And before that, I knew that it wasn't my overclocking since it booted into safe mode fine; it booted into Win98 fine every now and then, and there I could RC5 my heart out without it locking up. And, on top of that, it would only BSOD after I logged on or hit cancel - which means that something run at startup wasn't cooperating.

But anyhoo...win2K seems nice.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top