Windows 10: 0x00000119 ntoskrnl.exe+142940 BSOD - Possibly related to sleep

Hi, new member here, I thought this looks like the place to try and get over a annoying problem. Every 1 or 2 days intermittently I am getting a BSOD, it usually happens when my PC wakes up from sleep, but I can't repeat it. (I have tried manually sleeping my PC, then waking it, then sleeping and waking etc but it just happens so intermittently) I followed the sticky here to generate my report. I have been using bluescreenview to try and pinpoint the problem and the error module seems always to be ntoskrnl.exe

At this point I feel like if the error happened within a couple of minutes rather than a couple of days it would be far easier to get to the bottom of, but I just want my PC to be stable.

You will probably see I am overclocking my CPU from my report and I understand for troubleshooting purposes I need to turn this off. Other things I have tried include running memtest for 24 hours (no errors) and running driver verifier. Driver verifier caused BSOD on my Samsung SSD driver (I think SamsungRapidSvc I think) before the pc even booted and just stuck there, so I couldn't get to the memory dump to attach here.

I have updated on windows update and also made sure I have the latest Samsung magician, SSD firmware etc. I own a 840 EVO.

I am not sure if I am facing multiple problems here, before when I have had sleep issues it has usually pointed to the GPU, but ntoskrnl suggests something else, as does running driver verifier.

Any help is much appreciated. Thanks in advance.

Dodge

Attachment 95565

:)

 

BSOD APC_INDEX_MISMATCH ntoskrnl.exe+142940

I had a BSOD. Bug Check String APC_INDEX_MISMATCH , cause by driver ntoskrnl.exe caused by address ntoskrnl.exe+142940. Adive on the fix for this. XPS 15 9950 RUNNING Windows 10 Pro.

 

Continuing BSOD issue

OK, I will try that for a while. There has only been one more BSOD in the last two days. Again, occurring while the system was idle (Checked for any scheduled activities during that time - none). Again, it was the same fault ntoskrnl.exe +142940.

 

The last dump indicates a problem with your NVIDIA GeForce GTX 660 driver or card.
Code: ffffd001`0791c998 fffff800`1b6ed835Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x4d835[/quote] I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.

Edit: All 3 dumps are the same.

 

Thank you for your reply! I have done what you said, hopefully it fixes it. I did however notice last night my PC went to sleep while I was afk and I came back and it didn't wake, my screens were black and after a couple of minutes it restarted. Afterwards I found a new memory dump that looked different from the others. I wondered if you could help with this error too?

Attachment 96273

I also had another problem today when my computer was coming out to sleep, this time it woke but the screens didn't turn on, instead artifacts were appearing and the monitors kept flashing, see:

[youtube]8Cbqus53RXg[/youtube]

I kept it going for a while to see if it would BSOD but it didn't and I had to force a restart. Here is a new attached dm log. Attachment 96285

 

Last dump shows a Machine check:
Code: WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe0006f2638f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.[/quote] Code: MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV[/quote] Code: 2: kd> !errrec ffffe0006f2638f8 =============================================================================== Common Platform Error Record @ ffffe0006f2638f8 ------------------------------------------------------------------------------- Record Id : 01d1f68ebf5d0b17 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/15/2016 0:48:34 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe0006f263978 Section @ ffffe0006f263a50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000610f01 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe0006f2639c0 Section @ ffffe0006f263b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 01 0f 61 00 00 08 04 00 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe0006f263b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0006f263a08 Section @ ffffe0006f263b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4) Status : 0xbe00000000070f0f Address : 0x00000000f0100570 Misc. : 0xc00a0fff01000000[/quote] Can be hardware or software generated. Did you remove all over clocking and set all voltages to normal?

===================================================
RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information


MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

===================================================


HDD Test





Run SeaTools to check the integrity of your HDD.
SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

Run the following tests

• Short Drive Self Test
• Short generic
• Long generic

If the short generic fails, no need for the long generic.



Note Do not run SeaTools on an SSD as the results will be invalid.

Post screenshots/photos of the test results.

Again, please make sure all over clocking is removed and all voltages are set to normal/default.

 

I've ran memtest86 (not the + fork does this matter)? for over 16 hours which was 3 passes of my 16gb of ram. I thought using that version was better as it's been updated recently compared to 2013. Is this okay? Do I really need to run 8 passes? It will take me almost 48 hours.

