| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 49293 | 2004-09-15 04:08:00 | WinXP blue screen... shut down comp to protect | joe90ak (3042) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 272563 | 2004-09-15 04:08:00 | I recently installed new PSU, Western digital HD and extra stick of ram in my comp. I clean installed WinXP pro on one half of partitioned HD (40gig + 40gig) without SP1 or SP2. Loaded up all the standard programs, IE, outlook express, Office, Corel Draw HP printer and Dynalink router that i had before. I started getting getting pop up boxes 'This program needs to close...' intermittantly... mainly IE6 and outlook express but have also had it with programs like windows media player. Now i am getting the blue screen 'your computer has been shut down to protect it from damage.... try disabling bios shadowing etc...dumping memory to HD etc' most of the errors seem to be 'bad page call' or something like 'bad page pool ' I have tried reinstalling WinXP (but haven't done a reformat/install). can anyone give me suggestions what to try to fix this, I'm getting frustrated as hell. Joe |
joe90ak (3042) | ||
| 272564 | 2004-09-15 04:17:00 | I would run a memory test initially... then a test on all hard drives. Lo. |
Lohsing (219) | ||
| 272565 | 2004-09-15 04:25:00 | thanks Lo, sorry I'm not too bright even tho I managed to plug in the bits. Did do a scan of hard drive, but how do I test memory? Joe |
joe90ak (3042) | ||
| 272566 | 2004-09-15 04:31:00 | I have the impression that one reason for the XP blue screen is a Microsoft ploy to prevent what they don't like. Like if you install XP on one machine and then copy/transfer or whatever the OS files to another computer then the blue screen appears on the second computer. This is arguably justifiable by MS as long as the reason for the blue screen is pretty unambiguous and foolproof. Unfortunately it isn't and sometimes the blue screen can happen for totally unreasonable reasons. I think the "damage to computer" is a smokescreen to cover up the real reason. |
rugila (214) | ||
| 272567 | 2004-09-15 04:39:00 | yeah, i wouldn't put it past them :-) After i installed new HD etc and installing WinXP I made the 'mistake' of replacing the WPA with the old one i had copied before installing new bits. Win didn't like that and I had to obtain new key from MS auto phone service... maybe that's it and MS still thinks I'm cheating them! |
joe90ak (3042) | ||
| 272568 | 2004-09-15 04:51:00 | Test the memory with MemTest86 (www.majorgeeks.com). It comes with instructions in a Readme file but basically you put it on a floppy disk, reboot the computer with the floppy and leave the program to run for a few hours or overnight if you want to give it a really good test. | Susan B (19) | ||
| 272569 | 2004-09-15 06:35:00 | thanks Susan, I have downloaded it and will give it a go tonight Joe |
joe90ak (3042) | ||
| 272570 | 2004-09-15 09:57:00 | Maybe some essentially random (and comparatively uncommon) defects in RAM, HDD etc. can cause blue screens. I don’t know. But if you want to guarantee an XP blue screen, try the following: Get two computers, one with XP boot on its hard drive. Check both machines thoroughly and ensure there are no RAM or HDD problems with either. Then try to use the HDD with XP boot to boot the other machine, either by physically shifting that HDD between machines or by some cable or similar connection. What happens? Would you then like to try to form some conclusion as to the (most) probable cause of XP blue screens? |
rugila (214) | ||
| 272571 | 2004-09-15 11:12:00 | You cant just do that,unless the 2 machines were identical your going to get blue screens and/or HUGE issues from drivers conflicting with hardware. | metla (154) | ||
| 272572 | 2004-09-15 11:31:00 | > You cant just do that,unless the 2 machines were identical your going to get blue screens and/or HUGE issues from drivers conflicting with hardware. Yes, you can just do it. The question is whether the early part of the boot will work - whether the blue screen cuts in before you get to any stage of drivers conflictiing with hardware. And yes, certainly you are going to get blue screens. That outcome, and why, was the point of the post. |
rugila (214) | ||
| 1 2 3 | |||||