I'd like to join.
Posts made by eodregnar
-
Random System Lock Up
While testing game, have had multiple times my system has locked up. Have been checking event viewer and windows error reporting. Unsure exactly what is causing this. Some times i can go 4+ hours without locking up. Other times it will lock up after only 15 to 20 minutes. I will briefly list my system and copy windows error reporting.
CPU => Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2601 Mhz, 6 Core(s), 12 Logical Processor(s) GPU => NVIDIA GeForce RTX 2080 with Max-Q Design RAM memory => 32G SSD memory => 2x 2 TB (1st drive OS, 2nd drive is my game drive with Fractured installed)
(sorry about the format. I cut and pasted)
11/26/2019 1:36 PM Application Error Faulting application name: FracturedLauncher.exe, version: 1.5.0.0, time stamp: 0x5d5d19ef Faulting module name: FracturedLauncher.exe, version: 1.5.0.0, time stamp: 0x5d5d19ef Exception code: 0xc0000409 Fault offset: 0x0000000000bd1e29 Faulting process id: 0xec8 Faulting application start time: 0x01d5a45e824f5ac0 Faulting application path: D:\Program Files\Fractured\FracturedLauncher.exe Faulting module path: D:\Program Files\Fractured\FracturedLauncher.exe Report Id: 69768fe2-ea02-422f-8007-d07e3053e137 Faulting package full name: Faulting package-relative application ID:11/26/2019 1:36 PM Windows Error Reporting Fault bucket 1556798278622557593, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: FracturedLauncher.exe P2: 1.5.0.0 P3: 5d5d19ef P4: FracturedLauncher.exe P5: 1.5.0.0 P6: 5d5d19ef P7: 0000000000bd1e29 P8: c0000409 P9: 0000000000000007 P10: Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9FB.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA89.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA99.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA97.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAB8.tmp.txt These files may be available here: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FracturedLaunche_46f885598d1ebcea1a2a861185b7719ad355158a_f7e5f65d_e69d39e2-66ce-466e-ba5c-798b443b0711 Analysis symbol: Rechecking for solution: 0 Report Id: 69768fe2-ea02-422f-8007-d07e3053e137 Report Status: 268435456 Hashed bucket: c4704e3a90c835e7759adbc9403cb599 Cab Guid: 0
11/26/2019 4:12 AM Application Error Faulting application name: FracturedLauncher.exe, version: 1.5.0.0, time stamp: 0x5d5d19ef Faulting module name: FracturedLauncher.exe, version: 1.5.0.0, time stamp: 0x5d5d19ef Exception code: 0xc0000409 Fault offset: 0x0000000000bd1e29 Faulting process id: 0xd80 Faulting application start time: 0x01d5a40fc11945d8 Faulting application path: D:\Program Files\Fractured\FracturedLauncher.exe Faulting module path: D:\Program Files\Fractured\FracturedLauncher.exe Report Id: b7e5f62b-4688-4f32-95e9-7622a74fc252 Faulting package full name: Faulting package-relative application ID:
11/26/2019 4:12 AM Windows Error Reporting Fault bucket 1556798278622557593, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: FracturedLauncher.exe P2: 1.5.0.0 P3: 5d5d19ef P4: FracturedLauncher.exe P5: 1.5.0.0 P6: 5d5d19ef P7: 0000000000bd1e29 P8: c0000409 P9: 0000000000000007 P10: Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E1C.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EC9.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EDA.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2ED8.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EE8.tmp.txt These files may be available here: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FracturedLaunche_46f885598d1ebcea1a2a861185b7719ad355158a_f7e5f65d_04013eea-d329-40af-bf1a-e0f001acdb4d Analysis symbol: Rechecking for solution: 0 Report Id: b7e5f62b-4688-4f32-95e9-7622a74fc252 Report Status: 268435456 Hashed bucket: c4704e3a90c835e7759adbc9403cb599 Cab Guid: 0
11/26/2019 4:21 AM Application Error Faulting application name: FracturedLauncher.exe, version: 1.5.0.0, time stamp: 0x5d5d19ef Faulting module name: FracturedLauncher.exe, version: 1.5.0.0, time stamp: 0x5d5d19ef Exception code: 0xc0000409 Fault offset: 0x0000000000bd1e29 Faulting process id: 0xe2c Faulting application start time: 0x01d5a410e9302994 Faulting application path: D:\Program Files\Fractured\FracturedLauncher.exe Faulting module path: D:\Program Files\Fractured\FracturedLauncher.exe Report Id: 2bac8012-84c3-4760-8efa-04e2fcd1c37e Faulting package full name: Faulting package-relative application ID:
11/26/2019 4:21 AM Windows Error Reporting Fault bucket 1556798278622557593, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: FracturedLauncher.exe P2: 1.5.0.0 P3: 5d5d19ef P4: FracturedLauncher.exe P5: 1.5.0.0 P6: 5d5d19ef P7: 0000000000bd1e29 P8: c0000409 P9: 0000000000000007 P10: Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB51D.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB59B.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5AB.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5A9.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5BA.tmp.txt These files may be available here: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FracturedLaunche_46f885598d1ebcea1a2a861185b7719ad355158a_f7e5f65d_0d8f3eeb-1b71-4a80-903c-c4c2333c7586 Analysis symbol: Rechecking for solution: 0 Report Id: 2bac8012-84c3-4760-8efa-04e2fcd1c37e Report Status: 268435456 Hashed bucket: c4704e3a90c835e7759adbc9403cb599 Cab Guid: 0
11/26/2019 4:22 AM Windows Error Reporting Fault bucket 2267184434311536116, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: UnityClient@Windows.exe P2: 2019.1.14.35672 P3: 10.0.18363.2.0.0 P4: P5: P6: P7: P8: P9: P10: Attached files: \?\C:\Users\DredW\AppData\Local\Temp\RDRDC57.tmp\empty.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC67.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC68.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC78.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC89.tmp.txt These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 60173a71-af19-481f-9b50-929301a63a37 Report Status: 268435456 Hashed bucket: ba17b319cde780ddff76a83b1f6f1df4 Cab Guid: 0
-
RE: Incorrect Health bar status
Update: After letting wolves attack me for 0 damage. I went to where i knew a Dire Wolf spawns. It killed me in one shot. All my bars are back now. No more "god mode" lol
-
Incorrect Health bar status
All bars are showing 0. All are full. Just prior to this tried adding poison to arrows. Poison disappeared and arrows were moved back to bag.
While fighting wolf damage to me is showing red 0 every time. I am not sure if i am being damaged. Because of status bars are all showing 0.