Solved System thread exception not handled error when restarting PC

May 25, 2015 at 09:12:43
Specs: Windows 8.1
hp pavilion17 notebook pc How do I fix error system thread exception not handled. no other error message is given. I am able to turn off computer and to turn it on with no error, however when i try to restart my computer it gives the error

See More: System thread exception not handled error when restarting PC

Report •

✔ Best Answer
May 27, 2015 at 07:27:01
Re "critical structure corruption error"

If the system was updated from Win 8 to Win 8.1 then did you update your drivers?
You get the drivers from the HP website quoting your model number. Do not get drivers from other websites. If you are in the USA this is the HP website:
http://www8.hp.com/us/en/drivers.html

Always pop back and let us know the outcome - thanks



#1
May 25, 2015 at 12:31:33
This would be worth a try:
http://www.tomshardware.co.uk/faq/i...

Always pop back and let us know the outcome - thanks


Report •

#2
May 25, 2015 at 12:43:20
Thanks for the quick reply! I have already tried this and unfortunately it hasn't helped.

Report •

#3
May 25, 2015 at 12:44:14
I have downloaded farbar recovery tool if that is helpful? I just don't know what to look for.

message edited by jaso77


Report •

Related Solutions

#4
May 25, 2015 at 16:55:29
"I have downloaded farbar recovery tool if that is helpful? I just don't know what to look for"

I can have a look.

The logs are large, upload both ( 2 ) using this, or upload to a site of your choosing. No account needed. Give us the links please.
http://www.zippyshare.com/
Instructions on how to use ZippyShare.
http://i.imgur.com/naG6t2T.gif
http://i.imgur.com/Vi9ZdIh.gif
http://i.imgur.com/1IZu5kP.gif


Report •

#5
May 25, 2015 at 17:31:49
Hey thanks so much for helping, this error has been annoying.

http://www69.zippyshare.com/v/n5RAf...

http://www69.zippyshare.com/v/vpGPW...


Report •

#6
May 25, 2015 at 17:38:40
i also included my mini dump file as well

http://www39.zippyshare.com/v/SYx7y...


Report •

#7
May 25, 2015 at 17:55:25
"i also included my mini dump file as well"
Good thinking, just starting on them now.

Report •

#8
May 25, 2015 at 18:11:07
The dump file is the best starting point, when you get that sorted out.
Download the latest version of Farbar and save it onto your Desktop. If your default download location is not the Desktop, drag it out of it's location onto the Desktop.
Run Farbar again please, follow this SS & upload the 2 new logs.
http://i.imgur.com/i3fg3Pf.gif

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
https://msdn.microsoft.com/en-us/li...


Report •

#9
May 25, 2015 at 18:12:39
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff800`43e02000 PsLoadedModuleList = 0xfffff800`440db250
Debug session time: Wed Dec 3 19:06:21.167 2014 (UTC - 4:00)
System Uptime: 2 days 20:24:34.924
*******************************************************************************
* *
* Bugcheck Analysis *
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa80332d604a, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80043e64608, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
READ_ADDRESS: fffff800440c8c60: Unable to get special pool info
fffff800440c8c60: Unable to get special pool info
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffffa80332d604a
FAULTING_IP:
nt!MiMapPageInHyperSpaceWorker+40
fffff800`43e64608 450fb6411a movzx r8d,byte ptr [r9+1Ah]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 0
TRAP_FRAME: ffffd001e31b9570 -- (.trap 0xffffd001e31b9570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000110f201
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80043e64608 rsp=ffffd001e31b9708 rbp=ffffd001e31b97a1
r8=0000000080000000 r9=fffffa80332d6030 r10=ffffd001e31b9800
r11=000000000110f201 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiMapPageInHyperSpaceWorker+0x40:
fffff800`43e64608 450fb6411a movzx r8d,byte ptr [r9+1Ah] ds:fffffa80`332d604a=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80043f80d65 to fffff80043f529a0
STACK_TEXT:
ffffd001`e31b9308 fffff800`43f80d65 : 00000000`00000050 fffffa80`332d604a 00000000`00000000 ffffd001`e31b9570 : nt!KeBugCheckEx
ffffd001`e31b9310 fffff800`43e5a2b9 : 00000000`00000000 ffffe000`dc3aa900 ffffd001`e31b9570 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1deb5
ffffd001`e31b93b0 fffff800`43f5cc2f : 00000000`00000000 00000000`00000000 00000000`00010000 fffff800`43e6438b : nt!MmAccessFault+0x769
ffffd001`e31b9570 fffff800`43e64608 : fffff800`43ea2727 00000000`00000000 ffffd001`e31b97a1 ffffffff`ffffffff : nt!KiPageFault+0x12f
ffffd001`e31b9708 fffff800`43ea2727 : 00000000`00000000 ffffd001`e31b97a1 ffffffff`ffffffff ffffe000`00000000 : nt!MiMapPageInHyperSpaceWorker+0x40
ffffd001`e31b9710 fffff800`43ea46c8 : 00000000`00000002 ffffd001`e31b9878 ffffe000`dc3aadd8 ffffd001`00000000 : nt!MiWaitForInPageComplete+0x343
ffffd001`e31b9800 fffff800`43e5a10a : ffffe000`dc3aadd8 ffffe000`dc52b080 00000000`00000000 ffffd001`e31b9970 : nt!MiIssueHardFault+0x184
ffffd001`e31b98c0 fffff800`43f5cc2f : 00000000`00000000 00000000`00002000 00000000`00000001 00000000`00027000 : nt!MmAccessFault+0x5ba
ffffd001`e31b9a80 00007ffb`c1391889 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
000000c2`0d8cd0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffb`c1391889
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!MiMapPageInHyperSpaceWorker+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 54503718
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_AV_nt!MiMapPageInHyperSpaceWorker+40
BUCKET_ID: X64_AV_nt!MiMapPageInHyperSpaceWorker+40
Followup: MachineOwner

