PDA

View Full Version : Constant BOOTFAIL and POST interrupt



DarkFather
03-06-2011, 05:31 PM
I am fairly computer able. This is my 3rd PC I built myself. I have been having an issue with my PC for the past 2-3 months. I use NOD32 for antivirus.

Everything goes fine, and then out of nowhere I get a 2 second blue screen (so fast I can never read it) and then my PC reboots on it's own. After it gets to the bios screen it says there was a BOOTFAIL and I need to check the system boot list.

I try to re-start my PC up and I get a screen saying something about unable to boot hit CTRL+ALT+DEL to restart. I sometimes am able to get the upt to the Windows Start Up screen, but then the 2 second long blue screen apears and then my PC restarts.

I then sometimes get to a screen when trying to boot that A System BOOTFAIL or POST interrupt has occured. And then it tells me a system32 file is corrupt. After the second time this happened I was able to boot into safe mode but all the letters and numbers were complete gibberish. So, I removed the hard drive and installed a fresh Windows on another drive. After that I copy over the files I use and settings from my external hard drives. I usually just hook the hard drive up with external cables and grab the files I need off the previous drive so I dont loose my files and settings.

Two weeks later, it happens again. Upset, I get another brand new hard drive and install windows again getting everything back the way I like it. 1 week later, it happens again. This senerio has happened 4 times since January.

The problem I am having is that I have reformatted my PC 4 times (4th time since it just happened again today) after this happens. It runs fine for a week or month, and then it does it all over again. Something is wrong somewhere and I don't know exactly what it is. For some reason my system32 files keep getting corrupt and I get a BOOTFAIL even on a new install just a week or two later.

I have scanned my external drives (where I keep all my files) with my NOD32, but maybe it is missing some virus? What other programs would someone suggest to find this could be little virus/worm? If it is a virus, it is well hidden and doesnt want to be found. Maybe my BIOS have become infected making my BOOT continually get corrupted? Should I clone my HD after I get it set back up so I can just clone over it when it happens again? Program suggestions for an exact clone of a HD? I am getting sick of reformatting my PC over and over again. Any suggestions or help would be great.

Speedy Gonzales
03-06-2011, 05:38 PM
What do you mean by this??

After that I copy over the files I use? What files exactly? You cant install windows and copy programs that were already installed from another hdd. They wont work. You have to reinstall everything AFTER you reinstall windows (unless you clone the hdd with a program)

What version of windows is it?

DarkFather
03-06-2011, 05:49 PM
What do you mean by this??

After that I copy over the files I use? What files exactly? You cant install windows and copy programs that were already installed from another hdd. They wont work. You have to reinstall everything AFTER you reinstall windows (unless you clone the hdd with a program)

What version of windows is it?

I know that. I guess I wasnt clear on that. I only copy over my files after I install Windows and get it updated again. Files means, files I use. Such as my Fonts, theme settings, and the settings and bookmarks I have for Firefox, etc. Those kind of files. I dont copy over any Windows files. Any actuall programs I have I freshly install.

I use Win XP Pro and then upgrade to SP3.
AMD Athlon 64X2
3.5bg RAM
ASUS M2N32-SLI Deluxe MB
Nvidia Ge-Force 8800 GTS Graphics Card
3 internal HD's = 2 1TB WD GREEN drives and 1 Seagate 400GB with OS.

Snorkbox
03-06-2011, 05:52 PM
I'd be inclined to test the RAM using memtest as a first step if you have files corrupted.

Also turn off auto restart so you get a chance to get an error report before it reboots.

DarkFather
03-06-2011, 05:55 PM
I'd be inclined to test the RAM using memtest as a first step.

I was told RAM wouldnt be causing this, but it actually makes sense. I luckily have extra RAM I bought awhile back. I'll give this MEMTEST a try on the RAM I already have installed after I get things back installed again. I just need to nail this problem down, I am sick of redoing my PC every few weeks.

Auto restart off? I'll have to look up how to turn that off.

Speedy Gonzales
03-06-2011, 06:01 PM
Is AHCI enabled in the BIOS?? If it is, did you add the SATA drivers during the install? If windows is on it now and its still crashing, disable auto restart (either windows key+ pause, if you can get into windows) then advanced / bottom option. Untick auto restart. Or reboot, hold F8 down select disable auto restart

Which 64 x2 CPU is on it?? Theres a lot that this mobo supports and what BIOS is on it now?? Its up to 2205 now (non beta). The last 4 updates are beta (which I wouldnt use)

