Blue Screen of Death

edited February 2004 in Hardware
not to long ago i built my friend a computer the specs are as follows

asus a7v8x
amd1800+
ocz 256
16 gig hd

the other day he asked me to look at it saying that when he turned it on it gave a blue screen-when i turned it on it did also.

i looked at and immediatly thought of his hd

it gave the error of "kernal_data_inpage_error"


need some help on this one

Comments

  • a2jfreaka2jfreak Houston, TX Member
    edited February 2004
    As Prime would say: memtest86. I believe the site is www.memtest86.org or www.memtest86.com
  • edited February 2004
    is that the only solution?
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited February 2004
    Well try it and tell us if it worked.
  • edited February 2004
    does this require that you have to install it on the computer that you test it on? cause of so i cant- as soon as you boot up itll go into window and start loading the programs and just go blue- not to mention you cant even see the start menu just the backround
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited February 2004
    The key is the inpage part. The Windows Kernel grabs a "page" of workspace in RAM to live in. If it can't establish itself, it gives that error. RAM or OCing ratios not consistent between CPU and RAM are the most likely culprits, yes. While HD could be corrupt with kernel modules not stored right anymore, CHKDSK can check those basics that would affect that (scandisk doing physical media checks as best as it can is used for older Windows). A computer worm can also do this, but I would start with RAM, then run CHKDSK or scandisk (older Windows only), and eliminate hardware first. Then, if both check good, would scan for viruses.

    ADDED: To answer the "must memtest86 be installed?" part: No, memtest86 will run by itself from a CD boot, if you can burn an ISO of Memtest86 to CD and then boot from CD. You are in essence doing a CD image copy here to burn, you do not burn it as a data CD. It can also be run from a floppy boot if you get the floppy archive.


    John D.
  • edited February 2004
    as usual thanks for the help. im glad theres a place i can go to for questions and not feel belittled. this site owns! :rockon:
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited February 2004
    Just to add to Ageek's answer: it can be run from a bootable floppy, too. The test might take a while to run.

    If you have more than one stick of ram in the computer you could try using just one at a time to see if you can isolate the problem.
  • DexterDexter Vancouver, BC Canada
    edited February 2004
    Kernel errors usually come with a bunch more information on the blue screen. Does yours? If so, please give us everything it says, that helps to track down the source of the error. Often it will reference some DLL files, which giva an indication of what processes were active at the time.

    Also, are you able to boot into safe mode or VGA mode? Keep tapping the F8 key at startup and see if you get the boot options menu.

    Dexter...
  • edited February 2004
    at the bottom it gave a whole bunch of numbers, before i do the memtest ill try to boot up in safe mode.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited February 2004
    Dexter wrote:
    Kernel errors usually come with a bunch more information on the blue screen. Does yours?...
    Great idea, Dexter!

    This page will explain what the other mumbo-jumbo means.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited February 2004
    Too complicated! It's a memory problem.

    www.memtest.org

    download the thing, put it on a floppy, boot off the floppy. Voila - you will find memory errors. You have a bad stick of memory.
  • edited February 2004
    ok-BEFORE i ran the memtest i ran windows in safemode and vga mode- both worked. then i went to regular worked fine as well.but im still running the memtest.
  • hypermoodhypermood Smyrna, GA New
    edited February 2004
    Run memtest as this could be a memory related problem, but typically a Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR is disk or controller related. The second parameter in the STOP message will tell you what the kernel was trying to do when at the point of failure. Here are some of the codes out of MSDN in case this happens again and memtest comes out fine.
    * 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
    * 0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.
    * 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
    * 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
    * 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.
  • edited February 2004
    well i ran the test for 7 straight hours- no errors. lol maybe it just needs to be reformatted lol
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited February 2004
    It could be that by booting into safe mode it bypassed a driver causing a hardware problem, allowing Windows to figure it out.

    Is it safe to assume that it is running ok now? If so, this is a golden opportunity to back up your data in case of a relapse. :wave:
Sign In or Register to comment.