Boot loop

Maag himself · 19 May 2010

This is getting really frustrating. I built this computer about 7 months ago, so it was a clean install with 7 ultimate 64 bit. The first startup, I experienced this same issue, but I figured out that the controller type wasn't set to AHCI. Since then, the computer has been perfect. A few days ago I came home from work and found my computer doing this same damn boot loop. It gets to the windows splash screen, then just reboots. No BSOD or anything. Everything the bios looks okay to me.. I didn't change anything there. At one point I got the "bootmgr is corrupt" thing, which I was able to resolve but the loop still persists. I don't think it's a hardware such as a hdd or ram issue. I actually was able to boot once, but my video drivers were missing. Restarted to install them, and it was back to square one. The repair tool just tells me it can't repair it, and I've restored it a few times now, with no success.

Any ideass? Could it be the motherboard? I'm running oUt of ideas, and I don't want to wipe everything out.

zigzag3143 · 19 May 2010

Maag himself said:

This is getting really frustrating. I built this computer about 7 months ago, so it was a clean install with 7 ultimate 64 bit. The first startup, I experienced this same issue, but I figured out that the controller type wasn't set to AHCI. Since then, the computer has been perfect. A few days ago I came home from work and found my computer doing this same damn boot loop. It gets to the windows splash screen, then just reboots. No BSOD or anything. Everything the bios looks okay to me.. I didn't change anything there. At one point I got the "bootmgr is corrupt" thing, which I was able to resolve but the loop still persists. I don't think it's a hardware such as a hdd or ram issue. I actually was able to boot once, but my video drivers were missing. Restarted to install them, and it was back to square one. The repair tool just tells me it can't repair it, and I've restored it a few times now, with no success.

Any ideass? Could it be the motherboard? I'm running oUt of ideas, and I don't want to wipe everything out.

Can you boot into safe mode (F8)?

Maag himself · 19 May 2010

Nope.

HMonk · 19 May 2010

You mentioned that at one point your gfx drivers were missing. If you can boot to Safe Mode, delete the gfx drivers and reboot to see if the Windows generic driver will solve the issue.

Monk

Edit: your "Nope" beat my post.

Maag himself · 20 May 2010

Noone has any ideas?

Maag himself · 20 May 2010

Update: I came home today and just tried it and it booted right up, with this "Windows has recovered from an unexpected error" thing.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041287
BCP2: 00000000000013FD
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052010-23072-01.dmp
C:\Users\Mike\AppData\Local\Temp\WER-52478-0.sysdata.xml

Does this mean anything to anyone?

HMonk · 20 May 2010

Did you get this report from Event Viewer?

If not, go to <RUN> type <eventvwr.msc> without brackets and EV will open. Expand both the SYSTEM and APPLICATION trees in the left pane. In the right pane you will see events marked with a white (OK), yellow (warning), and red (error) circle. To see what the errors report, right-click on the red error event, select <PROPERTIES> read the blurb and then click on the blue-highlight link; a blank <HELP AND SUPPORT> window will open. Wait a bit (few seconds/minute depending on your connection speed) and it will populate with data about the crash and may open a web page with further information. That's always my first (simplest) step in my TS routine.

There is a free app called WhoCrashed that often yields more info than EV. You can read about and DL it here.

From there you can review the memory dmp files which you can post here.

Monk

Maag himself · 20 May 2010

Well if I don't have the shittiest of luck, I don't know what. The power went out for a second, and now it's doing the same crap again. If I get it back, I'll do what you said.

Maag himself · 20 May 2010

Well, Its back on and I ran the EV and it had a crapload of errors in it, and I didn't know where to start with it. I also ran WhoCrashed, and it gave two instances of this which could seem like a more likely culprit

On Thu 5/20/2010 4:27:10 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EB6EEE)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\052010-41137-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

zigzag3143 · 20 May 2010

Maag himself said:

Well, Its back on and I ran the EV and it had a crapload of errors in it, and I didn't know where to start with it. I also ran WhoCrashed, and it gave two instances of this which could seem like a more likely culprit

On Thu 5/20/2010 4:27:10 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EB6EEE)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\052010-41137-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

We need the actual DMP file created when your system crashed. Use these to find and upload them to us. V

thanks

Ken