DarkFather
03-06-2011, 06:10 PM
Is AHCI enabled in the BIOS?? If it is, did you add the SATA drivers during the install? If windows is on it now and its still crashing, disable auto restart (either windows key+ pause, if you can get into windows) then advanced / bottom option. Untick auto restart. Or reboot, hold F8 down select disable auto restart

Which 64 x2 CPU is on it?? Theres a lot that this mobo supports and what BIOS is on it now?? Its up to 2205 now (non beta). The last 4 updates are beta (which I wouldnt use)

Im on the PC now. I just did a fresh install of Windows, but havent updated Windows all the way yet. It isnt craching now because I just reformatted and did a fresh install. But, as I said, the problem seems to occur a week or month later. Than I have to do it all over again.

SATA drivers should be installed with windows right?

Which 64 x2 Cpu is on it? It's the same CPU thats been on it since I built it 3 and half years ago. The same BIOS as well. Should I update the BIOS and flash them?

pctek
03-06-2011, 06:13 PM
You have eliminated HDD.
Test the RAM, if that passes, then I'd be saying motherboard. I highly doubt the BIOS would need looking at if you've had this board for ages.

DarkFather
03-06-2011, 06:15 PM
I want to make sure I get the correct Memtest. Anyone know the best one?

Snorkbox
03-06-2011, 06:18 PM
Try this one.

http://www.memtest.org/

Speedy Gonzales
03-06-2011, 06:20 PM
No, the XP cd doesnt have SATA drivers on it, unless you add them with a floppy during the install. Or slipstream them into an ISO.

I dont think AHCI is enabled in the BIOS (if this supports SATA). Otherwise, if you didnt add SATA drivers (if the hdd is SATA), you wouldnt get to the install screen. It'll crash with a 0x0000007b stop error

Whats the speed of the CPU??

DarkFather
03-06-2011, 06:34 PM
All my HD's are SATA (II I think). I do not recall ever installing drivers for them other than the Chipset drivers everytime I reformat. Ive had this PC 3 and half years, it would have been a problem long before this if it was some SATA driver issue.

About to try the memtest...

Snorkbox
03-06-2011, 06:44 PM
All my HD's are SATA (II I think). I do not recall ever installing drivers for them other than the Chipset drivers everytime I reformat. Ive had this PC 3 and half years, it would have been a problem long before this if it was some SATA driver issue.

About to try the memtest...

Let the Memtest run for several hours unless it picks up errors quickly. I usually let it run overnight so about 8 - 10 hours.

DarkFather
03-06-2011, 07:47 PM
Let the Memtest run for several hours unless it picks up errors quickly. I usually let it run overnight so about 8 - 10 hours.

I let it run until it said 100% and then Pass. Took over and hour. I should let it run all night?

Snorkbox
03-06-2011, 07:50 PM
I let it run until it said 100% and then Pass. Took over and hour. I should let it run all night?

Yes. As it does several types of test.

DarkFather
03-06-2011, 08:04 PM
Yes. As it does several types of test.

Ok, thanx for the heads up. Hopefully it's just my RAM, because if it is my MB I am screwed.

Snorkbox
03-06-2011, 08:11 PM
Ok, thanx for the heads up. Hopefully it's just my RAM, because if it is my MB I am screwed.

It also may be related to your BIOS settings but I don't believe there will be a virus in there.

DarkFather
03-06-2011, 08:21 PM
It also may be related to your BIOS settings but I don't believe there will be a virus in there.

That would be odd, because I havent touched my BIOS settings in probably 2 years. The only thing that has changed on my PC is that I have been using 4 internal HD's (one with OS) instead of 3 since January.

Snorkbox
03-06-2011, 08:27 PM
That would be odd, because I havent touched my BIOS settings in probably 2 years. The only thing that has changed on my PC is that I have been using 4 internal HD's (one with OS) instead of 3 since January.

Let's make sure of the RAM as a first step. :)

Another memory tester can be found here:-
http://hcidesign.com/memtest/

This will test unused RAM only and may be somewhat quicker.

DarkFather
03-06-2011, 10:15 PM
Well, I decided to swap out all my RAM instead, and was able to overwrite the corrupt system32 file (ntoskrnl.exe) in Recovery console using the Win XP disk. So, I am back in my PC just like it was before. I'll keep the other HD with the fresh windows install on it the way it is just encase.

I am going to see if it happens again anytime soon, and I'll post back here if it does.

Thanx for all the help folks.

