Solved BSOD with APC_INDEX_MISMATCH

[pumafred]

I've had two or three blue screens and I barely managed to see APC_INDEX_MISMATCH before the PC reset itself.

Also, I don't know if it is related or not, at startup my computer almost always does a Boot reloop, getting stuck there. However, if I press F9, which for my Gigabyte BIOS is Info, and let it stay there for a few seconds, when I then press Ok, the PC always loops one more time and then Windows starts normally.
I mention this, because when I tried with an Ubuntu startup disk, I never had this reboot problem.

I attach the suggested file.

 

[Arc]

Welcome aboard.

Can you please Uninstall Daemon tools, and report us the situation after that?

 

[pumafred]

I uninstalled Daemon with Revo Uninstaller's most thorough option.
The "boot loop" continues, unfortunately.
I will report further if and when I get a BSOD.
Thanks.

 

[Arc]

I expect there will be no further BSODs.

For boot loop, first you download this STPD standalone installer, Execute it, and delete what it finds.

Then, run http://www.sevenforums.com/tutorials/681-startup-repair.html for three separate times, with restarts after every single run.

Best of luck.

 

[pumafred]

Thanks for your help.
You lost me with "delete what it finds. I downloaded and ran SPTDinst-v183-x64 and it asked me to reboot afterwards.
After rebooting, there was nothing to be seen anywhere, much less to delete.
If I run the program again, it says it is already there and asks if I want to Update or Uninstall.
Should I leave it at that and move on to Startup Repair?

 

[Arc]

:sarc:
There is nothing to be installed at all. It is standalone. An executive file that executes itself... without being installed.

STPD.sys is a part of Deamon tools, and the worst part most probably. The boot loop is probably caused by it, so I told you to uninstall it.

Seeing your results, I just downloaded it, double clicked, and it executed, nothing installed.
View attachment 238369

If STPD is there, the uninstall button will be available, and you are to remove it by pressing that button.

So, run the tool again and do it now.

After that, go for Startup repair.

 

[pumafred]

Did the Uninstall, reset and ran Startup Repair three times.
Every time it said it found nothing to repair.
Unfortunately, the boot loop continues.
Don't give up on me, please!

 

[pumafred]

Perhaps I should also mention that, as with Ubuntu disk, I did not get the boot loop with the Startup Repair disk.

 

[Arc]

Describe the boot loop in detail, please?
Exactly what is happening when you power the computer on?

 

[pumafred]

1) Power on
2) "Beep"
3) Gigabyte screen
4) Black screen
5) "Beep"
And so on

As mentioned before, if I choose F9 in Gigabyte screen, I get a small System Information screen. If I leave it there for a few seconds and then press "Ok", I get one more black screen, Gigabyte screen, and then Windows starts.
(I've also noticed that in one round of the Gigabyte screen the keyboard does not work, but it does in the following round.)

Also as mentioned before, none of this happens if I start the PC with an Ubuntu disk or a Windows Startup Repair disk. In these cases I get a most normal sequence of quick Beep-Gigabyte screen-Option to boot from disk.

Thanks again.

 

[gregrocker]

Please post back a screenshot of your maximized Disk Management drive map and listings:

1. Type Disk Management in Start Search box.
2. Open Disk Mgmt. window and maximize it.
3. Type Snipping Tool in Start Search box.
4. Open Snipping Tool, choose Rectangular Snip, click New, draw a box around full drive map and all listings.
5, Save Snip, attach using paper clip in Reply Box.

Tell us what is on each partition.

 

[pumafred]

Attached.
This PC aims to be a home studio recording PC.
C: devoted to Programs (Windows created "System Reserved" when I installed it.)
E: Music projects
D: Material to be read by programs (samples and loops)
Please let me know if you need clarification.
Thanks!

 

[gregrocker]

The config is correct. If you unplug the other HD"s does the problem replicate? If not then there may be stray boot code on one that is interfering. A solution for this is to move the data off of the problem HD to wipe with Diskpart Clean Command.

If problem persists with only Win7 HD plugged in then sort the boot by running Startup Repair - Run 3 Separate Times no matter what it reports. This will ensure the System boot files are intact and working correctly, however it can't always correct any bad boot code which remains on the HD from previous installs.

It could also be a hardware problem. CHeck for newer BIOS Update - what is it for? Also look in BIOS setup at fast boot options to try each. We have hardware experts who can help you with it more. I specialize in installation.

 

[pumafred]

Gregrocker: will do and report back.

Arc: just had a BSOD.

 

[Arc]

We need to see the BSOD dumps ... it works better than an intimation.

 

[pumafred]

I apologize if I was read as intimating anybody. Not my intention at all.

How do I produce those dumps?

 

[Arc]

If there is a crash, it will create dump. You need to collect it, following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Slartybart]

intimation: guesses, hints - not direct information

I apologize if I was read as intimating anybody. Not my intention at all.

 

[pumafred]

If there is a crash, it will create dump. You need to collect it, following the Blue Screen of Death (BSOD) Posting Instructions.

Attached

 

[pumafred]

intimation: guesses, hints - not direct information

I apologize if I was read as intimating anybody. Not my intention at all.

Thanks for the clarification. Spanish is my first language and led me to misunderstand the meaning of the word.