BSOD during first 5 minutes login windows

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

 SPTD Removal:

• Uninstall the software using Add/Remove Programs.
• Reboot the system.
• Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
• DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO

 Clean boot

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\KOOLKAT\Downloads\ISAAC-PC-23_10_2015__15003_17\102015-8299-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`0304a730
Debug session time: Wed Oct 21 09:24:54.482 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:01.887
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80072238f8, 0, 0}

Probably caused by : GenuineIntel

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

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try