Computing.Net > Forums > Windows XP > 3D crashes XP

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

3D crashes XP

Reply to Message Icon

Name: JoseBillBR
Date: December 18, 2004 at 06:45:01 Pacific
OS: XP
CPU/Ram: Celeron 2600 / 512 MB
Comment:

My computer crashed when I was installing the last patch of World of Warcraft open beta. Since that every time I try to run a game that uses 3d I immediatly get the blue screen. I've reinstalled Direct X 9.0c and drivers for my Radeon 9200 SE several times, but it doesn't help.

Office programs, web browser etc run fine, so does Football manager 2005 which doesn't use 3d. It's probably not heat related problem because the system crashes immediatly when I try to play a game that uses 3d, and 3d worked fine before I installed that patch. Directxdiag (?) also causes the blue screen when it tries to run the 3d tests. System restore doesn't help either. I'd hate to reinstall XP, do I have any other choice?



Sponsored Link
Ads by Google

Response Number 1
Name: grasshopper
Date: December 18, 2004 at 06:58:32 Pacific
Reply:

Completely remove your video card by using the device manger. Right click My Computer and choose Properties / Hardware / Device Manager. Highlight your card and remove it. Reboot windows and let XP reinstall the drivrs. That will wipe out the patch.

When all is said and done
More is said than done..


0

Response Number 2
Name: JoseBillBR
Date: December 18, 2004 at 07:29:44 Pacific
Reply:

Unfortunately that didn't help. I also ran dxdiag again. I clicked test DirectDraw. The first two tests which don't use full screen went fine, but when the third test tried to use full screen I got the blue screen again.


0

Response Number 3
Name: cpc2000
Date: December 18, 2004 at 08:13:47 Pacific
Reply:

When Windows crashes, it writes a system event 1001 and a minidump to the folder \windows\minidump
Check system event 1001 and it has the content of the blue screen

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001. Copy the content and paste it back here


0

Response Number 4
Name: JoseBillBR
Date: December 18, 2004 at 09:06:34 Pacific
Reply:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x00000075, 0xba59fcc8, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.to.microsoft.com/fwlink/events.asp


0

Response Number 5
Name: cpc2000
Date: December 19, 2004 at 07:21:30 Pacific
Reply:

Hi Bob,
The 1st bugcheck parameter is 0x00000075
which is ntstatus code. I could not find this code and I think it is 0xC0000075. Would you confirm it is not a typo error.

If you can email the minidump, I can process the dump to find out the culprit. You can find the minidump at the \windows\minidump. Post your email address and I will reply to you. You reply back with the minidump.

Regards,
Martin


0

Related Posts

See More



Response Number 6
Name: JoseBillBR
Date: December 19, 2004 at 10:19:33 Pacific
Reply:

Yes it actually was a typo, I'm sorry!

The dialog actually said:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0x00000075, 0xba59fcc8, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Now I figured how I can copy-paste the text, so no typos this time. My email is jyri_markkanen@yahoo.com. Thanks a lot for trying to help me out!


0

Response Number 7
Name: cpc2000
Date: December 19, 2004 at 15:08:33 Pacific
Reply:

You missed the 1st bugecheck parameter and 0xc0000005 stands for access violaton. The 2nd bugcheck paramter is 0x00000075 which is the failing instruction address. I've replied to your email.



0

Response Number 8
Name: cpc2000
Date: December 19, 2004 at 15:11:40 Pacific
Reply:

Don't email the \windows\memory.dump to me which is the kernel or full memory which is very big (usally over 50MB after zip). I only want the minidump.


0

Response Number 9
Name: cpc2000
Date: December 20, 2004 at 07:16:20 Pacific
Reply:

BugCheck 1000008E, {0xc0000005, 0x000000075, 0xba59fcc8, 0x00000000}

Probably caused by : vsdatant.sys ( vsdatant+f1d6)

I believe that vsdatant.sys belongs to ZoneAlarm.

Solution
1. De-install Zone Alarm and install other firewall such as black ice or etc
2. Your XP is the base level. Update XP to SP1.


0

Response Number 10
Name: cpc2000
Date: December 21, 2004 at 09:23:12 Pacific
Reply:

Hi Bob,
I'm glad to know that after you upgrade the latest version of ZoneAlarm and your BSOD is resolved.

Martin


0

Sponsored Link
Ads by Google
Reply to Message Icon

Monitor shuts down after ... Error - Access denied for...



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows XP Forum Home


Sponsored links

Ads by Google


Results for: 3D crashes XP

3D Windows XP Screensaver Problem www.computing.net/answers/windows-xp/3d-windows-xp-screensaver-problem/113656.html

CD-RW + DVD crashes XP www.computing.net/answers/windows-xp/cdrw-dvd-crashes-xp/24589.html

TMPGEnc Crashing XP www.computing.net/answers/windows-xp/tmpgenc-crashing-xp/18950.html