Member Panel

I managed to delete the partition and when I left for work it WAS loading windows. I'll see if it took when I get home in the morning.

Thanks,
Sean

Well, got home from work this morning and it was frozen at 5%......Could not get a response from it with anything I tried. So, silly me hit the reset button............Black screen, that's it, that's all I get now. Nothing, no signs of life whatsoever.

Now what?

Thanks,
Sean

The saga continues......

I pulled my HD out and tried to reformat/repartition it using a friends computer to do this. Repartitioned just fine (used the wizard). got to about 2% of the reformat ans I get the following on a blue screen:

Kernel_data_inpage_error

Tech info:

*** stop: 0x0000007a (0xe18a5dac, 0xc0000185, 0xbf931aa5, 0x47859860)

*** Win32k.sys-address BF931aa5 base at bf800000, Datestamp 3b7de698

beginning dump of physical memory.........

ummm, looks like greek to me. Right now I'm open to any and all suggestions. The shotgun and the target range are looking better and better.

hey manders01

for your error message i googled it and here are the results


Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.
Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:

• 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.

Possible Resolutions:

• Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.
• Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.
  Important
  • You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:
  • Press F6 if you need to install a third party SCSI or RAID driver.
  • Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this list.

genie3251

Hi manders, it may very well be your hard drive.

I'd suggest plugging it into the healthy computer, and running a check disk on it...this could tell you if there is a porlbme with the hard drive or not.

After you've partitioned the hard drive in the healthy computer, are you able to install windows on it now? (in your unhealthy one).

On a side note...they want you to run Memtest because they don't want to admit there is a problem with their products.

Memtest runs off either CD or FDD, so you don't need a windows install to be able to run it.

Memtest86 - Memory Diagnostic Page

Hi GaRHaR,

After partitioning my HD in the healthy computer, I put it back in the sick on and still get nothing but the black screen. No letters, no numbers, nothing. Just black.

Can I get a "play-by-play" on how I can run the memtest from the healthy computer?

When I get home in the morning, I'll plug it back into the good computer and run the chkdsk from there. That I do know how to do...lol

Thanks,
Sean