Jump to content

Twilight Phoenix

Anti-Spyware Brigade
  • Content Count

    550
  • Joined

  • Last visited

About Twilight Phoenix

  • Rank
    Advanced Member
  • Birthday 06/26/1986

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Previous Fields

  • Teams:
    Nothing Selected
  1. Well. I return. I attempted to increase the core voltage of my GPU in an attempt to correct the issue. Within hours it crashed again while in Far Cry 3. Nvidia's forums, and a friend of mine, have some suggestions of upping the DRAM voltage as a way to eliminate the issue. Is this safe to do?
  2. Could it be a GPU voltage issue? I've read increasing voltage a bit over stock can help correct the issue.
  3. Well, I did flash it to latest BIOS once before well before I knew that this motherboard had an issue with it. I flashed to the 1201 BIOS version and it absolutely did not help me. It seems unlikely that 1301 will really be any different unless you've details on what this new update specifically addresses.
  4. I'm currently running the 310.70 video drivers. As for the warranty, I'm not entirely sure. I did not purchase the motherboard through them, though their website states it's covered for three years which I've not yet passed. Problem is I'm not sure if I still have the serial number for it. I'm starting to feel I'm up fecal creek without my proverbial paddle here. Seems as though unless I can find the means to begin replacing hardware it's simply something I'm going to need to make peace with and endure.
  5. I can unfortunately confirm the issue doesn't seemed to be resolved, I just had another driver crash in an entirely different application.
  6. Been about a month now since my last crash, and tonight the display driver crashed on me. But it didn't go black, the application (Far Cry 3) just hanged and all I had to do was end the process. While it could be just a crash from the application itself, I thought I'd throw it up here. I won't know for sure until I crash again. Normally they come in clusters, so we'll see.
  7. Hey, Tom. Thanks for getting back to me. I appreciate the reg edit script, but I didn't require it. Microsoft had an .exe that I ran, and it also delayed it to 8 seconds. So, we'll see if this TDR change helps at all. It could be a few days or a few hours before it crashes again, it's completely and utterly random. One thing though, that AMD Chipset update seems to have caused instability. Ever since I installed it I've been receiving Window Explorer crashes, and they've never happened before. Should I revert back to the older drivers I was using before the update?
  8. I just used Microsoft's Fix It application for TDR errors when Googling this problem. We'll see what that does. But now I'm receiving an additional error that I've never had before. Windows Explorer keeps crashing on me. Seems to do it more often when I enter control panel. It started today, right after I installed the AMD Chipset drivers.
  9. If there's an issue with BIOS flashing, then I'd rather avoid that if there's not much hope that's the issue. I've tried tons of drivers in hopes of correcting the error, to no avail. I'll give the registry edit a chance, but would you mind guiding me through it? I've never once willingly edited anything in my registry. I also just installed the new AMD Chipset drivers.
  10. Motherboard is Asus M5A97, BIOS revision 1208. Windows 7, 64-bit. GeForce 560 TI, and no overclocking done to the system. I can't run a RAM test yet but I'll try and get that done as soon as I can.
  11. Hello Pitsters, For the past few months I've been dealing with my nvlddmkm driver crashing at random intervals. I could be gaming, or simply browsing the internet. It doesn't matter what it is I'm doing, it's completely random. I've tried every software fix I could scour Google for to no avail. About a month ago out a random, desperate attempt to solve the issue I switched my PC to run in power saving mode from BIOS. After I made that selection the crashing stopped for a little over a month. I thought I'd solved the issue, even though it might have indicated an issue with my motherboard.
  12. I haven't, no. In any case, I've deleted the hits detected by that MalwareBytes but the problem still remains.
  13. Can anything problematic be seen in my dxdiag log for drivers? I still can't solve my issue despite my best efforts. ------------------ System Information ------------------ Time of this report: 4/24/2008, 23:43:56 Machine name: YOUR-37E34C38B1 Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254) Language: English (Regional Setting: English) System Manufacturer: EMACHINES System Model: T6520 BIOS: Phoenix - Award BIOS v6.00PG Processor: AMD Athlon 64 Processor 340
×
×
  • Create New...