BSOD Caused By ntoskrnl.exe
- Thread starter m4r35ca
- Start date
Elmer BeFuddled
Resident eejit
- Joined
- Jun 12, 2010
- Messages
- 1,050
- Reaction score
- 251
Hi m4r35ca and Welcome to The Forum.
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack.
Your latest dump file lists WinFLdrv.sys as the probable cause.
This is a driver belonging to Folder Lock.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Random stop codes can often indicate hardware issues.
As a Priority:
Uninstall FolderLock
Bugcheck Analysis:
Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.
HTH.
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack.
Your latest dump file lists WinFLdrv.sys as the probable cause.
This is a driver belonging to Folder Lock.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Random stop codes can often indicate hardware issues.
As a Priority:
Uninstall FolderLock
Bugcheck Analysis:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 8f503750, 0, 0}
Unable to load image WinFLdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WinFLdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for WinFLdrv.sys
Unable to load image eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
*** WARNING: Unable to verify timestamp for epfw.sys
*** ERROR: Module load completed but symbols could not be loaded for epfw.sys
Probably caused by : WinFLdrv.sys ( WinFLdrv+1a50 )
Followup: MachineOwnerLet us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.
HTH.