Orion_Blastar
asked on
Kernel_Data_Inpage_Error on MSI motherboard
My brother has a 648F Neo MSI motherboard and 2.0 Ghz P4 CPU. He had an ABit VH6-II motherboard and 1Ghz PIII CPU and we went to switch the motherboards out.
All we have is a Radion 9000 series AGP video card attached to the motherboard, no other cards.
We have a 30Gig Maxtor Hard Drive, a 24X CD-ROM, and a CDR drive.
XP Pro runs fine under the VH6-II Motherboard. Virus scan showed nothing, used NAV 2003, AVG 6.0, and The Cleaner 3.5 before upgrading. Checked the disk for errors before upgrading, no errors found.
Installed new motherboard, ran XP Pro Setup chose reinstall. Got the Kernel_Data_Inpage_Error blue screen. Tried Install with deletion of the windows directory, same result.
Screen blacks out for a while in the "Installing Drivers" part before the blue screen.
Error message is as follows:
KERNEL_DATA_INPAGE_ERROR
Stop 0X0000007A (0XE113BC9C 0XC0000098 0XBF8ED7DD 0X3DDFD860)
WIN32K.SYS Address BF8ED7DD base at BF800000 Datestamp 367de698
Memory used is Coursar DDR RAM.
Any ideas what could be wrong? I'd like to get his Windows XP up and running and avoid this junk. This is the second MSI motherboard that we got that caused this error, last time they RMAed the motherboard and sent us a new one, calling the last one defective. What are the odds of getting two defective motherboards in a row?
All we have is a Radion 9000 series AGP video card attached to the motherboard, no other cards.
We have a 30Gig Maxtor Hard Drive, a 24X CD-ROM, and a CDR drive.
XP Pro runs fine under the VH6-II Motherboard. Virus scan showed nothing, used NAV 2003, AVG 6.0, and The Cleaner 3.5 before upgrading. Checked the disk for errors before upgrading, no errors found.
Installed new motherboard, ran XP Pro Setup chose reinstall. Got the Kernel_Data_Inpage_Error blue screen. Tried Install with deletion of the windows directory, same result.
Screen blacks out for a while in the "Installing Drivers" part before the blue screen.
Error message is as follows:
KERNEL_DATA_INPAGE_ERROR
Stop 0X0000007A (0XE113BC9C 0XC0000098 0XBF8ED7DD 0X3DDFD860)
WIN32K.SYS Address BF8ED7DD base at BF800000 Datestamp 367de698
Memory used is Coursar DDR RAM.
Any ideas what could be wrong? I'd like to get his Windows XP up and running and avoid this junk. This is the second MSI motherboard that we got that caused this error, last time they RMAed the motherboard and sent us a new one, calling the last one defective. What are the odds of getting two defective motherboards in a row?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks here is what I tried so far to correct the problem:
Used a GeForce2 AGP video card instead of the Readon 9000 Pro. Same result.
Ran Memtest86 on the RAM, it passed.
Hard drive is jumpered as Master, CD-ROM as Slave.
Flashed the BIOS to the latest version, jumpered the CMOS clear.
Got the same results after doing each one of these things.
Should I reformat the hard drive next? It seems that this is a virtual page issue caused by a bad sector, virus, or bad hardware. I can rule out viruses because I scanned the drive before switching the motherboard. I can ruloe out the memory and video card because the memory passed the Memtest86 test and the video card was replaced and got the same error.
Used a GeForce2 AGP video card instead of the Readon 9000 Pro. Same result.
Ran Memtest86 on the RAM, it passed.
Hard drive is jumpered as Master, CD-ROM as Slave.
Flashed the BIOS to the latest version, jumpered the CMOS clear.
Got the same results after doing each one of these things.
Should I reformat the hard drive next? It seems that this is a virtual page issue caused by a bad sector, virus, or bad hardware. I can rule out viruses because I scanned the drive before switching the motherboard. I can ruloe out the memory and video card because the memory passed the Memtest86 test and the video card was replaced and got the same error.
ASKER
Found the problem, overlooked the CDR drive. It was set to Slave on its own IDE channel with no Master. Changed to Master, problem went away.
Sunray