BSOD out of nowhere

[Syxx_Killer]

The computer has been on all day as I turn it on the same time everyday. Just a couple minutes ago a blue screen of death popped up out of nowhere as the computer sat idle. At the top of the screen it said Memory Management. Then, it had the Stop line of code. Here is that code:

0x0000001A (0x00000780, 0xC06A3B40, 0x8137DF04, 0x00004C0)

This is rather alarming. I hope something serious isn't starting to appear.

[ASWnut101]

type this in in the microsoft help center. It should tell you.

[Syxx_Killer]

Thanks, I will check it out later.

I just got an idea to check the Event Viewer in Control Panel. I open it up and view the System reports. One stuck out at me. It is a Service Control Manager error. It occured at 10:12:18 PM. Right around the time of the BSOD. The error message says:

The following boot-start or system-start driver(s) failed to load:
atitray


Could this have triggered the BSOD? It doesn't quite make much sense, though. atitray sounds like it has to do with my video card's driver or ATI's CCC. Why would the BSOD mention something about Memory Management if this error occured around the time of the BSOD? I think this dumb computer is making me paranoid.

Edit:

Nevermind. That must have happened upon the reboot. At 10:11:59 in the Event Viewer there is a Save Dump entry. This is what it says:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x00000780, 0xc06a3b40, 0x8137df04, 0x000004c0). A dump was saved in: C:\WINDOWS\Minidump\Mini010807-01.dmp.

A couple seconds prior to that are two eventlog entries. Each entry says:

The Event log service was started.

[Syxx_Killer]

I did check out Microsoft's Knowledge Base to see what it had to say. It does give me a result but I'm not sure what to make of it. It doesn't really help.

http://support.microsoft.com/kb/282504/en-us

[sonar732]

Do you have an ATI card?

This stop message is hardware related and that's why the atitray points to an ATI card. Check your device manager for conflicts, try a different video driver, etc.

1. Disable Write Combining, this is in your advanced options in your display properties.
2. Disable Video caching via your Bios settings.
3. Check to see if your video card requires updated hardware drives from the 3rd party site.
4. Check the microsoft site for hardware drives if maybe a prefix is needed for the hardware.
5. Start --> Run --> Dxdiag --> Run a couple of Direct X tests to make sure you aren't having a problem with direct X.
6. Pull out your video card and maybe try a different one if you have the resources, if the problem presists, this is not a video card problem.
7. If you cant do #6 try maybe just taking off the side of your computer and look at the video card, is it dusty? Damaged maybe? Is it connected maybe a little lose, tighten it or push it in and make sure its not loose.
8. Check your device manager to make sure your only have ONE display adapter, if you have more then one then your computer is trying to use the settings possibly from your other piece of hardware, simply disable the one you do not have. While you are in there check for any Bangs "!" beside them, if there are Bangs "!" present, there is something being detected with your video card and the device is not working correctly.

[Syxx_Killer]

Yes, I have an ATI card. I don't know if it has anything to do with this Memory Management BSOD or not, though. I think that is a whole other error. If that is some more driver related issues, I'm going back to the ATI 5.10 drivers. They never gave me a problem until that BSOD while playing SH3 a few weeks ago. The file mentioned in the BSOD was ati3duag.dll. I'm guessing maybe it somehow became corrupt as I never got a BSOD playing SH3 before then, and I played it allot. I'm hoping a simple reinstall of the drivers will put a good ati3duag.dll back on. But back to my other BSOD. As I started Windows (XP Pro SP2) today, I got an error message. It said Windows has encountered an error. I could send an error report or not. Event Viewer in Control Panel shows this:

Error code 0000001a, parameter1 00000780, parameter2 c06a3b40, parameter3 8137df04, parameter4 000004c0.

Yet another reference to the original BSOD last night. As I said in a post above, I did check the MS Knwoledge Base but I'm not sure it really helps.

[SUBMAN1]

Originally Posted by Syxx_Killer

Yes, I have an ATI card. I don't know if it has anything to do with this Memory Management BSOD or not, though. I think that is a whole other error. If that is some more driver related issues, I'm going back to the ATI 5.10 drivers. They never gave me a problem until that BSOD while playing SH3 a few weeks ago. The file mentioned in the BSOD was ati3duag.dll. I'm guessing maybe it somehow became corrupt as I never got a BSOD playing SH3 before then, and I played it allot. I'm hoping a simple reinstall of the drivers will put a good ati3duag.dll back on. But back to my other BSOD. As I started Windows (XP Pro SP2) today, I got an error message. It said Windows has encountered an error. I could send an error report or not. Event Viewer in Control Panel shows this:

Error code 0000001a, parameter1 00000780, parameter2 c06a3b40, parameter3 8137df04, parameter4 000004c0.

Yet another reference to the original BSOD last night. As I said in a post above, I did check the MS Knwoledge Base but I'm not sure it really helps.

Your stop code is typicale of impending hardware failure.

-S

[SUBMAN1]

Pull up a command prompt and type 'chkntfs c:' (assuming you are using NTFS and you have one hard disk partition)

If that comes back as not dirty, then type 'chkdsk /f' on the drive - you will need to reboot to complete this.

For testing your hard drive, go here - http://www.seagate.com/www/en-us/sup...loads/seatools

If you decide to download the Desktop bootable version, I find that their splash screen hangs PCI-E graphics cards. TO fix that, go into the .bat file that calls the spalsh screens and remove those lines that call it.

Memory is also another likely thing to go - so to test that, this program will help you:

http://www.memtest86.com/

If its your PSU, get a cheap PSU tester for $14 to test that. You can find them at Fry's or similar computer store.

