BSOD every time I try to log in

First, I am new to this so sorry if I'm not doing this right.

Yesterday, i installed a 64 bit version of Python (previously had 32 bit version). Had to restart to complete installation; while restarting computer also had several months worth of updates to do (it's a work computer). Since then, every time the computer starts and gets to the Welcome screen, I click 'OK' and it goes into BSOD. I can bypass this by going into safe startup mode and doing a clean boot, I suspect it is one of the startup drivers or something that was changed during the updates.

Please help! If i can provide any other info let me know.

Dan

To clarify,

Right now i am able to run the computer with all non-Microsoft system services turned off, and I don't get any BSOD. When i turn back on all the system services and restart I get the BSOD again, I am just not sure which one is causing it, or what to do about it.

I ran windbg and got the message below, saying the ntkrnlmp.exe file is to blame. I'm not too great at computers but if someone could tell me what the next step would be (as few acronyms as possible plz ><) that would be great.

Thanks,

Dan
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff8800115e722}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff8800115e722

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800034c7fe9 to fffff800034c8a40

STACK_TEXT:
fffff880`02f6bde8 fffff800`034c7fe9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff880`02f6bdf0 fffff800`034c64b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f6bf30 fffff880`0115e722 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`06311000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpGetFileNameInformation+0x492


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`034c64b2 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5507a73c

IMAGE_VERSION: 6.1.7601.18798

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x7f_8_nt!kidoublefaultabort+b2

FAILURE_ID_HASH: {0367acc4-9bb4-ab69-5701-46a2011718e9}

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

Hi Layback bear,

Thanks for the response. I did follow the tutorial and attached it to my initial post, however it didn't name the file with my computer name (I'm not sure why). The crash dumps and other info is in there though.

I have enterprise because this is a computer at a university. I am an administrator on it but I do not own it; I contacted IT guys here and this seems to have stumped the people on staff and many are away on holidays so I decided to post the issue here.

Is there some other information I could provide that would be more useful? All I have is the crash dumps currently.

Dan