if you got a monitor and graphics card both setup to support gsync you don't need any vsync settings anymore.
gsync and freesync were developed to replace vsync.
Spoiler
vsync adapts the frame rate output of your graphics card to the max fixed display rate of your monitor.
freesync and gsync both adapt the currrent monitor's display rate to the flexible output rate of the monitor.
for the crashes, try to further analyse the bluescreens, there is a tool here wich can give more information.
Hey thanks for the response, I have bluescreenview and I checked the errors. The main one I get is "caused by driver" hal.dll and error code 0x0124.
I'd keep the replies to this thread and let the other one die.
"
Adolf_Sheetler wrote:
Hey cipher, I forgot to quote your post last time, which I'm guessing didn't give you a notification. I'm still trying to find out what is causing this problem. Is there anyway you could look into that DxDiag to find out more info? I also tried looking at "Bluescreenview" and get the "caused by Hal.dll driver" and error code 0x0124
"
Adolf_Sheetler wrote:
Hey thanks for the response, I have bluescreenview and I checked the errors. The main one I get is "caused by driver" hal.dll and error code 0x0124.
The hal.dll file is the hardware abstraction layer library. It handles chipset communication, PCI Express, ACPI, and even has calls to multi-threading.
First, I'd try disabling multithreading in your graphics options for the PoE client. If it doesn't crash with multithreading disabled, there's your problem: driver issue with chipset and CPU. Possible causes: Windows file corruption, overclocking, or failing hardware. Use sfc to repair system files, disable overclocking, or swap out failing hardware.
Your BSoDs are driver level. That's completely, and I repeat COMPLETELY, unrelated to PoE. If you're seeing this in PoE only, then nothing else you run on your system pushes your computer enough to experience the issues. You can try running a burn-in test with FurMark and full-FFT test with Prim95 at the same time for at least an hour to check system stability overall. But regardless, a BSoD with
If you only get a flat tire when driving a Honda instead of a Toyota, do you blame the Honda for causing flat tires?
In your DXDiag, the drivers, specs, and configuration all look good. However, you have a lot of crashes and BSoDs shown at the bottom of that DXDiag...
"
Spoiler
---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket CLOCK_WATCHDOG_TIMEOUT_8_PROC, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 7dab6940-545c-434e-b69e-19905d090b26
Problem signature:
P1: 101
P2: 18
P3: 0
P4: fffff802a3f4d180
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER1 +++:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 101
P2: 18
P3: 0
P4: fffff802a3f4d180
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER2 +++:
Fault bucket 0x124_GenuineIntel_PROCESSOR_MAE, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: d5bcf978-deb4-4a54-8517-3e4c80cbbe86
Problem signature:
P1: 124
P2: 0
P3: ffffba0ed0d26028
P4: be000000
P5: 800400
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER3 +++:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 124
P2: 0
P3: ffffba0ed0d26028
P4: be000000
P5: 800400
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER4 +++:
Fault bucket 116237936602, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: CorsairLink4.Service.exe
P2: 4.3.0.154
P3: 57c697f6
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_1D_FROM_ntdll+0x0006E1BC
P8: c0000005
P9: 00000008
P10:
+++ WER5 +++:
Fault bucket 116238008778, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: CorsairLink4.Service.exe
P2: 4.3.0.154
P3: 57c697f6
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_33_FROM_ntdll+0x0006E1BC
P8: c0000005
P9: 00000008
P10:
+++ WER6 +++:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: CorsairLink4.Service.exe
P2: 4.3.0.154
P3: 57c697f6
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_1D_FROM_ntdll+0x0006E1BC
P8: c0000005
P9: 00000008
P10:
+++ WER7 +++:
Fault bucket 108377484158, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CUE.exe
P2: 2.4.66.0
P3: 57bc2511
P4: Qt5Gui.dll
P5: 5.6.1.0
P6: 5745cee6
P7: c000041d
P8: 00056aa0
P9:
P10:
+++ WER8 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CUE.exe
P2: 2.4.66.0
P3: 57bc2511
P4: Qt5Gui.dll
P5: 5.6.1.0
P6: 5745cee6
P7: c0000005
P8: 00056aa0
P9:
P10:
+++ WER9 +++:
Fault bucket , type 0
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: HID\virtualdevice&Col05
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Right here, lots of BSoDs and crashes. Specifically...
The last two types of BSoDs indicate that either your hardware is failing or you're overclocking things and they're failing because of the overclock. Fix your system first.
I'd keep the replies to this thread and let the other one die.
"
Adolf_Sheetler wrote:
Hey cipher, I forgot to quote your post last time, which I'm guessing didn't give you a notification. I'm still trying to find out what is causing this problem. Is there anyway you could look into that DxDiag to find out more info? I also tried looking at "Bluescreenview" and get the "caused by Hal.dll driver" and error code 0x0124
"
Adolf_Sheetler wrote:
Hey thanks for the response, I have bluescreenview and I checked the errors. The main one I get is "caused by driver" hal.dll and error code 0x0124.
The hal.dll file is the hardware abstraction layer library. It handles chipset communication, PCI Express, ACPI, and even has calls to multi-threading.
First, I'd try disabling multithreading in your graphics options for the PoE client. If it doesn't crash with multithreading disabled, there's your problem: driver issue with chipset and CPU. Possible causes: Windows file corruption, overclocking, or failing hardware. Use sfc to repair system files, disable overclocking, or swap out failing hardware.
Your BSoDs are driver level. That's completely, and I repeat COMPLETELY, unrelated to PoE. If you're seeing this in PoE only, then nothing else you run on your system pushes your computer enough to experience the issues. You can try running a burn-in test with FurMark and full-FFT test with Prim95 at the same time for at least an hour to check system stability overall. But regardless, a BSoD with
If you only get a flat tire when driving a Honda instead of a Toyota, do you blame the Honda for causing flat tires?
In your DXDiag, the drivers, specs, and configuration all look good. However, you have a lot of crashes and BSoDs shown at the bottom of that DXDiag...
"
Spoiler
---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket CLOCK_WATCHDOG_TIMEOUT_8_PROC, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 7dab6940-545c-434e-b69e-19905d090b26
Problem signature:
P1: 101
P2: 18
P3: 0
P4: fffff802a3f4d180
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER1 +++:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 101
P2: 18
P3: 0
P4: fffff802a3f4d180
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER2 +++:
Fault bucket 0x124_GenuineIntel_PROCESSOR_MAE, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: d5bcf978-deb4-4a54-8517-3e4c80cbbe86
Problem signature:
P1: 124
P2: 0
P3: ffffba0ed0d26028
P4: be000000
P5: 800400
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER3 +++:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 124
P2: 0
P3: ffffba0ed0d26028
P4: be000000
P5: 800400
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:
+++ WER4 +++:
Fault bucket 116237936602, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: CorsairLink4.Service.exe
P2: 4.3.0.154
P3: 57c697f6
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_1D_FROM_ntdll+0x0006E1BC
P8: c0000005
P9: 00000008
P10:
+++ WER5 +++:
Fault bucket 116238008778, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: CorsairLink4.Service.exe
P2: 4.3.0.154
P3: 57c697f6
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_33_FROM_ntdll+0x0006E1BC
P8: c0000005
P9: 00000008
P10:
+++ WER6 +++:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: CorsairLink4.Service.exe
P2: 4.3.0.154
P3: 57c697f6
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_1D_FROM_ntdll+0x0006E1BC
P8: c0000005
P9: 00000008
P10:
+++ WER7 +++:
Fault bucket 108377484158, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CUE.exe
P2: 2.4.66.0
P3: 57bc2511
P4: Qt5Gui.dll
P5: 5.6.1.0
P6: 5745cee6
P7: c000041d
P8: 00056aa0
P9:
P10:
+++ WER8 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CUE.exe
P2: 2.4.66.0
P3: 57bc2511
P4: Qt5Gui.dll
P5: 5.6.1.0
P6: 5745cee6
P7: c0000005
P8: 00056aa0
P9:
P10:
+++ WER9 +++:
Fault bucket , type 0
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: HID\virtualdevice&Col05
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Right here, lots of BSoDs and crashes. Specifically...
The last two types of BSoDs indicate that either your hardware is failing or you're overclocking things and they're failing because of the overclock. Fix your system first.
Thanks for the reply.
Yeah, I've tested my system with every stress test. Memtest 11 hours, Furmark 30 minutes (some say doing longer isn't good for the health of your GPU), and I did also run Prime95 for 2 hours with no issues or any warnings. I didn't have any overclocks on my system.
That said, I do believe now after analyzing my bluescreen reports that it is hardware related even though I had no issues during stress tests. I've taken my PC to the store which I purchased the parts from and am having them repair it (I have warranty on all parts). I'll update once the PC is back and I talk to the techs. My guess is that it is the mobo as all stress tests came back fine.
Last edited by Impaler_Games#0619 on Sep 27, 2016, 7:53:35 PM
Thanks for the reply.
Yeah, I've tested my system with every stress test. Memtest 11 hours, Furmark 30 minutes (some say doing longer isn't good for the health of your GPU), and I did also run Prime95 for 2 hours with no issues or any warnings. I didn't have any overclocks on my system.
Again...
"
cipher_nemo wrote:
You can try running a burn-in test with FurMark and full-FFT test with Prim95 at the same time for at least an hour to check system stability overall.
30 minutes is nothing. And you mentioned you didn't run both Furmark and Prime95 at the same time. That's important.
And no, doing this for a long time is fine for hardware. If that were true, then gaming for hours would bad for the "health" of your GPU. Don't listen to that nonsense, it's an urban myth. Processors are meant to run for extended periods of time at full load. Manufacturers do just that as a "burn-in" test on so many out of the batches to ensure reliability from their fabs.
"
Adolf_Sheetler wrote:
That said, I do believe now after analyzing my bluescreen reports that it is hardware related even though I had no issues during stress tests.
Remember, 30 minutes is not a stress test. Doing just your CPU or your GPU independently is not a system-wide stress test. Furmark tests the GPU, not the CPU, and Prime95 tests the CPU, not the GPU. Both need to be running at the same time to test overall system stability while gaming, as well as power consumption and heat dissipation.
"
Adolf_Sheetler wrote:
I've taken my PC to the store which I purchased the parts from and am having them repair it (I have warranty on all parts). I'll update once the PC is back and I talk to the techs. My guess is that it is the mobo as all stress tests came back fine.
...but you're getting BSoDs. The system isn't stable. Now, if you boot this system to another drive with its own OS and drivers for this system, you may not get any BSoDs, as these crashes are the result of the drivers working with the hardware, not necessarily the drivers or the hardware individually.
On 1080 there are many drivers relating kernels and cpu communication bugs. Also other win bugs are still common. Turn off multithread did the trick for me (bsod as well as crash-orgies)
Most drivers are still in beta phase.
As well as OP "ONLY IN THIS GAME"
Wait for DX 11, may do better, as it drops a lot of old garbage, which most modern gpus don't support anymore. "Think of dosbox lol"
Your dxdiag file looks nice btw! Nice specs. Then again, just look at the hal. Error as an example:
Windows AND poe want the same function called out of the "sandbox" pam crash
Easier: two kids want that same toy
Baby easy: 2 cars want to share 1 lane beside eachother.
Edit 2:
I have same specs except the monitor is an LG ultrawide cinemadisaplay and the SSD is the newer m.2 256GB, logitech mouse and razor keyboard.
Edit 3:
Stresstests for 30 min is a fuckton a lot! Most tests reach way more framedrops/heat within the first 5 minutes than high end games after 5 hours!
There are only a handfull (mostly simulators games) that actually have settings for "future hardware". So a stresstests simulates that and more.
No Problem,
Exile
Last edited by TheExile777#4663 on Sep 28, 2016, 2:21:08 PM
Edit 3:
Stresstests for 30 min is a fuckton a lot! Most tests reach way more framedrops/heat within the first 5 minutes than high end games after 5 hours!
There are only a handfull (mostly simulators games) that actually have settings for "future hardware". So a stresstests simulates that and more.
That's simply not true, regarding the timeframe of stress tests. Very true about the differences between stress tests and gaming. In all of my years of IT, I've personally had systems perform just fine for 20-30 minutes, then completely choke after hours of the same test.
Serious hardware issues can be detected within the first few minutes of any stress test. Unstable overclocking and voltage drops may not affect systems until hours later. This is generally why many people get away with unstable overclocks for gaming in one game and have issues in another, since the GPU and CPU are not always at full load all the time.
Fact: heat can have a cumulative affect on a system. At full load, a system with inadequate cooling can continue to build up more and more heat over time. If the cooling is grossly inadequate, that build up is quick and noticeable. If the cooling is barely adequate, that build up takes much, much longer.
Note: PoE now uses multi-threading. While gaming wasn't so stressful on CPUs in the past, in these days it is for any engine that has true multi-threading (and no just separate threading for different core tasks).
Poe's multithread is atm imho a fucking joke and beta when not even alpha stage...
Test results in bulks should be collected and fine tuned BEFORE release.
Another thing is that it's not really about cooli g nowadays (ssd, gpus with big fans, fucking most important cpu ice cooler needs to be big, agree on that one... But!... You CAN program it to overheat with certain loop calculation criterias and out loop at let's say 110 Centigrades. I7 is way cooler than i5 due to lower power usage.
Another thing is that IT Means a galaxy full of different "computer genies" and has nada to do with hardware knowledge (other than lego building a pc).
I did that at the age of 8! And blew every gpu before getting a new one (overclock the shit out of them). For fun.
TLDR: pie is so bugged, most errors, crashes, bluescreens-even if not directly, wut accompanied by running poe, is so true when "users" say it only happens in poe. It does only fucking happen here.
Thanks for the reply.
Yeah, I've tested my system with every stress test. Memtest 11 hours, Furmark 30 minutes (some say doing longer isn't good for the health of your GPU), and I did also run Prime95 for 2 hours with no issues or any warnings. I didn't have any overclocks on my system.
Again...
"
cipher_nemo wrote:
You can try running a burn-in test with FurMark and full-FFT test with Prim95 at the same time for at least an hour to check system stability overall.
30 minutes is nothing. And you mentioned you didn't run both Furmark and Prime95 at the same time. That's important.
Just strange that a 30min stress test on Furmark or 2 hour test on Prime95 wouldn't show anything but loading into Path of Exile and crashing within 5 minutes.
And no, doing this for a long time is fine for hardware. If that were true, then gaming for hours would bad for the "health" of your GPU. Don't listen to that nonsense, it's an urban myth. Processors are meant to run for extended periods of time at full load. Manufacturers do just that as a "burn-in" test on so many out of the batches to ensure reliability from their fabs.
"
Adolf_Sheetler wrote:
That said, I do believe now after analyzing my bluescreen reports that it is hardware related even though I had no issues during stress tests.
Remember, 30 minutes is not a stress test. Doing just your CPU or your GPU independently is not a system-wide stress test. Furmark tests the GPU, not the CPU, and Prime95 tests the CPU, not the GPU. Both need to be running at the same time to test overall system stability while gaming, as well as power consumption and heat dissipation.
"
Adolf_Sheetler wrote:
I've taken my PC to the store which I purchased the parts from and am having them repair it (I have warranty on all parts). I'll update once the PC is back and I talk to the techs. My guess is that it is the mobo as all stress tests came back fine.
...but you're getting BSoDs. The system isn't stable. Now, if you boot this system to another drive with its own OS and drivers for this system, you may not get any BSoDs, as these crashes are the result of the drivers working with the hardware, not necessarily the drivers or the hardware individually.
I mean, I've completely re-installed windows new. Nothing on either drive. So I don't necessarily think it was the drivers. I even tried each individual driver 1 version back when I wasn't having problems and that didn't do anything. That was the main reason I'm thinking it's a hardware issue.
On 1080 there are many drivers relating kernels and cpu communication bugs. Also other win bugs are still common. Turn off multithread did the trick for me (bsod as well as crash-orgies)
Most drivers are still in beta phase.
As well as OP "ONLY IN THIS GAME"
Wait for DX 11, may do better, as it drops a lot of old garbage, which most modern gpus don't support anymore. "Think of dosbox lol"
Your dxdiag file looks nice btw! Nice specs. Then again, just look at the hal. Error as an example:
Windows AND poe want the same function called out of the "sandbox" pam crash
Easier: two kids want that same toy
Baby easy: 2 cars want to share 1 lane beside eachother.
Edit 2:
I have same specs except the monitor is an LG ultrawide cinemadisaplay and the SSD is the newer m.2 256GB, logitech mouse and razor keyboard.
Edit 3:
Stresstests for 30 min is a fuckton a lot! Most tests reach way more framedrops/heat within the first 5 minutes than high end games after 5 hours!
There are only a handfull (mostly simulators games) that actually have settings for "future hardware". So a stresstests simulates that and more.
Thanks, and yeah it's just so difficult to find the exact problem, especially since I'm not too familiar with reading error reports and digging up the info they give. Either way, I'll probably get my PC back next week and hopefully the issue will be hardware related (so I don't pay and get a free replacement)