For testing your CPU, get Prime95 to torture test it - http://www.mersenne.org/freesoft.htm

Sisoft Sandra can also run some stress tests on your hardware -
http://www.sisoftware.net/index.html...uy&langx=en&a=

If you want to look through the crash dump file (Which is probably not going to help you is it's hardware), you can use Debugging Tools for WIndows to take a look -
http://www.microsoft.com/whdc/devtoo...nstallx86.mspx

If you still can't pinpoint the problem, let me know and I'll give you some more tools to test with.

-S

PS. I typically suspect impending hard drive failure as the primary cause of crashes like this. PSU's are second on my list.

[SUBMAN1]

ANother thought - Speedfan also will show you what SMART data looks like on your hard drive and it will also show you if you CPU temps are too high, etc - http://www.almico.com/speedfan.php

With speedfan you can also look at voltages to see how close your PSU is to the proper voltages. Of course, this is your motherboard monitoring going on here and it is not entirely accurate at showing you voltages, so all you should care about is that they are close, though not neccesarily exact. If you voltages are off by say several 10ths of a volt, then you should think about buying a PSU tester.

-S

[SUBMAN1]

One thing just popped into my head - If I remember correctly, the mini crash dump file is erased the moment you hit the 'OK' button upon windows reboot when it warns you about it. If you want to save it, leave the warning on screen, make a copy of the file and save it somewhere else. Basically, I am saving you the headache of trying to find it, that is if you are trying to find it.

-S

[ASWnut101]

Originally Posted by SUBMAN1

Pull up a command prompt and type 'chkntfs c:' (assuming you are using NTFS and you have one hard disk partition).

will that fix the errors or will it just tell you what they are? There is no "/f" suffix after it, which is why I'm wondering.

[Syxx_Killer]

Thanks for the help, Subman. I'll list what I have:

Win XP Pro w/SP2
Abit Radeon RX700-Pro
AMD Athlon64 3500+
Abit Fatal1ty mobo
1GB (2x512) Crucial Ballistix DDR400 RAM
Western Digital Caviar 250GB SATA HD
Fortron Bluestorm 500W dual-rail PSU

If something on this computer takes a dump, I can't really afford to replace it because when I built it, I pretty much stretched my resources really thin (almost two years ago). Most of the parts are still kind of expensive and I can't afford to replace any of them right now. Can a video card cause this? Checking my Event Viewer, there is a consistant error for atitray going back to when I updated my drivers (I updated back around Dec. 23rd). ATI's 5.10 drivers worked the best for me. I updated them because of the BSOD I got while playing SH3. That never happened before. I mentioned it above if you want to go over it again.

[danlisa]

If you find that it IS your ATI Control panel causing the problems you should consider using the Omega Drivers. http://www.omegadrivers.net/.

I remember having this problem with my ATI Catalyst, after updating the drivers there were conflicts with leftover parts of the old version.

See here for a manual (100%) removal instructions for the ATI Catalyst..http://support.ati.com/ics/support/d...asp?deptID=894

[SUBMAN1]

Originally Posted by Syxx_Killer

Thanks for the help, Subman. I'll list what I have:

Win XP Pro w/SP2
Abit Radeon RX700-Pro
AMD Athlon64 3500+
Abit Fatal1ty mobo
1GB (2x512) Crucial Ballistix DDR400 RAM
Western Digital Caviar 250GB SATA HD
Fortron Bluestorm 500W dual-rail PSU

If something on this computer takes a dump, I can't really afford to replace it because when I built it, I pretty much stretched my resources really thin (almost two years ago). Most of the parts are still kind of expensive and I can't afford to replace any of them right now. Can a video card cause this? Checking my Event Viewer, there is a consistant error for atitray going back to when I updated my drivers (I updated back around Dec. 23rd). ATI's 5.10 drivers worked the best for me. I updated them because of the BSOD I got while playing SH3. That never happened before. I mentioned it above if you want to go over it again.

Want the good news or the bad news?

ATI's drivers are unlikely to be causing you issue - I have played every sim on this board 100 times over using whatever was the latest rev for my ATI. I used to own a 9800 AIW (It's a pro model w/ a TV tuner built in), and now I run an x1900 XTX. i've run the Omega drivers as mentioned on this thread too in an effort to defeat Macrovision copyprotection on my old board. I even tried the rev's that were claimed to be Macrovision free, but sadely, I never did quite beat Macrovision. As far as the drivers go, they are a hack, but a decent hack at least. There used to be some reason to run them back when the ATI control panel was a major memory hog, but today that is not the case. Here is a copy of my Task Manager so you can see how much memory it takes today:



As you can see, it take almost nothing. Anyway, as for affording what is in your system today considering something is dying, nothing in your sytem is a major outlay of cash. A 250 GB HD will cost you about $50 to $70. You can probably even get an x1950 Pro now days for less than what you probably originally paid for your x700 Pro. If it makes you feel any better, most video card companies like ATI warrant their board for up to 3 years. A BSOD typically is not caused by a vid card however, but more by a driver fault or bad HD or bad CPU or bad mem.

What you need to do is see if you can reproduce the problem and then isolate it. Test your HD first, them test you mem and then stress your CPU. 3DMark2006 is a good stress test on the vid card too. If all that stuff passes from the links above, then try removing your vid drivers alltogether and reinstalling from scratch. Hopefully you just hit a bug in Windows XP and its a one time thing.

-S

[SUBMAN1]

Originally Posted by ASWnut101

will that fix the errors or will it just tell you what they are? There is no "/f" suffix after it, which is why I'm wondering.

chkntfs is to check if NTFS was shutdown in a dirty state

chkdsk /f will fix errors on the file system and is a totally seperate command from chkntfs