Jump to content

Dios

Member
  • Posts

    33
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ah, then it might be a possibility. But it still didn't explain the 2 hours or so period after I had just rolled back the BIOS to the original version when all games run smoothly without any hiccups. I'll try to work something out on borrowing another GPU
  2. ah... I forgot to mention it in my post, but I've done that several times. I've even did a clean install of windows 10 along with all the latest driver. I've been using this particular GPU for almost 1 year with no issue. This problem arose not long after I switched to Ryzen, also I don't have another GPU. Did "thermal fault" only happen after a while or can it happen instantly after the GPU experienced some load? because even after a cold boot the problem will happen immediately. Note: just now I turned the computer on and went straight to dirt 4. Didn't even get 1 minute of driving time before it happened
  3. This has happened several times, for the past couple of weeks. Basically, the screen suddenly freeze on a single frame but the game will keep playing (still respond to inputs and sound still plays). PC Spec AMD Ryzen 5 1600 Gigabyte Aorus x370 Gaming K5 Corsair Vengeance LPX 2666MHz (2x4gb) Seasonic m12ii-620 evo Colorful iGame GTX 970 Ymir OC Sandisk 128GB SSD (OS Drive) Hitachi 7200 RPM 1TB HDD (Games are installed here) I tried reverting back to F1 BIOS earlier today, and Dirt 4 manages to run without issue for about 1 hour (previously I'm not able to play for more than 5 mins before it freezes). But suddenly the problem came back, the game freezes and now the thing will freeze and crash just like before I reverted back to the F1 BIOS. Event Viewer log of the crash: Faulting application name: dirt4.exe, version: 0.1.120.786, time stamp: 0x59398d9f Faulting module name: dirt4.exe, version: 0.1.120.786, time stamp: 0x59398d9f Exception code: 0xc000041d Fault offset: 0x0000000000df2107 Faulting process ID: 0x714 Faulting application start time: 0x01d2e9b6b71c5106 Faulting application path: D:\Games\DiRT 4\dirt4.exe Faulting module path: D:\Games\DiRT 4\dirt4.exe Report ID: 1ea53c54-635d-4e37-bcda-2f605fb5a0fd Faulting package full name: Faulting package-relative application ID: Edit: another log that I found of the crash Fault bucket 120776242018, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: dirt4.exe P2: 0.1.120.786 P3: 59398d9f P4: dirt4.exe P5: 0.1.120.786 P6: 59398d9f P7: c000041d P8: 0000000000df2107 P9: P10: Attached files: \\?\C:\Users\glenn\AppData\Local\Temp\WEREEF2.tmp.WERDataCollectionStatus.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER267.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER277.tmp.txt \\?\C:\Users\glenn\AppData\Local\Temp\WER1F5F.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7034.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dirt4.exe_7295cc2d20c9c9ef5e2b4fb985543969ea9db1_03e44d54_23ed767e Analysis symbol: Rechecking for solution: 0 Report ID: 1ea53c54-635d-4e37-bcda-2f605fb5a0fd Report Status: 268435464 Hashed bucket: 679d159aaba7ab7a39503c6fec31e4c1
  4. Lowering the memory clock? and then raising power limit? I haven't run memtest. So far the only troubleshooting that I've done have been related to the gpu.
  5. yes. with ddu in safe mode and then performing a clean install of the new drivers
  6. I did reinstall the driver several times. I even try out different drivers with no luck
  7. I haven't. Yea, been having this issue for the past 2-3 weeks. So annoying. Do you have any idea what might caused it? I was thinking it might be driver related.
  8. I've been running into these issues quite frequently, across multiple games. Basically the screen freezes (stuck in one frame) but the game still respond to input (sound keeps playing and responding to any given control). For example in Dota 2 when this happens I can still talk to my teammates via voice chat, but the screen is stuck. I've tried reinstalling windows and drivers. Currently using windows version 1703 (OS Build15063) and Nvidia Driver 382.53. Anyone have any idea how to fix this? PC Spec: AMD Ryzen 5 1600 Overclocked to 3.7Ghz @1.46v GIgabyte Aorus X370 Gaming K5 motherboard with latest BIOS (F3C) Corsair 8GB kit (2x4GB) Vengeance LPX 2666 R (stuck at 2133) Colorful iGame GTX 970 Top Ymir OC Seasonic M12ii-620W EVO Sandisk 120GB SSD (OS Drive) Hitachi 1TB 7200RPS HDD (game drive)
  9. No it didn't. It just froze without warning. When the screen froze, it's just the screen. The cursor is still movable, and even I can still chat via voice with my teammates.
  10. System specs: AMD Ryzen 5 1600 Gigabyte GA-X370-Gaming K5 Corsair vengeance lpx 8gn (2x4) 2666 igame GTX 970 Ymir OC Windows 10 pro 64 bit The game is running off a hitachi 1tb HDD and the OS is in a Sandisk 120gb SSD
  11. Dota 2 keeps freezing both in the menus and in game. Tried everything from verifying local data, several launch options (-safe, -autoconfig, -dx11), tried reinstalling the game, I've even reinstalled windows. None seemed to work. Also, I started experiencing this issue after upgrading to ryzen 5 1600. Anyone has a solution?
  12. I just installed MacType and found myself really liking the smoother fonts that's resulted. But I notice that the start menu still retain the standard (admittedly worse looking) windows font. How do I change this?
  13. Will the 1500X overclock better ? Or somehow perform better in games ?
  14. As per the title, which one is better for gaming and light productivity ? I can afford either of them, but I've no idea whether to go for the binned quad core or the 'basic' six core part. The cpu will be paired with AsRock's X370 Gaming K4 and 8GB Apacer kit
  15. I know.... I almost did it. But hey, only 1 month until ryzen got released. Then I can say goodbye to this ****** of a cpu. *Linus still uses it for a build guide though*
×