BSOD STOP: ntkrnlmp.exe error 0x0000007F

[zdzdz]

Hello, recently I have annoying BSODs 0x07f

My laptop is Lenovo z570 (i5 2450m, 6gb ram, nVidia gt520m).
I have hd graphics which I mostly use.
All the BSODs happen while I use Firefox (37.02) and especially when I watch Youtube videos.
At first I thought it's something graphics related, so I tried to use firefox with nvidia card(changed in optimus) - BSOD. After that I updated hd graphics to the latest version - BSOD.
I changed youtube default player to html5, then again to flash - BSOD.
Last time I haven't opened a Youtube page but again BSOD.
When I don't use firefox and play games or watch videos I don't have problems.

[FONT=Courier New, Courier, FixedSys][SIZE=2][COLOR=#000000]Crash dump  file:        C:\Windows\Minidump\042615-755637-01.dmp
Date/time:              26.4.2015  г. 15:25:15  GMT
Uptime:                 16:09:02
Machine:                IVAN-LAPTOP
Bug  check name:         [URL="http://www.google.com/search?q=MSDN+bugcheck+UNEXPECTED_KERNEL_MODE_TRAP"]UNEXPECTED_KERNEL_MODE_TRAP[/URL]
Bug check  code:         0x7F
Bug check parm 1:       0x9
Bug check parm  2:       0x80050033
Bug check parm 3:       0x406F8
Bug check parm  4:       0x140341941
Probably caused by:     [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT]
Driver description:     
Driver  product:         
Driver  company:         
OS  build:               Built by:  7601.18798.amd64fre.win7sp1_gdr.150316-1654
Architecture:           x64 (64  bit)
CPU count:              4
Page size:              4096

Bug  check description: 
This bug check indicates that the Intel CPU generated a  trap and the kernel failed to catch this trap.

Comments:

The crash  took place in the Windows kernel. Possibly this problem is caused by another  driver that cannot be identified at this time. 

[/COLOR][/SIZE][/FONT]

 

[Arc]

I have never seen such a crash dump before.

Arguments:
[COLOR=Red]Arg1: 0000000000000009, EXCEPTION_NPX_OVERRUN[/COLOR]
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: 00000000021bb703

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


[COLOR=Red]BUGCHECK_STR:  [B]0x7f[/B]_9[/COLOR]

NPX is Numeric Processor Extension is an IC that is designed to be used with the CPU to form a high performance numeric data processing system. So it apparently hints of some hardware issue.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Let us know the results.

 

[zdzdz]

I tested the RAM - no problems at all. No errors, everything passes.

I tested furmark. No problems again. No artifacts or BSOD.

Prime95 ran for 2 hours. Again no errors.

Could a driver be the culprit?

 

[Arc]

Could a driver be the culprit?

As i have said it earlier, I am unaware of this particular error. So I cannot say it with certainty. But I agree it with you, we should search for any failing driver.

Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.