Hi Sukhijashubham. :smile9:
First dump shows BugCheck CA, {a, ffffe000d27af060, 0, fffd} Probably caused by : Ø
And missing informations about
dptf_acpi.sys (part of INTEL Dynamic Platform Thermal Framework Driver?).
What's Ø? I don't know.
Second dump shows BugCheck 50, {fffff6fb400037a8, 0, 0, 6} Probably caused by :
bcmwl63a.sys (I remember in a previous thread a very similar file, if not the same, has been used by the wireless NIC - network adapter).
Then I see between the informations you get errors about DriverTalent by OSToto - drivethelife.com
I think this last software updated drivers it shouldn't update (or, it used a bad source?) and now they are causing you these BSODs.
Now, you can wait for sysnative staff help/opinion or try the following things at your own risk!
1) Roll back the wireless NIC - network adapter driver to its previous version (and see if the problem has been solved; in this case, no need to try the following point).
2) Run driver verifier to get more precise informations.
If you want to try to run driver verifier, please read CAREFULLY the following instructions:
- Change the bcdedit bootmenupolicy setting from standard to legacy:
Read More:
From an elevated command prompt, launch:
Then:
Code:
bcdedit /set bootmenupolicy legacy
Then:
You should get something like (see bold strings):
c:\>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale it-IT
inherit {globalsettings}
default {current}
resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale it-IT
inherit {bootloadersettings}
recoverysequence {5d5a201b-d643-11e4-a71c-9001aae18364}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
nx OptIn
bootmenupolicy Standard
C:\>bcdedit /set bootmenupolicy legacy
The operation completed successfully.
c:\>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale it-IT
inherit {globalsettings}
default {current}
resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale it-IT
inherit {bootloadersettings}
recoverysequence {5d5a201b-d643-11e4-a71c-9001aae18364}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
nx OptIn
bootmenupolicy Legacy
Restart your PC and see if you are able to make appear windows advanced boot options (SAFE MODE included!) with the good old F8 key.
- Create a restore point
- Create a system image
- Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
- Read some other tutorials/guides and WARNINGS on internet.
- Enable verifier
- If you'll get a very fast BSOD after you logged into windows, you'll need to go to safe mode to reset verifier settings.
From an elevated command prompt:
- Post here the new verifier dump