Report •

#10
May 25, 2015 at 18:38:49
Just to double check, that dump file is from last year, is that the latest you have?

This is what relates to your post.
https://msdn.microsoft.com/en-us/li...

message edited by Johnw


Report •

#11
May 25, 2015 at 18:55:38
Another step.

1: Uninstall > AMD catalyst control center

2: Test.

message edited by Johnw


Report •

#12
May 25, 2015 at 19:23:26
Okay, so these are the new files, farbar is installed on my desktop. Yes, that is the most recent mini dump file,I have been limping along with it as is for awhile now. http://www53.zippyshare.com/v/XCH5h...
http://www53.zippyshare.com/v/ibA0x...

I don't understand what to do with the Microsoft link you provided. (not tech savvy enough I guess.)

About deleting catalyst, I also have raptyr the "gaming evolved" Steam-like app. this is a part of catalyst. Do you think it will delete my games attached to it? My restarting issue was happening before I installed catalyst, which is the latest rendition of the driver.

message edited by jaso77


Report •

#13
May 25, 2015 at 19:36:42
"1: Uninstall > AMD catalyst control center"
Go ahead, this is a common cause of your > System thread exception not handled error

"I don't understand what to do with the Microsoft link you provided"
Scroll down & read the Resolution.


Report •

#14
May 26, 2015 at 18:08:03
Ok so before I could do any of the above things, I got a new bsod.... critical structure corruption

Report •

#15
May 26, 2015 at 18:34:36
Any chance you have a program on there called MacDrive, which lets you read Mac-formatted harddrives? If so uninstalling the program cured the "critical structure corruption error" for someone else.

Always pop back and let us know the outcome - thanks


Report •

#16
May 26, 2015 at 18:51:21
No. .. no mac programs. I am not sure if this is helpful, but it is above my level. https://software.intel.com/en-us/fo...

Report •

#17
May 26, 2015 at 20:57:56
"I am not sure if this is helpful, but it is above my level"
All you can do is google what you don't understand.

What AV ( anti virus ) are you using?

message edited by Johnw


Report •

#18
May 26, 2015 at 21:34:33
Windows defender, malwarebytes anti exploit-free, malwarebytes anti malware

Report •

#19
May 26, 2015 at 22:03:34
"Windows defender, malwarebytes anti exploit-free, malwarebytes anti malware"
They are what I use, but I would like you to do a test with Malwarebytes removed & see if you still get problems.

To make sure we get a thorough clean, use this 2 step uninstaller.

Wise Program Uninstaller
http://www.softpedia.com/get/Tweak/...
http://www.freewarefiles.com/Wise-P...
http://www.freewarefiles.com/screen...
http://wisecleaner.com/wiseuninstal...


Report •

#20
May 27, 2015 at 07:27:01
✔ Best Answer
Re "critical structure corruption error"

If the system was updated from Win 8 to Win 8.1 then did you update your drivers?
You get the drivers from the HP website quoting your model number. Do not get drivers from other websites. If you are in the USA this is the HP website:
http://www8.hp.com/us/en/drivers.html

Always pop back and let us know the outcome - thanks


Report •

#21
May 27, 2015 at 19:42:38
The system was updated along time ago, and yeah I've kept up to date with drivers. I'm able to run windows normally using the debug, but there are still a lot of errors not fixed, and they seem to only increase.

Report •

#22
May 27, 2015 at 19:45:54
I very much appreciate everyone's help. Johnw, and Derek, I am working long hours, so it is taking me awhile to get through this.

Report •

#23
June 30, 2015 at 13:32:50
So sorry it's taken me so long to get back to you guys. I do really appreciate the time and help you both gave. In the end, I gave up and just reinstalled win. 8 then had to go through the whole new drivers and updating to win 8.1, so it is all working good now.

Report •

#24
June 30, 2015 at 14:14:42
Good to hear it's sorted and thanks for popping back to let us know.

Always pop back and let us know the outcome - thanks


Report •

Ask Question