SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Hey,
i keep getting random BSOD's.
.dmp files indicate several errors, but all produce same exception - "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"

what can i do to solve the problem?

here is the lates .dmp



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


Loading Dump File [C:\Minidump\111612-18486-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0325e000 PsLoadedModuleList = 0xfffff800`034a2670
Debug session time: Fri Nov 16 18:08:00.864 2012 (UTC + 2:00)
System Uptime: 1 days 22:51:51.738
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800032ee65a, fffff880035d2538, fffff880035d1d90}

Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800032ee65a, The address that the exception occurred at
Arg3: fffff880035d2538, Exception Record Address
Arg4: fffff880035d1d90, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAcquireFastMutex+1a
fffff800`032ee65a f00fba3100      lock btr dword ptr [rcx],0

EXCEPTION_RECORD:  fffff880035d2538 -- (.exr 0xfffff880035d2538)
ExceptionAddress: fffff800032ee65a (nt!ExAcquireFastMutex+0x000000000000001a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880035d1d90 -- (.cxr 0xfffff880035d1d90)
rax=0000000000000001 rbx=ffff29800dfaaa08 rcx=ffff29800dfaaa08
rdx=0000000000000150 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032ee65a rsp=fffff880035d2770 rbp=fffff880035d28e0
 r8=fffffa800788a5d0  r9=0000000000000002 r10=fffffa8007887c80
r11=fffffa800d617680 r12=fffff8a017659b20 r13=0000000000000000
r14=fffff8a0176599f0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExAcquireFastMutex+0x1a:
fffff800`032ee65a f00fba3100      lock btr dword ptr [rcx],0 ds:002b:ffff2980`0dfaaa08=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!ExAcquireFastMutex+1a
fffff800`032ee65a f00fba3100      lock btr dword ptr [rcx],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880014cc4ab to fffff800032ee65a

STACK_TEXT:  
fffff880`035d2770 fffff880`014cc4ab : fffffa80`0cbc1b10 fffff880`00da74d9 fffffa80`0d617680 fffffa80`0cbc1b10 : nt!ExAcquireFastMutex+0x1a
fffff880`035d27a0 fffff880`00da7bcf : fffff880`035d2950 fffffa80`0c1ecc60 fffff880`035d8000 fffff800`00000002 : Ntfs!NtfsFsdClose+0xcb
fffff880`035d28a0 fffff880`00da66df : fffffa80`079c6a30 fffffa80`0c1ecc60 fffffa80`07887c00 fffffa80`0c1ecc60 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`035d2930 fffff800`035d4f2e : fffffa80`0cbc1b10 fffffa80`0798f820 fffff8a0`189c57b0 fffffa80`079c6a30 : fltmgr!FltpDispatch+0xcf
fffff880`035d2990 fffff800`032e61d4 : 00000000`00000001 00000000`00000000 fffffa80`06a623f0 00000000`00000000 : nt!IopDeleteFile+0x11e
fffff880`035d2a20 fffff800`035780f1 : 00000000`00000000 00000000`0008c081 fffffa80`0bfda1d0 fffffa80`0e874d70 : nt!ObfDereferenceObject+0xd4
fffff880`035d2a80 fffff800`03329651 : fffffa80`0bfda1d8 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0xa1
fffff880`035d2ac0 fffff800`03329515 : 00000000`00000000 00000000`00000080 fffffa80`069ef990 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`035d2b80 fffff800`03573e5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`035d2c00 fffff800`032cdd26 : fffff880`009b3180 fffffa80`06a0d040 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035d2c40 00000000`00000000 : fffff880`035d3000 fffff880`035cd000 fffff880`035d26b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExAcquireFastMutex+1a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

STACK_COMMAND:  .cxr 0xfffff880035d1d90 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!ExAcquireFastMutex+1a

BUCKET_ID:  X64_0x7E_nt!ExAcquireFastMutex+1a

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

|

​Hi,

As I understand the issue, you are keep getting blue screen of death on the computer with error code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M. Please let me know if this is not correct. 

 

You've reached the right forum for your question. We are here to help fix your issue and guide you in the right direction.
Before proceeding with the troubleshooting steps I may need a few more information to understand the issue better.
1. When exactly you get blue screen of death?
2. Did you make any recent changes on the computer prior to this issue?
3. Are you able to boot to the computer normally?
Method 1:
Step 1:
I would suggest you to boot the computer into safe mode and try to perform a virus scan. Check if the issue occurs in Safe Mode or not.

Start your computer in safe mode
http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode

Step 2:
If the issue is fixed in safe mode, then I would suggest you to perform clean boot and remove the program that is causing the issue.

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
http://support.microsoft.com/kb/929135

Note: Follow step 3 from the clean boot article KB929135 to reset the computer to normal mode.
Method 2:
If the issue persists you may scan the computer for virus using Microsoft Safety Scanner.

Microsoft Safety Scanner will help us to get rid of viruses, spyware, and other malicious software.

The Microsoft Safety Scanner is a free downloadable security tool that provides on-demand scanning and helps remove virus, spyware, and other malicious software. It works with your existing antivirus software.

http://www.microsoft.com/security/scanner/en-us/default.aspx

Note: The Microsoft Safety Scanner expires 10 days after being downloaded. To rerun a scan with the latest anti-malware definitions, download and run the Microsoft Safety Scanner again.

Disclaimer: If you run the virus scan the program that is infected with virus will get deleted. So you have to reinstall the program. Also if the files and folders are affected with virus then they might even get deleted.
Method 3:
If the issue is not resolved I would suggest you to try the steps from the following link and check.

Resolving stop (blue screen) errors in Windows 7
http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

Note: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost. If you re-install windows make sure you backup all your data.
Give this a go; I’m confident you will find what you need here. But if you face any further issue please reply back to this post and I'll be happy to assist you further.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

*Dont forget to upload any further DMP files (especially those when verifier is running)


*If you are overclocking anything reset to default before running these tests.
In other words STOP!!!   If you dont know what this means you probably arent


1-Memtest.


*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org  

*Boot from the CD, and leave it running for at least 5 or 6 passes.

*Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

*Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

*But sometimes it'll crash and won't tell you the driver.

*Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

*I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.

*Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

*In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
*Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

*Reboot the system and wait for it to crash to the Blue Screen.

*Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

*If you can't get into Windows because it crashes too soon, try it in Safe Mode.
*If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.



*Further Reading
"http://support.microsoft.com/kb/244617"

Using Driver Verifier to identify issues with Windows drivers for advanced users
Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

ZigZag3143x - 
I am using a notebook, so no 'slot play' for me.
as for the driver verifier, I am afraid to use it


Yes, this is correct.

 

1. When exactly you get blue screen of death? -- The BSOD started about 6 months ago, and i get it randomly. some time's when pkaying, some times when listening to music, and some times i just get when idle. hance no specific reason

2. Did you make any recent changes on the computer prior to this issue?-- hardware changes? no, I'm using a notebook so I'm not even trying to. and i cant recall any changes other than that.

3. Are you able to boot to the computer normally? -- Yes

Method 1:
Step 1: 
I would suggest you to boot the computer into safe mode and try to perform a virus scan. Check if the issue occurs in Safe Mode or not. -- Its a bit tricky I dont know what causing the BSOD and its inconsistent. so there is no tell how long i'll have to wait.



Method 2: 
If the issue persists you may scan the computer for virus using Microsoft Safety Scanner.

Microsoft Safety Scanner will help us to get rid of viruses, spyware, and other malicious software.

The Microsoft Safety Scanner is a free downloadable security tool that provides on-demand scanning and helps remove virus, spyware, and other malicious software. It works with your existing antivirus software.

http://www.microsoft.com/security/scanner/en-us/default.aspx  --
I am using Microsoft Security Essentials. no viruses detected. should I try this Saftey Scanner or it wont matter?


Method 3:
If the issue is not resolved I would suggest you to try the steps from the following link and check.

Resolving stop (blue screen) errors in Windows 7
http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

Note: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost. If you re-install windows make sure you backup all your data.
Give this a go; I’m confident you will find what you need here. But if you face any further issue please reply back to this post and I'll be happy to assist you further. --
Done that a couple of time before I came here, didnt changed anything :S

btw thanks for the fast replies!

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have had the same issue with :

"SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)"

After following your instructions I can't login normally to windows, I have to go through safe mode.  Once I am in safe mode am i supposed to uncheck one of the drivers (using the verifier) and reboot to see if that was the one causing the error?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated January 31, 2021 Views 14,759 Applies to: