[Coolyxxx]

Hi,

This is probably not the best place to ask, but I can't find any results anywhere. My windows 7 will crash a minute or 2 after booting. Comes to a blue screen. It produced a dump file, except I'm having trouble reading it. I used this to help me, but the debugging tool says the symbols are not recognised. I have a feeling because it's windows 7.
Tried to attach the dump file, but it won't even accept .rar or .zip

Dump file linky:
http://www.mediafire.com/download.php?0extowfmj3z

Any help appreciated, but if no one knows, I guess it's a reinstall.

[rider200]

Looking at your hardware it doesn't have anything out of the ordinary.

I can come up with a list of different reasons why the system would crash but will ask these questions instead:

What OS did you have before Win 7?
When it crashes did you go in to the BIOS and look at the temp of the processor and motherboard (Your MSI should have this option).

Are your Seagates Raid 1 (mirrored?)

And the last question - Are you using a Dual Boot setup?

If the OS is over driving the processor and causing a thermal shut down then the BIOS will tell you how hot it is getting. (I have Win 7 installed but haven't installed the ASUS utilites and haven't looked at the temp while it is running) This is a long shot but a possiblity.

In another forum a guy said that Win 7 broke his mirror set, then crashed and would not run for more than a minute or two. If you did mirror your drives did you do it with a different OS or Win 7?

Sorry about the questions but the dump file isn't much help for me.

[Coolyxxx]

I was using XP before 7, and still am in a dual boot.
The drives are not setup in Raid.

Why would the OS be overdriving the processor?
And it only started restarting yesterday. It was fine before that. The only thing that I think may have changed it was my speaker setup, I removed 2 speakers.

Will try again now and see if it crashes, and if the temps are high.

Thanks.

[Coolyxxx]

Temperatures after the crash are ~45 celcius for processor
~25 celcius for system.

[rider200]

Hi

45*C is a little high (113*F) but not outragious and shouldn't cause a reboot. (My ASUS with a Core 2 Quad @3.04 GHz runs at 35*C (95*F) under load, it is about 80*F in my office, so it is running 15*F higher than room temp, I live in Az and it is not cost effective to keep this one room below 80*F, the rest of the house would be at 74*F or lower.

What is the normal temp for XP?

Removing sound drivers shouldn't cause it either.

You could try doing a 'Search for New Hardware' and see if something wasn't installed when the OS installed. A long shot but I have seen that happen before.

When you set up the Dual Boot did you use the native Dual Boot that Win 7 provides or did you use some thing like VistBootPro?

When I intially installed VistaBootPro I didn't backup the registry before modifing the Boot Manager. This caused the boot sector of the primary active drive to over written. I had to reinstall XP and Win 7. If not then forget this part, if you are then try uninstalling it and see if that makes any differacnce.

One more thing you can look at and that is the Paging or Swap file. Normally if you let the OS set it up it will make the file 3x the physical memory, but it is recommended to be 1.5x physical memory. Maybe the swap file is so large that it is getting corrupt trying to manage it. Another thing that most Systems Admins do for servers that have over 2 Gig of ram make the swap file the max of 2 gig per hard drive or volume, that is if you have 6 Gig of memory in the comptuer you would spread the swap file accross three drives at 2 gig each (of course you have to have three volumes or drives to do this). I haven't done this with my Win 7 yet because I am going to install the 64 bit versoin and see how that runs on my system.

You may have to reinstall the OS if the paging file isn't causing the problem.

Your system crash with Win 7 is the first I have seen, this is a new OS and we are kinda shooting in the dark to find a resolution for you.

[Carbon]

Wouldn't it be a lot easier if you just told us what the blue screen said?

[Coolyxxx]

Blue screen:
STOP: 0x000000E3 (0xFFFFFA8004D20AC0, 0xFFFFFA8005D79440, 0xFFFFFA8004E12140, 0x0000000000000003)

Temps for XP are ~35 celcius
When searching for new hardware, none were found.
I used the Windows 7 bootmanager.
Paging file was set to 4GB, I increased it, but it didn't fix anything.
I guess it's a reinstall?

[rider200]

This is what MS says about your stop error:

http://support.microsoft.com/kb/281317

This problem can occur because there is a timing problem with the Ntfs.sys file, which may cause a resource to be released even though you did not acquire it.

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base---

Now there isn't a service pack for Win 7 as of yet.

You could reinstall the OS, you may want to go get the 64 bit version and try it instead.

Beta testing is so much fun!

:)

[4D(Fordy(Ford) Ollie]

[QUOTE=rider200;110785]
Beta testing is so much fun!
QUOTE]



Sarcasm, or you actually get a kick out of your PC crashing, fixing it, and it crashing again?

I'm sure I could find some virus filled sites for you if you want links...

[Carbon]

This is a much more general error.

Check this out and see if you have that AnyDVD thing installed. If not, make sure your DVD drives have drivers installed correctly, see if uninstalling these sort of programs fixes it, might disconnect them and see if it goes away to narrow it down.