Snorkbox
03-06-2011, 10:19 PM
Well, I decided to swap out all my RAM instead, and was able to overwrite the corrupt system32 file (ntoskrnl.exe) in Recovery console using the Win XP disk. So, I am back in my PC just like it was before. I'll keep the other HD with the fresh windows install on it the way it is just encase.

I am going to see if it happens again anytime soon, and I'll post back here if it does.

Thanx for all the help folks.

OK. Thanks for the update.

DarkFather
09-06-2011, 04:39 PM
Well, it happened again.

This time I was able to see the errors.

STOP: C 0000221 unknown Hard Error
\SystemRoot\System32\ntdll.dll

A Problem has been detected (etc etc)

Tech info

*** 0X000000F4 (etc etc all with zero's)

-----------------

So, I restarted my computer and then got another similar error during start-up with

STOP: 000000F4 (and then zero;s)

Beginning dump of physical memory (then it completed the memory dump and hung there)

-----------------

So, I restarted PC and tried to replace the ntdll.dll in the Recovery console, but I was unable to get to Recovery the first time trying and got another 0X00000 type error. After I tried again, I was able to get to Recovery and replace (COPY) the ntdll.dll file

Restart computer and then now there is a corrupt System32\Drivers\Ntfs.sys

I then restart and got another blue screen which informed me of

PROCESS1_INITIALAZATION_FAILED

right after the windows screen.

So, I am now on my "back-up" hard drive and really don't know what keeps causing these corrupt System32 errors even with fresh Windows installs and brand new hard drives.

One thing I do notice is this seems to happen while downloading with Utorrrent (that's what started it today) right after it starts. Almost like the hard drove or memory doesn't want to read it.

I am really at a loss of what to do now........

Speedy Gonzales
09-06-2011, 04:53 PM
1. Reinstall windows.

2. Dont install P2P programs

3. If 1 and 2 dont work / it keeps crashing, buy another hdd

Is the windows cd/dvd you're using legit?

gary67
09-06-2011, 05:16 PM
Something I haven't seen, what size, brand is your power supply? As you are running so many drives it might not be powerful enough, just a thought

DarkFather
09-06-2011, 05:17 PM
1. Reinstall windows.

2. Dont install P2P programs

3. If 1 and 2 dont work / it keeps crashing, buy another hdd

Is the windows cd/dvd you're using legit?

Iv'e reinstalled Windows freshly on 3 hard drives now, 2 of them brand new. This keeps happening eventually. If you read the previous posts you'd see.

Yes, my windows is legit. Its a official Win XP Pro SP1 disk. I update all the way to SP3 everytime I install.

Why would Utorrent cause my System32 files to keep getting corrupt? Ive been using it for years and this only started the last few months.

DarkFather
09-06-2011, 05:29 PM
Something I haven't seen, what size, brand is your power supply? As you are running so many drives it might not be powerful enough, just a thought

700w OCZ Power supply. It's only 1 yr old since my previous one died.

Iv'e only had 3 HD's in the PC the past few weeks. 1 hard drive with the OS and 2 1gb WD Green.

How would this keep causing my System32 files to be corrupt?

gary67
09-06-2011, 05:49 PM
Faulty power supplies can do all sorts of unusual things, it was just something to check but it should be more than powerful enough

Snorkbox
09-06-2011, 09:02 PM
uTorrent might be stable but after a fresh installation of Windows SP3 what else do you install that you got from a torrent site?

What apps or games are installed?

What did you install just before your WinXPSP3 died last?

sroby
09-06-2011, 09:18 PM
as previously suggested.

A new Win install (format the drive during install)
Load win updates & latest drivers.
Keep win generic as poss with NO other crap loaded, untill you sort the issue.
Dont copy across fonts etc (docs,mp3's etc should be OK)
Default the bios, are you overclocking RAM or CPU ??

Occasionly, faulty RAM wont be detected by RAM tests, the RAM fault has to be really bad to be detected that way.

wainuitech
09-06-2011, 09:31 PM
Try changing the CMOS battery as well, cheap enough.

Seen it several times where some odd ball error messages appear, or strange things happen, change the battery and the problem goes away.

While this shouldn't make any difference, is the OS drive on the correct SATA port, if you have ports 0,1,2,3,4 and the OS drive is on #2 for example and another drive on 0 or 1 that sometimes can cause strange happenings.

DarkFather
09-06-2011, 09:33 PM
uTorrent might be stable but after a fresh installation of Windows SP3 what else do you install that you got from a torrent site?

What apps or games are installed?

What did you install just before your WinXPSP3 died last?

After Win XP disk is installed I have to install the Drivers needed for my MB Chipset in order to get online for Windows Update. Then I install my NOD 32 antivirus system.

After everything is updated to SP3 and all Windows updates (I do not update to newest explorer since I dont use Explorer) I install the drivers for my M-Audio sound card.

.Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update and the 1.1 version as well

Windows Media Player 11

Then I uninstall (from Windows Components) Paint, MSN Explorer, Windows Messenger, and Outlook express since I do not use them.

then I install:

My NVidia graphics card drivers (newest ones)

AMD Dual Core optimizer

I copy over all my Fonts

Newest K-Lite Mega Codec packs

MP4 registry edit so that WMP reads MP4 files for streaming to PS3

Firefox newest version and copy over my bookmarks and settings that I have saved. Then install newest Flash and Java.

I copy over my display theme settings I have for my Windows and how it looks (no program, just the settings file).

WinRAR 4.0b2

Adobe CS5 Master Collection and Adobe Lightroom 3

newest Utorrent and copy over my files from my downloads folder

mkv2vob

Winamp PRO

Raptr

QuickTime Pro v7

I do not have any games installed the past 2 times I have had this problem and reinstalled Windows starting from scratch.

Those are generally the main things I install first. I have a few that I sometimes install such as MyScreenRecorder. But this last time I only had the ones above and MyScreenRecorder, which I just installed last night before this happened.

Remember, this is now the 5th time this has happened in the past 3 months. SO, I have it streamlined since Ive done it so much.

wainuitech
09-06-2011, 09:35 PM
Did you read post 30 -- Some other suggestions to an odd error message, the F4 is uncommon

DarkFather
09-06-2011, 09:39 PM
Try changing the CMOS battery as well, cheap enough.

Seen it several times where some odd ball error messages appear, or strange things happen, change the battery and the problem goes away.

While this shouldn't make any difference, is the OS drive on the correct SATA port, if you have ports 0,1,2,3,4 and the OS drive is on #2 for example and another drive on 0 or 1 that sometimes can cause strange happenings.

Yes, OS is in first default SATA as it always has been

How would I go about changing the CMOS battery?


as previously suggested.

A new Win install (format the drive during install)
Load win updates & latest drivers.
Keep win generic as poss with NO other crap loaded, until you sort the issue.
Dont copy across fonts etc (docs,mp3's etc should be OK)
Default the bios, are you overclocking RAM or CPU ??

Occasionly, faulty RAM wont be detected by RAM tests, the RAM fault has to be really bad to be detected that way.

If you read the list I posted that is what I install. So I cant have anything installed that I use? ugh....

No, I do not overclock anything. My BIOS haven't changed since I got everything working since I built this computer 3 and half years ago now.

I just swapped out my RAM the last time this happened, 7 days later it happened again (today)

I have a backup hard drive (which I am on now) with a minimal XP fresh install so I can copy my files off the previous OS HD so that I don't loose my files.

Speedy Gonzales
09-06-2011, 09:52 PM
Use this instead of WMP for MP4 for the PS3

http://code.google.com/p/ps3mediaserver/

DarkFather
09-06-2011, 09:57 PM
Use this instead of WMP for MP4 for the PS3

http://code.google.com/p/ps3mediaserver/

Ive tried that program, and others. It (and others) use CPU and loads movies too slow for my tastes. WMP 11 works great with minimal CPU usage and no lag/wait time. That ps3mediaserver you cant scan ahead in movies well and always has to play "catch up" when trying to watch a new movie/show. WMP 11 is instant.

wainuitech
09-06-2011, 10:13 PM
How would I go about changing the CMOS battery?
Simply locate it on the motherboard, flick the tab, it pops out, push in a new one. They are about $3-$6 depending on where you buy them (warehouse etc) take the old one with you or write down the number, normally CR2032 3V.

If you want to watch a video Found this on youtube (http://www.youtube.com/watch?v=tkBWZOtp2is&feature=related)

Just make sure you put it back in the right way up, (writing to the top face)

After its changed you have to reset all the BIOS settings again.

Cant guarantee it will fix it, but as I mentioned I've seen the CMOS battery cause "strange behavior" before.

1101
10-06-2011, 02:50 PM
If you read the list I posted that is what I install. So I cant have anything installed that I use? ugh....


ah , no.
If you are serious about tracking down the cause of these issues.
You can do all this on one of you spare hd's. It sounds like you have a few
Start with a basic , non tinkered, non crapified Win install & go from there.
Perhaps load 3Dmark & just keep running it to see if it crashes .

Are by chance loading up cracks/keygens :for Abobe, & the other "pro " versions of software you have
have you run malwarebytes(full scan, not quickscan) across the HD with all your files ?? Download TDSSKILLER from kaspersky & run it. You may have rootkits.

You can also just remove the CMOS batt( with power off). Then go into bios & correct the date & time. As long as the PC is power on the CMOS will retain its settings . This is just for testing you can put that batt back in later if you dont have a new one.

DarkFather
10-06-2011, 03:11 PM
ah , no.
If you are serious about tracking down the cause of these issues.
You can do all this on one of you spare hd's. It sounds like you have a few
Start with a basic , non tinkered, non crapified Win install & go from there.
Perhaps load 3Dmark & just keep running it to see if it crashes .

Are by chance loading up cracks/keygens :for Abobe, & the other "pro " versions of software you have
have you run malwarebytes(full scan, not quickscan) across the HD with all your files ?? Download TDSSKILLER from kaspersky & run it. You may have rootkits.

You can also just remove the CMOS batt( with power off). Then go into bios & correct the date & time. As long as the PC is power on the CMOS will retain its settings . This is just for testing you can put that batt back in later if you dont have a new one.

I am serious because there is no way I could afford to get new parts for my PC right now. I've been Unemployed for a year now and was denied Unemployment, so I've just been scrapping by. :( My PC has been my main source of entertainment except my PS3 and X360.

Yes, I have about 4 spare HD's. lol. As you probably read, I have a back-up HD with a fresh install of Win XP on it bare bones for encase this happens, or something else, that way I can just pop it in and save my files.

I have installed a fresh Win XP Pro updated to SP3 and all updates. Both .Netframework 3.5 and 1.1. My Chipset drivers, graphics card drivers, audio card drivers, Firefox with Java and Flash, and SPybot and SUPERAntispyware. I have not installed NOD 32 yet. That is all I have installed.

I was using no keygen for Adobe, just a .host file edit done by hand. My NOD 32 should have found any spyware/malware if there was one in any keygen's I had for a few other programs on the list. NOD 32 is very good, or so it seems, about finding them, it finds them when there is no virus.

Right now I am going to scan the 2 drives I keep my files/movies/pics on with a few programs. I'll try the programs you mentioned as well. My brother seems to think there is some hidden virus that no program detects that is causing the chronic problem.

As far as the battery. I will have to figure out where to buy one. I don't know if Staples would carry one, that's about the only PC friendly store around here unfortunately. Unless I get one through Amazon.

Snorkbox
10-06-2011, 03:24 PM
I feel no sorrow for those that use Keygens. Likely this is the cause of your pain!

SolMiester
10-06-2011, 04:20 PM
In my experience, and according to Microsoft, Drivers are 99% of the time responsible for BSOD, not memory...If you have memory issue, this normal appears as computer freeze\lockup......

Do you allow Windows to update your drivers for components?....

DarkFather
10-06-2011, 04:48 PM
In my experience, and according to Microsoft, Drivers are 99% of the time responsible for BSOD, not memory...If you have memory issue, this normal appears as computer freeze\lockup......

Do you allow Windows to update your drivers for components?....

Everything that needs drivers is installed from the manufactures website or disk. My graphics card, audio card, chipset, etc. Most everything I get the newest drivers when I install. Now, are you speaking of the "Optional hardware updates" in Windows update? Because I never have installed those, there are 7 of them usually. I have been told the optional ones can be wrong.

SolMiester
10-06-2011, 05:23 PM
Everything that needs drivers is installed from the manufactures website or disk. My graphics card, audio card, chipset, etc. Most everything I get the newest drivers when I install. Now, are you speaking of the "Optional hardware updates" in Windows update? Because I never have installed those, there are 7 of them usually. I have been told the optional ones can be wrong.

Yes, the hardware driver updates....The Windows driver can screw things up for a gamer, however it could be worth a shot looking at using Update for the drivers.....I only glanced at the thread, did you find any info regarding the BSOD?

1101
10-06-2011, 05:36 PM
As far as the battery. I will have to figure out where to buy one.

the CMOS batt is usually fairly generic & cheap. Even most supermarkets
have them. I got one from a car parts shop !!

Heres the link for tdsskiller. Rootkit infections arnt very common (ive only seen it twice) but can be very hard to detect.
http://support.kaspersky.com/downloads/utils/tdsskiller.zip

malwarebytes (spyware scanner) this is very good & free. You need to make sure that the issues arent caused by infections.
http://www.malwarebytes.org/

It may also pay to make a image of that basic/minimal XP install & burn to DVD. Just in case. could save you alot of wasted time later.
MaxBlast is very good for that, its free from seagate. Or the WD equivalent.

DarkFather
10-06-2011, 05:59 PM
the CMOS batt is usually fairly generic & cheap. Even most supermarkets
have them. I got one from a car parts shop !!

Heres the link for tdsskiller. Rootkit infections arnt very common (ive only seen it twice) but can be very hard to detect.
http://support.kaspersky.com/downloads/utils/tdsskiller.zip

malwarebytes (spyware scanner) this is very good & free. You need to make sure that the issues arent caused by infections.
http://www.malwarebytes.org/

It may also pay to make a image of that basic/minimal XP install & burn to DVD. Just in case. could save you alot of wasted time later.
MaxBlast is very good for that, its free from seagate. Or the WD equivalent.

I fully scanned both my other internal drives with malwarebytes. 9 threats were found on the second drive, 7 of them were from Keygen's that I have not used in ages or since this trouble began, so that clears them as being any cause. But, 2 of them were in the system volume information\_restore section. If I am not wrong, this could be what keeps infecting my new installs since it has infected the restore section of that HD and could be infecting my new install when I use that drive? One is Trojan.Dropper.PGen the other is a PUP.Hacktool.Patcher.

I have been wanting to do an image so I dont have to keep doing this. I will look into MaxBlast. The one thing I am unclear on is if it makes a full exact copy of your drive including all Windows and Registry files, or just some files?

gary67
10-06-2011, 07:03 PM
It copies everything unless you tell it otherwise.

The forum rules are against keygens and cracks of any sort though

DarkFather
10-06-2011, 07:12 PM
It copies everything unless you tell it otherwise.

The forum rules are against keygens and cracks of any sort though

Ok, i'll try it.

Haven't used any keygens, not in the past few installs anyway. They were just setting there, those programs were old and had not been used in ages. I deleted them anyway after the scan.

sroby
10-06-2011, 10:40 PM
Maxblast images you whole hard drive to dvd or another HD. An exact copy of the whole thing is the easiest option
Maxblast also has the option of making a Bootable CD, you'll need that as well to use to recover with.

If it complains that you havnt got a Seagate HD, HIT 'alt T', 'Alt O' (Tech Overide) at that message.

The stuff in your system restore is probly just old stuff. It wont be causing you problems. AntiSpyware programs REALLY dont like keygens, but its only finding the keygen & not infected win/system/program files etc then its ALL OK.

good luck

DarkFather
18-06-2011, 06:02 AM
So, in doing some research on my setup it seems my PC has been running my Hard Drives as IDE ever since I built this PC nearly 4 years ago now. ALl my hard drives are SATA. How do I go about getting them to read as SATA now, especially after all this time? Which drivers do I need? Maybe this is part of the cause of my trouble recently?

Speedy Gonzales
18-06-2011, 09:16 AM
You have to enable AHCI in the BIOS. And you need SATA drivers (from the mobo site)

However, if you're using XP, you shouldnt enable AHCI in the BIOS now, or the system will crash, the next time you boot it up.

You usually install SATA drivers during the install of windows (with XP anyway - Or the SATA drivers need to be slipstreamed on an XP cd).

Vista and Windows 7 install basic SATA drivers. And AHCI should be enabled in the BIOS before you install windows

Having it on IDE mode or SATA wouldnt cause corrupt files tho

Looks like this mobo uses Silicon Image SATA drivers (http://support.asus.com/Download.aspx?SLanguage=en&m=M2N32-SLI+Deluxe&p=1&s=24). Change it to XP. They're under IDE

DarkFather
18-06-2011, 09:34 AM
You have to enable AHCI in the BIOS. And you need SATA drivers (from the mobo site)

However, if you're using XP, you shouldnt enable AHCI in the BIOS now, or the system will crash, the next time you boot it up.

You usually install SATA drivers during the install of windows (with XP anyway - Or the SATA drivers need to be slipstreamed on an XP cd).

Vista and Windows 7 install basic SATA drivers. And AHCI should be enabled in the BIOS before you install windows

Having it on IDE mode or SATA wouldnt cause corrupt files tho

Looks like this mobo uses Silicon Image SATA drivers (http://support.asus.com/Download.aspx?SLanguage=en&m=M2N32-SLI+Deluxe&p=1&s=24). Change it to XP. They're under IDE

Yes, I downloaded those drivers and created the floppy disk to install them. However, do I need to reinstall Windows (again) and install them during the install with F6 when prompted to?

The thing is, I have always just installed Windows without ever installing the SATA/Raid drivers because I thought they were part of Windows XP Pro. I guess my SATA drives have always run under IDE without me ever even knowing. You are sure this wouldn't be causing any issues? Could installing the SATA drivers increase my performance as well?

The Slipstream with NLite is a bit confusing because my XP Pro disk is only SP1 but all instructions I find are for SP3. Do I not need to make the slipstream include SP2 and SP3? Can the Slipstream also include the Chipset drivers?

Speedy Gonzales
18-06-2011, 09:48 AM
Yes, I downloaded those drivers and created the floppy disk to install them. However, do I need to reinstall Windows (again) and install them during the install with F6 when prompted to?

Correct. Unless you slipstream them. There is a hack on the net, to get AHCI to work (after windows has been installed). But, I've never tried it


The thing is, I have always just installed Windows without ever installing the SATA/Raid drivers because I thought they were part of Windows XP Pro.

Nope, SATA drivers have never been part of the windows install until Vista / Win7.


I guess my SATA drives have always run under IDE without me ever even knowing. You are sure this wouldn't be causing any issues? Could installing the SATA drivers increase my performance as well?

Might increase the performance, BUT I've never had probs (whether it was on IDE or SATA)


The Slipstream with NLite is a bit confusing because my XP Pro disk is only SP1 but all instructions I find are for SP3. Do I not need to make the slipstream include SP2 and SP3? Can the Slipstream also include the Chipset drivers?

Its better if you slipstream as much as you can (including service pack 3). SP3 includes what was in SP2. So, you should be able to slipstream SP3 (without downloading SP2 as well).

In order to slipstream drivers, Nlite needs an inf file. So, if the chipset drivers have an inf file in it, you should be able to slipstream them.

Altho, you may have to use something like 7-zip to extract whats in the exe file (if the chipset drivers is an exe install file).

If you want some help with slipstreaming, I can help you, if you want.

All you need is teamviewer (I can show you remotely what to do). The SATA drivers, and NIC / LAN drivers (if they've got an inf file in them).

And I can show you an easy way of slipstreaming 1 file. So, once you reinstall windows again, XP will be up to date. I usually install something like VirtualPC (and make my own slipstreamed (32 bit cds). Then once I make them up, I test them in VirtualPC. This saves me wasting cd's if it (the ISO I burn to cd), doesnt work / crashes

DarkFather
19-06-2011, 01:19 AM
Well, I really don't want someone else having access to my PC.

Having a problem Slipstreaming the SATA/RAID drivers because when I download it they are for making a Bootdisk only...

I also have a problem with my mouse after a fresh install of Win XP and it freezing after the load screen saying it Made adjustments to my Screen resolution. My mouse wont register and I have to reboot. Can I install the drivers for my mouse in this Slipstream as well?

Speedy Gonzales
19-06-2011, 01:27 AM
You'll see what I'm doing, and I'll probably chat to you as well. . But thats up to you. I've helped heaps of people on here, using teamviewer

You get the other SATA drivers file (not the zip file,with the makedisk.exe file in it). The smaller zipped file. You dont need mouse drivers (unless its got buttons on it, so you can configure whatever)

Probably not a good idea, trying to slipstream the chipset drivers (theyre 61 mb). Since, it includes more than just the chipset drivers

DarkFather
19-06-2011, 04:02 AM
You'll see what I'm doing, and I'll probably chat to you as well. . But thats up to you. I've helped heaps of people on here, using teamviewer

You get the other SATA drivers file (not the zip file,with the makedisk.exe file in it). The smaller zipped file. You dont need mouse drivers (unless its got buttons on it, so you can configure whatever)

Probably not a good idea, trying to slipstream the chipset drivers (theyre 61 mb). Since, it includes more than just the chipset drivers

Ok, I have Teamviewer installed. PM me.

Speedy Gonzales
19-06-2011, 09:00 AM
PM sent

Speedy Gonzales
19-06-2011, 06:45 PM
So far so good, got in with TV, slipstreamed XP with SP3 and SATA drivers and everything else. Created the ISO. Reformatted. Updated the BIOS using Ez-flash.

Just have to see if it behaves now! Only thing that didnt work was firewire for some reason.. Maybe its shorting or something? Or its disabled in the BIOS now. Since the BIOS has been updated

DarkFather
20-06-2011, 03:38 AM
Tried the MAxBlaster to back up my HD. However, it will not let me pick which drive to mount it on. I have another drive I want to mount it on so it's an exact copy and boot's up so I can just switch to that drive incase of data corruption. Any help?

DarkFather
25-06-2011, 11:19 AM
Speedy Gonzales has helped me alot (many thanx) and we did a fresh Sliptream of Win Xp Pro SP3 and all new drivers for everything. Brand new BIOS, etc. Everything has been running fine the past week.

Well, today another BSOD (after watching a few video files). This time I was able to get back in Windows fine and now have the Memdump file and info:

As follows:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini062411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Jun 24 12:26:40.593 2011 (UTC - 7:00)
System Uptime: 0 days 5:42:25.231
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..........
Loading User Symbols
Loading unloaded module list
...................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for MAudioDelta.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioDelta.sys
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Probably caused by : MAudioDelta.sys ( MAudioDelta+2934 )

Followup: MachineOwner
---------






ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4d5f0e3d

BUGCHECK_STR: 0x7f_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805a2729 to 804f9f1e

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b84d7bec 805a2729 0000007f 805395ab 8907d008 nt+0x22f1e
b84d7c44 80542284 b84d7c50 b84d7cf4 805395ab nt+0xcb729
b84d7c50 805395ab badb0d00 00000000 00000000 nt+0x6b284
b84d7cf4 b6f40934 00000004 0000000d 8907d008 nt+0x625ab
b84d7d08 b6f48d01 8a032560 00000004 0000000d MAudioDelta+0x2934
b84d7d28 80545eef 8907d204 8907d008 0000000d MAudioDelta+0xad01
b84d7d2c 8907d204 8907d008 0000000d 00000000 nt+0x6eeef
b84d7d30 8907d008 0000000d 00000000 8055c0c0 0x8907d204
b84d7d34 00000000 00000000 8055c0c0 b833ae20 0x8907d008


STACK_COMMAND: kb

FOLLOWUP_IP:
MAudioDelta+2934
b6f40934 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: MAudioDelta+2934

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MAudioDelta

IMAGE_NAME: MAudioDelta.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------


As well as this:


==================================================
Dump File : Mini062411-01.dmp
Crash Time : 6/24/2011 12:30:56 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 0x00000000
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f1e
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_qfe.101209-1646)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22f1e
Stack Address 1 : ntoskrnl.exe+cb729
Stack Address 2 : ntoskrnl.exe+6b284
Stack Address 3 : ntoskrnl.exe+625ab
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062411-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================


and this:

==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+7495f
From Address : 0x804d7000
To Address : 0x806e5000
Size : 0x0020e000
Time Stamp : 0x4d00d4fc
Time String : 12/9/2010 6:09:16 AM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 5.1.2600.6055 (xpsp_sp3_qfe.101209-1646)
Company : Microsoft Corporation
Full Path : C:\WINDOWS\system32\ntoskrnl.exe
==================================================


I had older drivers for the Audio card since this has been happening. However, this time the drivers are brand new and current, and yet another BSOD. This audio card is not "Authorized by Windows" and never has been. However, it worked fine for 3 years until a few months ago with those drivers. So, it seems my Audio card is dying, or the drivers are bad? Could this have been causing my BSOD and corrupt files?

Speedy Gonzales
25-06-2011, 11:57 AM
PM sent remove the soundcard and use onboard. And remove ZA if you reinstalled it. The 7f stop error can be caused by ZA

DarkFather
25-06-2011, 12:03 PM
PM sent back.

I don't have ZA, and never have.

radium
25-06-2011, 01:20 PM
Speedy has done a ton of work for you, it seems to me (after reading all these posts) and I know you can't afford it... But I think you need a new Motherboard. At least if these problems arn't caused by dodgy programs or themes...

Speedy Gonzales
25-06-2011, 01:29 PM
By the sounds of it the cause now,is the soundcard drivers (not the onboard card). So, he's removed them and the card. And using the onboard soundcard.

Will have to see if that will stop the crashing. If he wants another soundcard, it'll probably be better if he got one thats got signed drivers. This may or may not make a diff. Could be that the drivers that were installed were crappy / buggy