theBlackman on 16/4/2009 at 23:08
I finally got the new MOBO to react properly, but I have a problem that is new to me. In the 38 years of installing operating systems and building my own rigs, I've never run into this and don't know how to "fix" it.
When installing my Operating system on a reformatted HDD, the install freezes and goes to blue error screen with the message "Page_Fault_In_Non_Paged_Area"
I'm going to try to reformat the drive, and ensure that it is set with NO PAGE file, and see if that works. I needed to reformat it on a USB external drive and on a system other than the one I am rebuilding.
Meanwhile, any suggestions from our resident experts would be gratefully received.
bikerdude on 16/4/2009 at 23:13
Quote Posted by theBlackman
install freezes and goes to blue error screen with the message "Page_Fault_In_Non_Paged_Area"
Thats the old classic IDE/SATA driver BSOD, windows dosent recognise the controller that the hard drive is connected to etc.
What you need to do is do the 'F6' driver install when installing windows for the 1st time. What's the exact make and model of the motherboard so I can get the correct driver download link 4 u.
theBlackman on 16/4/2009 at 23:22
Quote Posted by Bikerdude
Thats the old classic IDE/SATA driver BSOD, windows dosent recognise the controller that the hard drive is connected to etc.
What you need to do is do the 'F6' driver install when installing windows for the 1st time. What's the exact make and model of the motherboard so I can get the correct driver download link 4 u.
Did that. I have the F6, and used it, and the Drivers to load when asked. The system accepts them and then does the BSOD. I'll make new copies and see if that helps.
I really appreciate the information. Possible driver conflict did not occur to me. I have the install disk (new) for the MOBO and will make new copies of the two drivers (a SATA/PATA from VIA, and one from ALI) the system has 4 IDE channels and 4 SATA channels, with a possible 11 HDD available.
I'll let you know what happens.
Thanks again.
bikerdude on 17/4/2009 at 09:19
Quote Posted by theBlackman
Did that. The system accepts them and then does the BSOD. Will make new copies of the two drivers (a SATA/PATA from VIA, and one from ALI)
I have a used the F6 method on a via based mobo and its ben fine, so its possible the copy of the drivers you have maybe corrupt (ive had that happen on me)
you didnt give me the model and make of your mobo btw, also whats the configuration - how have you got the hard drive plugged in and what what port.
Also can i assume the harddrive is in good cond and hasent got a bad sector etc - as this would also produce a bsod.
theBlackman on 17/4/2009 at 17:33
MOBO is a Soyo Dragon 2 Ver. 2.0 KT880. HDD is clean no bad sectors, in IDE 1 as Primary.
All HDD were been individually checked and scanned prior to installation. (5 for a total of 1.5 Tbytes).
All RAM has been burned in for 4 to 6 hours with a cycling 6 stage RAM test.
I solved the NTLDR problem.
I think you are right about the Corrupt driver(s). I am burning two new ones and will try again.
Your input is always appreciated, and your knowledge respected.
Thanks.
bikerdude on 17/4/2009 at 18:51
no prob, let us know what fixed it etc.
theBlackman on 20/4/2009 at 08:01
Up and running. I had a corrupt added driver file, and needed to install only two instead of the three I thought I needed. The corrupt driver file, and the "extra" driver were the problem.
So far so good. I'm having a little trouble with my Vcard installation, but that's purely mechanical I think.
Thanks for the help.
Dusty
bikerdude on 20/4/2009 at 09:43
Quote Posted by theBlackman
So far so good. I'm having a little trouble with my Vcard installation, but that's purely mechanical I think.Thanks for the help.Dusty
In what way..?
theBlackman on 20/4/2009 at 20:56
Quote Posted by Bikerdude
In what way..?
If the question is about "what help", then your comments on NTLDR and the possibility of a corrupt driver, or missing driver, definitely were helpful.
bikerdude on 20/4/2009 at 22:02
Quote Posted by theBlackman
your comments on NTLDR and the possibility of a corrupt driver, or missing driver, definitely were helpful.
I ment how are you haviong problems fitting your graphics card...