Windows Blue Screen Memory Dump Help

[GerhanaZ]

Anybody know what is the problem with windows xp and memory dump,
after i played any games in few minutes my computer will goes to blue screen and memory dump,
try to change to win 2000, still the same problem, and listed that there is something wrong with myvideo card(which is radeon8500).dll file

Tnahk You in advance

 

[smp]

Is there an error code?
If you can, quickly jot it down and search microsofts knowledge base for that error code.
If you switched between OS's .. maybe your video card is bad, maybe some bad memroy on the card or something?

 

[Shamrock]

umm...I had the same problem, getting memory dump BSOD's, so I thought "Windows has always been finicky about ram slots" so i moved a stick of ram from bank 3, to bank 2 (no it was installed correctly), and poof, my ram starting zapping, and smoke rose up from the mobo, and I inhaled it, it made me sick and dizzy for about 30 minutes. It fried my CPU, Mobo, RAM, Power supply, and Vid card, I am now awaiting Fedex/UPS on new parts.

I am not saying your ram is bad, but better think about something before continuing. Just heed smp's advice...look into bad components, may be RAM, video or mobo.

 

[igiveup]

LOL Shamrock, did you turn the computer OFF first? JK...

Please write down the message displayed on your screen. If its rebooting itself and it goes by too quick then you can change it so that it stops at the blue screen. Right click on My Computer and choose properties. Choose the Advanced tab, and then under the third section "startup and recovery" click the Settings button. Uncheck Automatically Restart near the bottom.

If it is mentioning your Radeon 8500.dll or whatever then I would download a new set of drivers and install those. You might try changing some of your settings in the video card to make it less demanding on the card. ATI's website and forums would be a good place to start, they would more than likely be able to help you far better than we can. I am running a GeForce3 for example. Everybody there would be running an ATI.

 

[IcemanJer]

Originally posted by: Shamrock
my ram starting zapping, and smoke rose up from the mobo, and I inhaled it, it made me sick and dizzy for about 30 minutes.

Oh gee... getting high off fried PCB. those stuff are toxic, ya know!

 

[Shamrock]

no joke it was toxic!!!! I didnt inhale it on purpose!, I was about 6 inches from the RAM when it happened, I was checking things out, making sure nothing was touching. I saw smoke, and inhaled deeply to blow out what I thought was fire (it was electricity) and the smoke went right down my neck when I inhlaed. EEEEEEEEKKK. (This happened about 2 weeks ago) Mushkin and MSI both replaced everything no charge (got my ram in today)

 

[IcemanJer]

nice. glad to hear that they replaced your parts w/o charge!

 

[Sunner]

Sounds like a rather expensive way to get high...

 

[IcemanJer]

well, I guess you look for whatever happens to be around you that's on fire and emitting smoke...

 

[VirtualLarry]

Originally posted by: Shamrock
umm...I had the same problem, getting memory dump BSOD's, so I thought "Windows has always been finicky about ram slots" so i moved a stick of ram from bank 3, to bank 2 (no it was installed correctly), and poof, my ram starting zapping, and smoke rose up from the mobo, and I inhaled it, it made me sick and dizzy for about 30 minutes. It fried my CPU, Mobo, RAM, Power supply, and Vid card, I am now awaiting Fedex/UPS on new parts.

I am not saying your ram is bad, but better think about something before continuing. Just heed smp's advice...look into bad components, may be RAM, video or mobo.

Wow, what an experience!

PS. Next time, unplug the system before removing anything. ATX systems are still "live", even if shut down.

 

[Shamrock]

I am not stupid about this, as I build PC's all the time. I had it shutdown, turned off at the power supply, AND my surge protector was turned off. It was confirmed that I had a faulty Motherboard from MSI.

 

[wxjunkie]

I get BSOD's just when booting up a Window 2k SP3 revision....so I'm stuck with SP1 for the time being.
Must be the harddrive...