Need help with BSOD with new Asus M2N-E mobo

[Ken90630]

Any of you guys seen this code? I built a new machine today and went to install Windows. The HD formatted okay and Windows loaded fine. But when it reboots, the Windows XP screen comes up, the green progress bar thingy on the bottom does its thing, then just when the desktop would normally come up, the BSOD with that error code comes up.

I'm using a Seagate ST3808110AS serial hard drive (80GB), and it came as a bare drive with no drivers on a disk. I checked the BIOS settings for the HD and the serial controllers and everything appears to be okay. Do I need to install drivers for this serial HD, or update the BIOS or ??? Incidentally, the only drivers included with the mobo CD are for serial RAID configs -- nothing for just serial drives in non-RAID (and I'm not doing RAID).

Tearing my hair out here and would really appreciate a point in the right direction if anyone's encountered this before. TIA.

 

[John]

Look here

 

[Ken90630]

Thanks, John, but I'm not seeing what you were trying to point me to. I'm not overclocking, and I'm using Kingston RAM that was on their list as 'officially' approved for this mobo, so ....

What are you trying to tell me?

Ken

 

[John]

Please keep in mind that memtest is not the final verdict on stability. You should run it under the following circumstances.

Overclocking
New build
Adding new memory or cpu to existing system
Troubleshooting OS errors that could be tied to faulty memory

 

[btcomm1]

Ken, have you tried running memtest on the system? Have you run seagate diag tools on it?

http://www.seagate.com/support/seatools/

Also, have you tried booting the machine with just mouse, keyboard and video hooked up? If you plugged in a bunch of USB devices that could possibly be the cause.

 

[Smilin]

For an SATA drive you'll need to load drivers during setup.


A stop 7B is most commonly from a missing or bad driver start 0 (boot) driver, but can also be caused by problems with filter drivers.

Given that you are getting to the splash screen before the stop it means a boot driver is loading fine, but either crashing later, or a filter driver is loading that has problems.


Questions:
Has it ever booted right? If yes, you've likely added a filter driver that's got problems.
If no, then the inbox driver appears to be working but isn't.


Fix:
Run a repair install, but when you boot your CD to get started F6 and provide a driver.

 

[Ken90630]

Originally posted by: btcomm1
Ken, have you tried running memtest on the system? Have you run seagate diag tools on it?

http://www.seagate.com/support/seatools/

Also, have you tried booting the machine with just mouse, keyboard and video hooked up? If you plugged in a bunch of USB devices that could possibly be the cause.

Thanks, bt. No, I haven't tried memtest yet or run Seagate's diagnostic tools. I was about getting to that point.

But yeah, I have tried booting the machine with just the mouse, keyboard and video card hooked up (well, the FDD and CD ROM drives are hooked up too). But no PCI cards or USB devices are installed or connected. Actually the HD has always been hooked up too, but I think that would be necessary since the machine won't boot up with it disconnected, right?

I tried to nuke the existing Windows installation tonight to start over, but I now I get a new BSOD that says, "The problem seems to be caused by the following files: partmgr.sys"

Then it says PAGE_FAULT_IN_NONPAGED_AREA. So I'm guessing maybe I just got a bad HD outta the box? (It was a plain drive in just the wrapper from TheNerds.net.)

Incidentally, I'm running with only 1 stick of RAM installed right now (512) and I adjusted the RAM voltage in the BIOS from Auto to 1.8V, which is what Kingston specifies for these modules.

 

[Ken90630]

Originally posted by: Smilin
For an SATA drive you'll need to load drivers during setup.

A stop 7B is most commonly from a missing or bad driver start 0 (boot) driver, but can also be caused by problems with filter drivers.

Given that you are getting to the splash screen before the stop it means a boot driver is loading fine, but either crashing later, or a filter driver is loading that has problems.

Questions:
Has it ever booted right? If yes, you've likely added a filter driver that's got problems.
If no, then the inbox driver appears to be working but isn't.

Fix:
Run a repair install, but when you boot your CD to get started F6 and provide a driver.

Thanks, Smilin. Actually, everything I'm reading on Seagate's Web site says that their SATA drives don't require drivers. And I don't see any on their site to download even if I wanted to.

The machine has never really booted right. At one point or another, I always get either a BSOD or a message saying Windows didn't load properly. And now when I try to nuke the existing Windows installation and reformat, I get a new BSOD early on that says the partmgr.sys file is causing a problem. And it specifices "PAGE_FAULT_IN_NONPAGED_AREA" and everytime I try to boot from the CD and reformat, this same BSOD appears. I'm wondering if this HD was just bad outta the box (it was OEM, in just the wrapper). And the new STOP error is OxOOOOOO50.

 

[btcomm1]

Run memtest on it, and or the seagate tools and see what you come up with.