BSOD casued by dxgmms2.sys

Toggle sidebar Toggle sidebar
Sort by date Sort by votes
Did you do this? http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

Direct X errors are normally the GPU so you went to right place

Hard to read that sig at 4k so here is another link - https://valid.x86.fr/hcwjxq
Is it a Medion Erazer X series?
Motherboard is a CLEVO P775TM1-G / SAGER NP8172

Lenova owns Medion, meanwhile Medion uses a design made by Clevo... who really makes the PC you buy? talk about a rabbit hole.

I guess since it only happens in games, its not going to be caused by Intel igpu then. I will get someone to read the dump files.
 
Upvote 0 Downvote


I did do the clean install from that link. My laptop is a Medion Erazer X7849 and I dont think it's a Clevo P775TM1-G. I think its based off the Clevo P670RS-G.
 
Upvote 0 Downvote
I ran WhoCrashed and this is what came up in the analysis:

On Wed 27/06/2018 23:39:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062718-7203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0xD1 (0xE1BBD, 0xD, 0x8, 0xE1BBD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 27/06/2018 23:39:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0xC6)
Bugcheck code: 0xD1 (0xE1BBD, 0xD, 0x8, 0xE1BBD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 27/06/2018 17:14:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062718-12812-01.dmp
This was probably caused by the following module: Unknown (0xFFFFA001D1FDAFA0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80EF7BAB51A, 0xFFFFA001D1FDB758, 0xFFFFA001D1FDAFA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 25/06/2018 23:42:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062518-7109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0xFC (0xFFFFA401B5912180, 0x8A00000001132863, 0xFFFFA401B5956E10, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 25/06/2018 21:44:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062518-39921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17E100)
Bugcheck code: 0xFC (0xFFFF9200FE914180, 0x8A00000001335863, 0xFFFF9200FE956E10, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23/06/2018 16:21:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062318-32875-01.dmp
This was probably caused by the following module: Unknown (0xFFFFBA8068F6BF90)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80A8AB9AF8A, 0xFFFFBA8068F6C758, 0xFFFFBA8068F6BF90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
Upvote 0 Downvote
Who crashed is great at showing you what crashed and 10% of time may actually show the driver to blame, but it doesn't often tell you why it crashed. I used to suggest it a lot but I soon found its better to just go to the dump
Go to C:\Windows\Minidump
copy contents of folder to document or another folder
upload the copies to a file sharing web site and show a link here, I will get someone called Gardenman to reply with a paste bin file that should show me more of what was running at time of crashes..

I got motherboard model from the link you get if you click on your sig, its possible it is wrong. I only did that search to try to find drivers for device

The unknown module is a problem with who crashed.
NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause
hal.dll = hardware abstraction layer. It too sits between windows and hardware

 
Upvote 0 Downvote
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/CYIt.html

File: 062818-6703-01.dmp (Jun 28 2018 - 09:50:55)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: dxgmms2.sys (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 0 Hour(s), 55 Min(s), and 16 Sec(s)

File: 062718-7203-01.dmp (Jun 27 2018 - 18:39:30)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)]
Uptime: 0 Day(s), 4 Hour(s), 00 Min(s), and 46 Sec(s)

File: 062718-12812-01.dmp (Jun 27 2018 - 12:14:06)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: dxgmms2.sys (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 5 Hour(s), 10 Min(s), and 10 Sec(s)

File: 062518-7109-01.dmp (Jun 25 2018 - 18:42:27)
BugCheck: [ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Uptime: 0 Day(s), 0 Hour(s), 43 Min(s), and 12 Sec(s)

File: 062518-39921-01.dmp (Jun 25 2018 - 16:44:18)
BugCheck: [ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Uptime: 0 Day(s), 3 Hour(s), 18 Min(s), and 39 Sec(s)
There were multiple errors in the dump files. This is not your fault, it's either Windows created the dump files incorrectly or the debugger didn't like the dumps.

Remove all overclocks. The overclocking drivers "XtuAcpiDriver.sys" & "IOCBios2.sys" were found on your system. (Intel Extreme Tuning Utility)

PC: Erazer X7841
Motherboard: P670RP6-M
BIOS: VERSION: 1.05.08RGME6 -- DATE: 07/25/2017

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 1 Downvote
Medion driver update site - https://www.medion.com/gb/service/_lightbox/treiber.php?msn=30020518&prod=MEDION%20ERAZER%20X7843%20(MD%2099945)%20UK

Try removing intel processor diagnostic tool if its installed as it appears to be from 2008. Its possible the file in question is also from BatteryCare by OpenLibSys.org or EVGA Precision X as the file is used in many different programs. File name is WinRing0x64.sys

You installed version of Realtek HD Audio is from 2009, odd to find on a relatively new system. The one on the Medion site is from 2015 - I can't tell what driver numbers you have so this might be same file.
Update Realtek NIC driver here - http://www.realtek.com.tw/Downloads/downloadsView.aspx?Conn=4&DownTypeID=3&Langid=1&Level=5&PFid=5&PNid=13

Curious why a notebook even has Intel extreme tuning on it.

There is a bios update newer than what you have installed.

Not sure what Savitech Hotkey is but its from 2013 and isn't a win 10 driver.

Dump agrees that motherboard is a P670RP6-M
 
Upvote 0 Downvote


I dont have the intel processor diagnostic tool or BatteryCare or EVGA Precision X installed.
I updates the Realtek drivers for both audio and networking.
I dont have Intel XTU installed so no idea where thats from.
I got the latest BIOS from the Medion site.
Im guessing the Hotkey thing is from the airplane mode driver.

Anyway, after all this Im still getting BSODs. I've uploaded another minidump here: https://1drv.ms/u/s!Aq_EjEzbdgBBkE2o67BdzXO5Lnhv
 
Upvote 0 Downvote
Your BIOS says "Product Name Erazer X7841 MD99556". I'm not saying you are wrong, that's just what the BIOS on your system says (info from dump file).

I ran the dump file through the debugger and got the following information: https://pste.eu/p/1Ko9.html

File: 062818-27562-01.dmp (Jun 28 2018 - 15:05:45)
BugCheck: [ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Uptime: 0 Day(s), 0 Hour(s), 33 Min(s), and 24 Sec(s)

Colif, that WinRing driver appears to be located in a "Throttlestop" folder so maybe that's what it is assocated with on his system.

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote


So my undervolting settings could be causing my crashing? Jeez, I'll try taking off Throttlestop and see if that helps.
 
Upvote 0 Downvote
I don't like jumping to conclusions so I won't. I don't know if throttlestep is cause, it might be.

xtuacpidriver.sys, while it shows as part of Intel Extreme Tuning is the Intel(R) Acpi Control Driver. ACPI is power management so it is possible another Intel process includes it as well.
iocbios2.sys is also part of same program but to give you benefit of doubt, its possibly part of another Intel program. it is the Intel Extreme Tuning Utility Performance Tuning Driver

I am more curious about why it can't verify timestamp of ntoskrnl as that is the windows kernel.

I wonder if the problem is ram. Try downloading and running memtest86 on your ram, 1 stick at a time, up to 8 passes. Any error count higher then 0 is too many, remove/replace sticks that get errors. Memtest creates a bootable USB
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom