- Joined
- May 3, 2003
- Location
- Cleveland, GA
My brothers computer is randomly shutting down with the blue screen. He has done a 'repair' install of XP home and is continuing to get the same error message. In his words:
" Okay, guys...you got to help me out here.
About once a day, my screen goes blue with the first text relaying:
------
Windows is now shutting down to protect your computer.
------
There are some general statements as to the possible cause.... And, almost without exception, this appears:
------
Technical Information:
Stop: 0x0000008E (0xc000000S, 0xbf867726, 0xF43C3584, 0x00000000)
win32k.sys -- address BF867726 base at BF800000
Beginning dump of physical memory:...."
I've got him running det destroyer and cleaning up his graphics drivers and loading the latest for his card, a hand me down GF3 w/64m, and checking for updated drivers on his motherboard. Unfortunately, he bought a bargain system from Wintergreen and we can't seem to track down any info on the board (m925 are the only numbers we can find) or the system. He's using the onboard sound chip but can't locate updated drivers for that due to the same problem as stated above.
He has run memtest with out a hitch so it's not the actual memory. Need some suggestions as to possible causes.
Thanks.
" Okay, guys...you got to help me out here.
About once a day, my screen goes blue with the first text relaying:
------
Windows is now shutting down to protect your computer.
------
There are some general statements as to the possible cause.... And, almost without exception, this appears:
------
Technical Information:
Stop: 0x0000008E (0xc000000S, 0xbf867726, 0xF43C3584, 0x00000000)
win32k.sys -- address BF867726 base at BF800000
Beginning dump of physical memory:...."
I've got him running det destroyer and cleaning up his graphics drivers and loading the latest for his card, a hand me down GF3 w/64m, and checking for updated drivers on his motherboard. Unfortunately, he bought a bargain system from Wintergreen and we can't seem to track down any info on the board (m925 are the only numbers we can find) or the system. He's using the onboard sound chip but can't locate updated drivers for that due to the same problem as stated above.
He has run memtest with out a hitch so it's not the actual memory. Need some suggestions as to possible causes.
Thanks.