Asagrim
Member
- Messages
- 43
I have been told stackhash crashes are 99% DEP (Data Execution Prevention) related.
I have disabled secure boot in my UEFI to be able to disable DEP using the command "bcdedit.exe /set {current} nx AlwaysOff" in the command prompt,
I verified after a reboot in the system settings, that DEP is entirely disabled, but I still get a StackHash_2264 crash when I try to start the application. The application itself is a portable install that runs just fine on Win7 x64, I have most recent drivers yada yada yada ...
What would be the next step in diagnosing the issue?
I have disabled secure boot in my UEFI to be able to disable DEP using the command "bcdedit.exe /set {current} nx AlwaysOff" in the command prompt,
I verified after a reboot in the system settings, that DEP is entirely disabled, but I still get a StackHash_2264 crash when I try to start the application. The application itself is a portable install that runs just fine on Win7 x64, I have most recent drivers yada yada yada ...
What would be the next step in diagnosing the issue?
My Computer
System One
-
- OS
- Windows 8.1
- Computer type
- PC/Desktop
- CPU
- i3-6100
- Motherboard
- ASUS Z170I PRO GAMING
- Memory
- Kingston 1x8GB 2400MHz@CL15
- Graphics Card(s)
- Sapphire HD7850 2GB
- Monitor(s) Displays
- LG 34UM68-P
- Screen Resolution
- 2560x1080
- Hard Drives
- SAMSUNG 840 Pro 128GB SSD
- PSU
- Corsair TX650W (Seasonic OEM)
- Case
- Zalman M1
- Cooling
- Cooler Master Hyper 212X
- Keyboard
- Ozone Strike Battle MX Brown
- Mouse
- Roccat Nyth
- Internet Speed
- 34 Mbit
- Browser
- Chrome, Cyberfox, Vivaldi
- Antivirus
- common sense upper-intermediate v3.0
- Other Info
- Some of the hardware might seem odd (PSU, SSD), but I'm not wasting money on replacing perfectly functional hardware only because a newer version is out. Nor am I willing to pay extortion money for replacements or intended upgrades (GPU, RAM), especially if that "upgrade" has a hardware design flaw (CPU).