BSOD for 3 months BCCode: 7f

Code:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff800030e0ef6

There are two common cause of a double fault.
A driver causing stack overflow; and
A hardware issue.
First let us check for the drivers. 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.

Also, from another crash dump ....

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80003088770, fffff880034f44c8, fffff880034f3d20}

Probably caused by : msrpc.sys ( msrpc!LRPC_CASSOCIATION::OpenSecurityContextWorker+b9 )

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

Remote control programs also can cause this BSOD. So if you have any such program installed, Uninstall it.

Better download and install CCleaner. Then run it.
Go to "Tools" .... by default it will open the "uninstall" tab.
Click on save as text file. Save it on your desktop.
Upload the text file for us.

Enable Driver Verifier yourself, following the instructions carefully. Let us see how it responds?

Not seeing any remote control program, apparently. If anything I missed (I am not aware of all the installed programs, but most of them are games. :) ) Driver Verifier will catch it.

So you are a dedicated gamer? Nice! :)

Add one more thing .... as you are planning to shut the computer down in between a verifier session. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Otherwise the computer may give a trouble at the reboot.

If anything is there to be caught by the verifier, it will not take 24 hours. This is just a maximum time set in order to be sure.

Enable it. If it causes BSOD, then disable it and supply the crash dump.

Now execute the Blue Screen of Death (BSOD) Posting Instructions again so that we can check the crash dump.