I have also run the HDD tests on my two data drives and found no faults in seatools.

I haven't managed to get screenshots because my PC kept sleeping and crashing so I lost the results but I'm running the long test again overnight with sleep disabled (takes about 10 hours on my largest HDD) to try and get one.

As for my memtest results, I was close to taking a photo but I didn't in the end (damn I should have read your reply better) but I hope you can trust me that with my results.

I have since received another bsod the same as my first 3 video scheduler ones after the fresh reinstall of drivers so that still isn't fixed! However I did read that it could be an issue in the latest windows build so I have since opted in for insider builds and I'm running the latest to see if it goes away.

I also had another standby crash since then but I'm not sure it's related. I'll upload the new dump file when I can.

Yes my system is at stock clocks again, it doesn't seem to make a difference. The computer still crashes.

I have attached the latest 3 dumps, the very latest one from today was after I installed the insider build, it looks like another one of the dxgmms2 errors which looks like the problem still isn't fixed.

I have read online that a lot of other nvidia users on windows 10 are also having this dxgmms2 BSOD.

Attachment 96716

 

The reason we request you run memtest86+ rather than memtest86 is because we've had better results with it. We've had cases where memory failures showed up in the later passes. Just last week there was one on pass 7. Run as many as you can.

You have two diffe3rent kinds of Ram, Memory 2x Gskill F3-1866C9-4GAB & 2x Corsair CML8GX3M2A1866C9.
Try removing half of your ram, two of the same kind. Run and see what happens. If it still fails, swap ram and test some more. If all is well when one pair is removed then one or more of them is almost certainly defective and needs to be replaced.

 

The memtest86 was fine for 16 hours, no errors, but I will try with the other version. My HDD test however failed one of the long tests.
Yes my memory is two different brands (I tried to get the same but it was discontinued) but it seems to be fine so far in tests.











Its not a Seagate drive so I can't attempt to fix it in the software, I will write zeros to the drive and then run a chkdsk. I don't think this has much to do with my BSODs though since its a drive only used for data. My primary drive is an SSD.

 

What is the make and full model number of the SSD?

Never mind, found it in the msoinfo.nfo file: Samsung SSD 840 EVO 250GB
Is it's firmware up to date? Run Samsung Magician and have it check for a firmware update and install if there is one.

I have the same drive and my firmware was updated a week ago to EXT0DB6Q via Samsung Magician.

 

Thanks @Ztruker, I hope this test is enough to prove stability of memory, almost 40 hours + 16 of the non + version before that. Is it safe to say there is no problem with memory? I remember running memtest for a while when I installed my new ram too, just to make sure it didn't cause a problem like I had heard it can.



I updated my SSD firmware recently too, here's a screen from magician:




The only BSOD I have now is the dxgmms2 one I linked earlier (from 18th of August). I have yet to receive any more, when I do I will update with them. I am worried about this dxgmms2 error because it seems like it could be a common issue for some nvidia users. I've thought about setting a higher TDR delay, I seem to only have this error with sleeping my PC sometimes so I will try to get it again.

Edit* I also wrote zeros to my secondary drive that failed its test and performed a chkdsk, no errors.

 

Yes, looks like your PC RAM is good.

Reading through this article from Nvidia on TDR, it doesn't sound to me like this would cause the dxgmms2 error. You can try playing with it. Making it to short can cause problems, making it too long should only cause a hang for a short time before Windows resets the GPU.

 

Its been a while and I still haven't got to the bottom of my bsods.
I have however found out a sure reason that I can almost (70% of the time) get a BSOD to happen. It happens when the PC tries to sleep when I am playing back a video in MPC-HC and with the MadVR renderer. But strangely, it doesn't always happen if I manually place the PC to sleep, only if I leave it to fall to sleep by its own timer (like setting sleep to 2 mins in power options).
But sometimes I get bsods anyway, even when not playing a video. In my dumps only one points to the nvidia driver, the others to ntoskrnl.exe.
I'm truly stuck here. Really don't know what else to try.*Sad

 

I would try not using sleep. Use a screen saver and have it turn off the monitor and hard drive after some specified period of time instead. See if that helps. Not a fix but maybe a valid work around.

 

Yeah it looks like I may just have to accept not being able to sleep my pc *Sad it really sucks though as I bought this system determined to make it stable *Sad