64-bit Win 7 SP1 BSOD "SYSTEM_SERVICE_EXCEPTION" post-repair install

On the very first boot after completing a successful, error-free Repair Install (using the SevenForums tutorial), and after entering my username and password but before the desktop appeared, I received the following BSOD message:

SYSTEM_SERVICE_EXCEPTION

STOP: 0x0000003B (0x00000000C0000005, 0xFFFFF960000F3530, 0XFFFFF8800A954ED0, 0X000000000000000)

win32k.sys - Address FFFFF9600003530 base at FFFFF96000030000, DateStamp 53f7e75f

I saved the kernel dump (no mini-dump was created, even though I have that enabled) and the boot log, and uploaded them here. However, once that was done I was already in the process of over-writing the problematic boot volume with a cloned backup volume, so I was unable to run either the DM Log Collector or SF Diagnostic Tool, so I cannot upload those (sorry).

I should also explain that the reason I performed the Repair Install in the first place was that I had been experiencing some weird behavior from a few pieces of third-party software for the last several months that their vendors were completely unable (or unwilling) to resolve, and SFC /SCANNOW never reported any errors, so in the end there was nothing left to try but a Repair Install.

(If it matters, here are some examples of the symptoms of weird behavior that no one was able to solve: A couple of apps (such as from DataViz) worked fine at first but eventually stopped accepting any data pasted from the clipboard, two different company's apps always failed installation attempts with utterly useless "Unknown Error" messages, etc.)

Before beginning the Repair Install, I disabled several non-hardware related third-party startup apps and services (such as antivirus and firewall). (As an aside, I wish I could find a list of services that must be running and those that should not be prior to a Repair Install, but I've never been able to locate any such info)...

Also, note that after the Repair Install I could always boot fine into Safe Mode. I also ran disk check with automatic repair several times against the boot volume. Although the first pass reported some minor problems and repaired them, every subsequent pass reported no errors at all. Nevertheless, I still got the exact same BSOD every time I tried to perform a full normal boot into Windows.

Here are the uploaded files: Kernel Dump and Boot Log.zip (the SevenForums upload failed, so I uploaded it elsewhere.)

Finally, the BlueScreenView info was totally useless. All it did was show the same error message and details that I already quoted above.

If you'd like any other info I can provide, I'd be happy to do so.


Thanks!

Truly, Arc, I very much thank you for your reply, but as I indicated in my OP, I regret that I cannot do as you ask. As I wrote early in my OP:

... However, once that was done I was already in the process of over-writing the problematic boot volume with a cloned backup volume, so I was unable to run either the DM Log Collector or SF Diagnostic Tool, so I cannot upload those (sorry).

You see, I've already completely replaced the boot partition in question with a cloned backup so that I can boot up the old system and continue to work. I cannot produce another BSOD, therefore I cannot create a mini-dump, since the BSOD partition no longer exists. Sorry about that!

Is there anything you can do with the kernel dump, since the mini-dump cannot be created anymore?

Arc said:

I would prefer a minidump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

EDIT: Post the zip after another BSOD, whether there is a minidump or not.