Continual Blue Screens of Death

[leggy]

Ok so I've had this problem with my lappy for a while. I'll get a bit of a pause which will be followed by a blue screen of death (of various guises). I'm convinced it is hardware related but I've been unable to find the problem. I have tried 4 different RAM replacements, 2 hard disk replacement, numerous reinstalls of OS. Still getting them though. I've attached an image of one to this post.

I was convinced it was the hard disk controller on the MB for a while as the System Event Viewer was reporting hard disk errors on any hard disk that I had installed. And hard disk replacements didn't seem to solve the issue. The only other thing that I have noticed is that some info/text on the bios setup screen is corrupt (may be bugger all).

It rarely boots up now and I'm frequently getting a 'operating system not found' error after the bios splash screen.

Any help would be greatly appreciated.

 

[Kryten]

I'd probably agree on a motherboard failure. I assume you've tried things like running memtestx86 (this will also flag up problems with the memory controller and some motherboard issues). Might be worth trying some other on-boot diagnostic software such as eurosoft PC Check.

 

[Overdriven]

I'm going to third on the motherboard agreement. First thing I would of said was change the RAM, and you did. (How much you got in it atm? as I was getting this issue at one point, just needed to be careful on how I used my machine (no killing it anymore))


PS: Give me your screen mine sucks.

 

[Kryten]

Maybe of some use, from MS :

Error Message:

KERNEL_DATA_INPAGE_ERROR

Explanation:

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

User Action:

If the I/O status is C0000185 and the paging file is on a SCSI disk, the disk cabling and SCSI termination should be checked for problems. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, manually launch the disk scanner. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. Check that all network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error. Disabling memory caching of the BIOS might also resolve it. Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at Microsoft Help and Support.

 

[leggy]

Thanks guys, appreciate the effort. Looks like I'm in the market for a new lappy

 

[Kryten]

No prob - if you can, format the drive in that one and lob it on Ebay - it continues to suprise me that people are willing to pay over £100 for fucked laptops, especially low-mid range P4's - when you can buy brand new ones for 300 quid. At least you'd get something back for it.

 

[leggy]

No prob - if you can, format the drive in that one and lob it on Ebay - it continues to suprise me that people are willing to pay over £100 for fucked laptops, especially low-mid range P4's - when you can buy brand new ones for 300 quid. At least you'd get something back for it.

I was actually thinking of doing this. Thanks.

 

[Guest]

could your bios need fixing, try and see if you can update it, the corrupt text could be because the bios is fubar, if you cba taking it apart you could reset the bios, alternatively you could just update the bios with the latest from the mobo manufacturers site. Currupt bios can missread what hardware you have, lets say for example it auto determines what type of hard drive you have, updating the bios is cheaper than a new lappy......