immediate bsod on wow launch, went through blizzard tech support already to no avail. Other games launch fine through both bnet and steam.
computer:
Windows 7 ultimate x64
2 AMD Opteron 4386
nvidia geforce 1060
32 GB memory
Last edited by smefan; 15 Aug 2018 at 20:07. Reason: added some computer info
Run Whocrashed. Resplendence Software - WhoCrashed, automatic crash dump analyzer
It may be cryptic, but can shed more light on what the conflict is. Post its results.
Did WoW run prior? Have you installed any software or hardware prior to this happening? Have you looked in Event Viewer?
On Wed 8/15/2018 9:27:34 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-27066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xFC (0xFFFFF88003397180, 0x8000000832B2C963, 0xFFFFF880033C6AB0, 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 Wed 8/15/2018 9:27:34 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!PoCallDriver+0x4E30)
Bugcheck code: 0xFC (0xFFFFF88003397180, 0x8000000832B2C963, 0xFFFFF880033C6AB0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 Wed 8/15/2018 9:07:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-29406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93970)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Wed 8/15/2018 6:35:38 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003637183, 0x1, 0x0)
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 Wed 8/15/2018 5:15:40 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-32931-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xFC (0xFFFFF880033D0180, 0x80000008136E8963, 0xFFFFF880033FFAB0, 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 Wed 8/15/2018 2:52:12 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-32604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xFC (0xFFFFF88002F00180, 0x8000000414D9B963, 0xFFFFF88002F28AB0, 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 Wed 8/15/2018 2:25:25 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-34445-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xFC (0xFFFFF880030A5180, 0x8000000414C58963, 0xFFFFF880030CDAB0, 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 Wed 8/15/2018 12:55:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-31808-01.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0xB581)
Bugcheck code: 0xFC (0xFFFFF880031F1180, 0x800000041432A963, 0xFFFFF8800325BAB0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Wed 8/15/2018 12:26:44 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-30732-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xFC (0xFFFFF88003524180, 0x8000000813730963, 0xFFFFF8800354CAB0, 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 Wed 8/15/2018 12:18:08 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081518-34569-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xFC (0xFFFFF88003172180, 0x8000000414ECB963, 0xFFFFF8800319AAB0, 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.
Wow ran a year or so ago on the same hardware, I looked in event viewer but I'm not really sure how to comprehend any of it.
I don't think this is connected anymore?
Code:Name [00000013] Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter Adapter Type Not Available Product Type Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter Installed Yes PNP Device ID Not Available Last Reset 8/15/2018 6:37 PM Index 13 Service Name RTL8192su IP Address Not Available IP Subnet Not Available Default IP Gateway Not Available DHCP Enabled Yes DHCP Server Not Available DHCP Lease Expires Not Available DHCP Lease Obtained Not Available MAC Address Not Available
Diagnostic Test
DRIVER VERIFIER
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Incidentally I ran driver verifier last night after posting on here, my computer immediately bluescreened and I removed the driver that driver verifier said was responsible, turned verifier back on and no bsod for ~20 mins, launched wow -> immediate bsod, the driver 'responsible' was an nvidia driver. Last night before bed I ran memtest86 and it detected no errors over almost 3 passes; today I did a fresh install of windows as I'd been meaning to for some time and the problem still persists (immediate bsod on attempted wow launch)
System Information (local)
--------------------------------------------------------------------------------
Computer name: STEFAN-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: H8DCL, Supermicro
CPU: AuthenticAMD AMD Opteron(tm) Processor 4386 AMD586, level: 21
16 logical processors, active mask: 65535
RAM: 34341031936 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
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
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
One crash dump has been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Last edited by smefan; 16 Aug 2018 at 18:11. Reason: added whocrash for latest bsod
Here is the new info file
Last edited by smefan; 16 Aug 2018 at 18:17. Reason: misclicked attachment
Quote