I'm wondering if it's a setting in your GPU software or in fact the GPU driver. It may even be a graphics setting in WoW its self.
You could also try stress testing the GPU. FurMark > Home
If the GPU crashes then I would suspect it's a bad card or the PSU is at fault. There is another program to test a GPU's memory. 5 Ways to Check the Memory of Your Video Card For Errors • Raymond.CC
Unfortunately the latest dump didn't contain any info, so we have to wait for another crash.
Last edited by axe0; 21 Aug 2018 at 14:32.
Just now I went to get more dumps, as thus far the bsod happened consistently right when I tried to run wow.exe and I was met with a windows error window. The info listed therein is as follows:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Wow.exe
Application Version: 8.0.1.27377
Application Timestamp: 5b7477e4
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.19135
Fault Module Timestamp: 56a1c9c5
Exception Code: c0000005
Exception Offset: 000000000004c941
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: b147
Additional Information 2: b147a6015de3ed8d401be1ac83e27254
Additional Information 3: 7b2b
Additional Information 4: 7b2be237f42c69dd561cfeb51ea9c36d
I don't know if this helps at all
Well now windows doesn't seem to be creating new dump files, I think everything is configured correctly and on the bsod it says that the dump is being written to the disk, I think it's configured correctly to do so but there's nothing being created. I'm installing windows updates maybe that will help?
The windows update fixed that problem, I've triggered the bsod a bunch more times and the dumps are here. Also, I tried stress testing my gpu as was suggested and everything went fine, I'll test my gpu memory tonight but I don't think it's at fault as I've had literally no issue doing anything besides attempting to launch wow; as for graphics drivers the crashing happened exactly the same with outdated nvidia drivers (at first), then with the up to date drivers, then again with the same up to date drivers on the fresh install.
To summarize: I can trigger this pretty much at will as I just have to run wow.exe for the bsod to happen immediately; running driver verifier doesn't seem to cause bsod (unless I run wow.exe), I tested my memory and found no faults. I hadn't experienced a bsod beforehand on this machine for a period of more than one year, and every bsod I've experienced thus far (barring one caused by driver verifier on the old windows install) has been immediately upon attempting to run wow.exe.
On Sat 8/18/2018 1:39:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081818-27159-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xFC (0xFFFFF88003132180, 0x8000000413B9E963, 0xFFFFF88003161AB0, 0x2)
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 8/18/2018 1:36:23 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081818-27565-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xFC (0xFFFFF8800331E180, 0x8000000813679963, 0xFFFFF8800334DAB0, 0x2)
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 8/18/2018 1:33:50 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081818-29343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xFC (0xFFFFF88003132180, 0x8000000413B9E963, 0xFFFFF88003161AB0, 0x2)
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 8/18/2018 1:29:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081818-28813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xFC (0xFFFFF880033E4180, 0x8000000813610963, 0xFFFFF8800345BAB0, 0x2)
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 8/18/2018 1:15:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081818-30700-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000D6FD25, 0x0, 0x38691CF5)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 8/16/2018 3:58:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: Unknown (0x000000026497B860)
Bugcheck code: 0xD1 (0x26497B860, 0x2, 0x8, 0x26497B860)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
whoops, my bad i misclicked
Could you provide a kernel dump of an ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY crash, it looks like the minidumps do not contain enough info.
The kernel dump, C:\Windows\MEMORY.dmp, should be uploaded to onedrive, google drive, dropbox or a similar 3rd party service and post a link in your next post please.
Microsoft services
They're currently uploading and won't be done until this post is ~4 hours old.
Quote