Solved MacBook Pro 2011 - Startup Repair BSOD after every Hard Shutdown

[caseyfriday]

I've been working on this for about 4 days now, and I'm officially asking someone else for help. I even dished out $30 for RegCure Pro, hoping that it would fix some magical registry madness that is causing my problem.

I've installed a legit "System Builder" copy of Windows 7 Professional on a client's MacBook Pro 15" (2.3 quad-i7) 2011 model, on the Bootcamp partition that's formatted NTFS. It boots fine, and it restarts just fine, but when I actually shut the thing down and let it sit for longer than 60 seconds before turning it back on, the BSOD occurs on startup.

After 60 seconds or more of being completely off, a startup to the Windows partition will result in an IRQL_NOT_LESS_OR_EQUAL BSOD, and then it goes to the Startup Repair screen. It doesn't matter if I skip Startup Repair or run it - the system will boot either way, right after the BSOD. I can reboot the system 10 times in a row with no issues after this, but the second I shut down and leave it turned off for more than 60 seconds, the error returns.

I've attached my SF diagnostic file, so hopefully someone here can make some sense of this. This is a fresh install, by the way. This laptop had no issues for three years, then I replaced the stock RAM with 16GB of Patriot 1333 Mac RAM, a Crucial M4 512GB SSD, and I replaced 32bit Win7 Pro with 64bit Win7 Pro. I've run the Windows memory test from the DVD, and it found no memory issues. I ran the Mac version of memtest for 5 passes (about 4 hours), and it found no issues with the RAM.

Ideas?

Edit: Forgot to mention I installed the most recent version of Bootcamp (5.0.5033), so all the drivers are whatever Apple decided on.

 

[Arc]

Hi caseyfriday.

One of the BSODs are blaming AVG.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff80002ca6150}

*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
[COLOR=Red]Probably caused by : avgldx64.sys[/COLOR] ( avgldx64+2032d )

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

So better you uninstall AVG. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Also, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
_______________________________________________________________________________________

BugCheck A, {10, 2, 1, fffff80002ca6150}

*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : avgldx64.sys ( avgldx64+2032d )

Followup: MachineOwner
------------------------------------------------------------------------------------
BugCheck 1A, {8886, fffffa800c4593f0, fffffa800c4594e0, 105}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )

Followup: MachineOwner
------------------------------------------------------------------------------------
BugCheck 4E, {99, 41784b, 2, 4177ca}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

 

[caseyfriday]

I uninstalled AVG and let the computer sit again. I had another blue screen on startup, but it came and went too fast for me to see what it was, and then I didn't see it when I opened Blue Screen Viewer.

I ran the SF Diagnostic again and have uploaded my new diagnostic file. I appreciate your recommendation for testing the RAM, but like I said in my first post, I already ran memtest for 5 passes for 4-5 hours total. I'm willing to do it again, but I want to see if the problem is something else first.

On a side note, I have no problems booting into Mac OSX 10.8.5, and no issues while it's loaded and running. It's only booting Windows after the laptop has been off for over 60 seconds, and when it's booting up, it gets to "Starting Windows" and the flag doesn't show up - it just hangs there.

I hope my new diagnostic file has something telling in it!

 

[Arc]

No BSOD is recorded.

As you are not having any issue with Mac, it may be simply a driver caused issue in the parts of windows. Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[caseyfriday]

Well, I just tried enabling the Driver Verifier, and the laptop boots up to Windows and gets to the login screen. I click on the username, type in the password, press enter, and then the Welcome icon starts spinning - then stops spinning and freezes. I tap the power button, and the laptop shuts down instantly.

I'll start up in Safe Mode and see if I can get some sort of Diagnostic report to find out why Windows won't even let me completely load after logging in.

 

[caseyfriday]

There are no new dump files, but I did try to run memtest off of a DVD I burned it to, using IMGBurn. Memtest freezes at 18% and won't go any further. I don't know if this is indicative of a memory issue, or something else, since as I said before - no memory issues on the Mac OSX side. Here's a photo of the RAM and of the spot the Memtest freezes.

 

[Arc]

EDIT: Did not see your post earlier, as it appeared while I was typing.

Yes, what is happening there should be treated as memory issue. You should replace the RAM, at least as a test.

Memtest is an OS independent platform. It runs from outside of windows, so it may be considered that what it is finding is independent of what Windows is facing, and there should be one-to-one correspondence between those two.

 

[caseyfriday]

The memtest I was running with that blue screen was on a DVD that loaded after the Windows kernel loaded. When I ran ANOTHER version of memtest, booting straight from the Mac EFI to the DVD, it ran for 5 hours and found no problems.

I'm going to let the laptop sit for 30 minutes, and then try to boot it up again to see if this issue is still present after deleting the AVG nonsense. If it still is, I'll do an 8-pass memtest, and if that finds problems, I'll get this memory RMA'ed.

Thanks so much for your help!

 

[caseyfriday]

I just took the laptop apart to replace the thermal compound on the CPU and GPU, since it was getting incredibly hot during idle operation. The heat issue is fixed now (there was almost no thermal compound on the actual processor dies - just on the PCB next to them, where it's not needed.

I booted up and got the blue screen again, but I opened Blue Screen Viewer, and I don't see an October 6 mini dump. I set up mini dump files from a tutorial on this forum, but it didn't seem to get created. Is this because the BSOD is happening during boot up, and not once the system is loaded?

Nonetheless, I created a new diagnostic file. If nothing new comes from this diagnostic file, I'm RMA'ing the RAM tomorrow.

I also performed an Extended Hardware Test (as well as a simple one) from the Mac Hardware Test suite, and it reported no issues. It ran for about an hour and a half.

 

[caseyfriday]

Fixed it. I personally own a 17" MacBook Pro with the exact same specs as the laptop I've been quoting in this thread. I have Komputerbay RAM installed in my laptop (also 2 x 8GB), and so I swapped the two laptops' RAM, and now it boots with no issues!

Since I don't run Windows on my laptop, I can keep the Patriot memory for myself, since it works fine and passes 5-passes of Memtest86+.

Thanks again so much for all the help everyone gave me here! This forum is truly a gem.

 

[Arc]

Very good to know.

Let us know for any further issue.

Yes, what is happening there should be treated as memory issue. You should replace the RAM, at least as a test.