Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Hardware
Hardware Troubleshooting
A couple bluescreens
Message
<blockquote data-quote="vivid" data-source="post: 470520" data-attributes="member: 31598"><p>It was probably caused by : FSPFltd2.sys</p><p></p><p>[CODE]</p><p>KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)</p><p>This is a very common bugcheck. Usually the exception address pinpoints</p><p>the driver/function that caused the problem. Always note this address</p><p>as well as the link date of the driver/image that contains this address.</p><p>Some common problems are exception code 0x80000003. This means a hard</p><p>coded breakpoint or assertion was hit, but this system was booted</p><p>/NODEBUG. This is not supposed to happen as developers should never have</p><p>hardcoded breakpoints in retail code, but ...</p><p>If this happens, make sure a debugger gets connected, and the</p><p>system is booted /DEBUG. This will let us see why this breakpoint is</p><p>happening.</p><p>Arguments:</p><p>Arg1: c0000005, The exception code that was not handled</p><p>Arg2: 82b6d985, The address that the exception occurred at</p><p>Arg3: b14ad6c0, Trap Frame</p><p>Arg4: 00000000</p><p>[/CODE]</p><p><a href="https://msdn.microsoft.com/en-us/library/ff557203%28v=3DVS.85%29.aspx" target="_blank">Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M - Windows 10 hardware dev</a></p></blockquote><p></p>
[QUOTE="vivid, post: 470520, member: 31598"] It was probably caused by : FSPFltd2.sys [CODE] KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 82b6d985, The address that the exception occurred at Arg3: b14ad6c0, Trap Frame Arg4: 00000000 [/CODE] [URL="https://msdn.microsoft.com/en-us/library/ff557203%28v=3DVS.85%29.aspx"]Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M - Windows 10 hardware dev[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top