What is the most common reason for bluescreens when OS rise?

Hi, Tried everything on my T-140p vaio, and couldn't figure out what might be the reason why the XP stops with bluescreen after the XP logo starts.
Replaced almost every piece of hardware - this includes Motherboard, Disk, Power sub-board. Someone asked what the bluescreen says - but I can't hold the screen to see it. The system fails also on safe mode, after showing some dos lines. and reboots itself time after time. I wonder if there is a simple obvious reason for bluescreens OS. there is no blue screen on bios or OS starting optins. only when the XP starts.
Thanks

 

Did you replace the RAM as well? Generally, a lot of these issues are related to bad RAM. Try running some tests like Everest to see

@

 

Generally BSOD are caused by driver issues...
So maybe it may be an idea to reinstal - and make sure drivers are "good".

 

DetlevCM is right. The vast majority of BSOD are caused by bad or corrupted drivers.

When you say you replaced everything what exactly do you mean?

I would also take ajaffarali suggestion and run some tests from a bootable CD just to rule out a hardware issue 1st.

My recommendation is to do a repair install and be done with it.

 

If you post the exact message and stop code - it will say something like IRQL_NOT_LESS_OR_EQUAL_TO or KERNEL_STACK_ERROR with a STOP code that will look something like 0x0000E3 or something like that, and may also reference a specific file.

That info will tell you exactly what the problem is and will allow you to find a solution.

 

Many thanks for all the ansers. I will try to catch the blue screen from a short movie I've made. the memory seam to work OK, I also took it out, and the one that comes onboard can't be the reason - since its the same problem with the original mobo and the new mobo.. thanks

 

this is the blue screen from a movie I've made...

 

Hmmm never saw a blue screen that asked to disable AV and back-up.

 

they all say that--his computer is rebooting before he can get to the STOP error.

Do you ALWAYS blue screen, or do you occasionally get into Windows?

 

They do? All of them? Never saw one that asked me to disable AV and back-up that I recall, but then again I don't blue screen very often

 

after switching a disk, and reinstalling windows and drivers I've got lots of good reboots. always suspected something at the bottom of the case is bad wiring or bad mobo - but I couldn't figure out what. before and after replaceing the mobo - the bluescreens appears all the time - couldn't get it operate windows again. after a certain system file is coming up on safe mode - it restarts with bluescreen again. It might be a driver or unconnected peripheral which has a driver, but couldn't reconize the device. that's my suspisions. since I see the OS coming up even without the touch-panel - I have no clue if a driver such as "touch panel" can cause the system to reboot endlessly. Thanks

 

I was gonna say drivers but what you said is fine

 

Just curious...

Virus?
The request to switch off the Anti virus is extremely suspect.

Can you remove the HDD, put it in an exclosure, scan for Viruses from another computer, also run chdsk etc. ?

 

That error message is incomplete as well, its missing the ending.

Could be overheating or memory failure. Something is shutting the CPU down or stopping it from completing the error message.

 

You could try running a live linux cd, that may help narrow down the problem to software or hardware.

 

A Linux live CD will only narrow down the problem if it is hardware.

If it is software - speak driver - then a Linux live CD wont help.

 

That was my first thought.

 

Few options.. I've seen this, and had different results...

First, it could definitely be a program or AV software. Daemon tools has actually hit myself with this error, and at work a test machine running a certain AV app did this as well.

You can download Bart's PE Builder (free) from http://www.nu2.nu/pebuilder/ and create a bootable CD. Boot your computer with this CD, open a Command Prompt window and run:

CHKDSK C: /F

Also look at the root directory of drive C: and make sure the file ntdetect.com is present. If not copy it from the \i386 folder on the
hard drive.

Also, you could try a repair install:

http://www.michaelstevenstech.com/XPrepairinstall.htm

You can try ultimatebootcd to see if it'll boot your system:
http://www.ultimatebootcd.com/

Lemme know how it goes.

 

I've replaced the MOBO and also With/Without the memory upgrade, - same error from 2 disks which XP installed and ran well. maybe a virus - but both of them shoudl be infected (the disks are differnt) - maybe its some hardware missing - or the power is insufficient (DC power - although changed the unit - might not supply enought current to run the OS? or to run the DISK itself?

 

OK, it took me three days, but I finally blue screened a computer...I was incorrect. They don't all say that. For some reason, I thought there was a reference to antivirus in the section on newly installed software, but there is not.

I know I'd seen it before though and I think--THINK--I may have found the issue.

First off, you say you replaced all these various parts...ok---let me ask you, are you trying to install Windows XP, or simply run it from an old disk where Windows was already installed?

With the amount of changes you have made, you cannot simply drop an old installation of Windows XP into the machine. When you install Windows XP, the installation is set up specifically for your hardware. If you change the hardware, unless it is very, very, close, you need to reinstall windows so the windows hardware abstraction layer is appropriate for your hardware.

Furthermore, the antivirus reference in the blue screen seems to occur only if you are using a fat32 file system (as opposed to ntfs)--which also makes me think that perhaps you are using an old OS in a basically new machine.

Any chance I'm getting close?

 

all my answers are on top in red

 

Hmm, no. I think I was grasping at straws.

The only way to test it is to swap out parts with known good parts. I had a desktop once where it turned out to be a cpu that worked most of the time, but not all of the time. This CPU worked for two years before going bad.

 

I did replaced every known part - only peripherals such as Touchpad or mouse were not replaced. Also replaced the motherboard (that's for the CPU issue) - the only thing I can think about is a Virus. do you know of a list of viruses which are designed to generate blue screens? (i.e. same effect) - Thanks

 

Sorry yer that's what I meant, run a live linux cd and if you don't blue screen then it can't be hardware, must be windows software related?

 

SInce when does Linux "blue screen"??

(I'm 99,9999999 (recuring)% (=100%) certain that Linux can crash - but I'm pretty sure its not a BSOD )

 

Not being a linux user I don't know, I was just giving a suggestion to try and help narrow down the problem, as it looks by the posts it could be either hardware or software.

 

I'm quite sure its software related - since I don't get bluescreen when the black screen with "start windows normally" and "Safe mode" apears. I belive this means - the laptop passed the System initialization (lets say the "dos mode") and is willing to go into the os - lets say "windows safe mode". now the question is if windows doesn't recognize a certain hardware which is not the Keyboard or Video or is it a virus that prevents XP to rise. I'm suspecting a virus. Linux will not help me realize if its a virus - or will it? (or at least direct to the bad driver)?

 

you replaced the motherboard, but did you replace the actual CPU -- the little chip that plugs into the motherboard. (I only am clarifying because too many people think the CPU is the entire box and I want to be clear.)

I had this old AMD box that would crash constantly and we could never figure out why until I had an extra CPU. I swapped the chips and it never crashed again.

 

If it is a virus you can search for it from Linux....

But I don't think its one if you replaced every component etc. also unlikely tha safe mode would work if it were a virus.

 

Correct linux wont bsod. But it will crash back to a command line with error codes.

Similar thing tbh.

 

This thread is like "What do women want "