Jump to content

wjm67x

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. did both of them to be sure. testing now... edit: nope just did it once again... It was worth a try though.
  2. crash directory finally showed up. can anyone give me any ideas from this? cityofheroes-01dv4k8h11a73d5camzz92g4mk.report
  3. Happened again but this time I got an error message saying it was a TDR failure. https://docs.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery?redirectedfrom=MSDN Timeout Detection and Recovery (TDR) 04/19/2017 One of the most common stability problems in graphics occurs when a computer "hangs" or appears completely "frozen" while, in reality, it is processing an end-user command or operation. The end-user typically waits a few seconds and then decides to reboot the computer. The frozen appearance of the computer typically occurs because the GPU is busy processing intensive graphical operations, typically during game play. The GPU does not update the display screen, and the computer appears frozen. In Windows Vista and later, the operating system attempts to detect situations in which computers appear to be completely "frozen". The operating system then attempts to dynamically recover from the frozen situations so that desktops are responsive again. This process of detection and recovery is known as timeout detection and recovery (TDR). In the TDR process, the operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to reinitialize the driver and reset the GPU. Therefore, end users are not required to reboot the operating system, which greatly enhances their experience. The only visible artifact from the hang detection to the recovery is a screen flicker. This screen flicker results when the operating system resets some portions of the graphics stack, which causes a screen redraw. This flicker is eliminated if the display miniport driver complies with Windows Display Driver Model (WDDM) 1.2 and later (see Providing seamless state transitions in WDDM 1.2 and later). Some legacy Microsoft DirectX applications (for example, those DirectX applications that conform to DirectX versions earlier than 9.0) might render to a black screen at the end of this recovery. The end user would have to restart these applications. This sequence briefly describes the TDR process: Timeout detection in the Windows Display Driver Model (WDDM) The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen. To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, direct memory access (DMA) buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play. Preparation for recovery The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis. Desktop recovery The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then re-create its Microsoft Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK. Edit: video drivers were not up to date. They are now. testing to continue. Edit: still does it...
  4. UPGRADED to windows 10 (not an initial install) and it seems to be stable now
  5. went back to windows 8.1 and it STILL does it...
  6. seriously considering switching back to windows 8
  7. Thanks for the info Tahquitz. I just finished rebooting after doing that and will see if that worked for me. (edit: so far so good!) Nope it just did it again. It was worth a shot though.
  8. SO there's maybe a fix for the random crashes???
  9. Thus far it happens with all my characters. I've even tried reducing my video settings to no avail.
  10. I have an issue where the game crashes at random. some days it doesn't do it for hours, other days it crashes every 5 minutes. I'm running tequila on an i7-2600 with 8gb ram (dual 4gb G-skill ripjaws), video card is an Nvidia GTX 750ti with 2Gb ram, windows 10 fully updated. I've tried 32 bit, 64 bit AND safe modes. tried deleting and copying over from a copy of the initial version pre updates, no go still does it. deleted again and reinstalled tequila and did a fresh install from tequila, still crashes. it's completely at random, some days it doesn't do it at all, some days, like today it does it every 5 to 10 minutes. I started noticing it a couple of updates ago and it's been getting worse since. it's not a mapserver issue, I haven't seen a single mapserve message. It's not the video card as the system was recently disassembled, cleaned and rebuilt. Every other game I have runs perfectly fine. Overwatch, WoW, SWTOR, Star Trek Online and Wolfenstein II all run without issues. OS and video codecs are all up to date. Any suggestions would be greatly appreciated. Yes, I know there was another post someone put up who was having similar issues, but his were resolved by cleaning his video card as it was overheating. I've checked everything out and yet it still persists. any help in this would be greatly appreciated. -Hierarch on Everlasting.
  11. Virtue here as well... My alts were Powerstar67x (Peacebringer) Zhaojhyn (Black Adam costume) Thunderhawk (Elec/Elec blaster speedster)
  12. Score is once again on the paragon Chat loader, but Login server is offline. But it looks like it's on it's way.
×
×
  • Create New...