Random BSOD's (x0124), Graphic glitches, TDR's, in games (Skyrim, Total War, Youtube VIdeos, google maps)

Specifications:



Windows 7 64 bits SP1 Home edition

Ati Radeon HD 7750, driver updated (17.2.1 version)

AMD Athlon II x2 250

8gb RAM


Been playing skyrim for more than 2 years and I'd no issues. But recently it started to show graphical glitches:

(example)

Then the bsod's started.

I made a clean Windows 7 reinstall in another drive (new WD blue), full reinstall of drivers along with the Skyrim itself. Bsod again, with same glitches.

I'm also experiencing random freezes with the Radeon host application stopped working (TDR)


I ran Whocrashed an here's the report:


I know that it has little to do with the game itself, but its the one that triggers the BSOD


Recently, before these problems started I bought 2 RAM sticks, just about a month ago, but I ran MEMtestx86 V4 edition 4 passes and it showed not errors at all



I also run Furmark for about 10 minutes without any errors

Heaven benchmark 1080 max everything , no errors nor glitches

I didn't do any overclock, never, and I've got this PC since 2010 so it's a bit old, but the GPU is from 2013


FULL specifications:


Youtube Glitches examples

Google Maps




I wouldn't declare my GPU dying since I fully tested it with furmark and Heaven Bench, plus another Vram test software (Video Ram stress test).

GPU Temps are around 72C on full load and 30C IDLE
Never Overclocked anything... fearing that something like this would happen

Due to the random nature of this issues I can't reproduce the BSOD's, And all this problems started 2 weeks ago,

Many thanks for your help, (sevenforums and AMD support forums couldn't lend me a hand)
Reply to ChrisCamm
15 answers Last reply
More about random bsod x0124 graphic glitches tdr games skyrim total war youtube videos google maps
  1. Bump
    Reply to ChrisCamm
  2. bugcheck 0x124 with parameter 1=0 is generally a power problem. Too much power being pulled from the PCI/e bus. (can be caused by GPU overclock, overheating of a GPU) Generally, someone can look the the actual memory dump file and get an idea why it shutdown.
    Reply to johnbl
  3. How can i post the memory dump?
    Besides, i never overclocked anything. And my power supply is a Thermaltake 500wts
    Reply to ChrisCamm
  4. you would copy the files from c:\windows\minidump directory to a server like google docs, mediafire or microsoft onedrive, mark the files as public and then post a link here.

    graphics cards get power from two sources, one from a power supply connector to the GPU and the rest from the graphics slot. if the GPU pulls too much power from the graphics slot a good motherboard will reset your CPU. a crappy motherboard will just let your GPU and graphic slot catch fire.

    older gpu can get dust build up that slows down the fan and causes overheating.
    make sure your fan is spinning and blow the dust out.

    ChrisCamm said:
    How can i post the memory dump?
    Besides, i never overclocked anything. And my power supply is a Thermaltake 500wts
    Reply to johnbl
  5. https://www.dropbox.com/s/z6e1x40my7uuslb/CHRIS-PC-09_03_2017_131748%2C80.zip?dl=0

    I know that im posting this issue in the middle of new GTX craze, but i cannot easily afford a new one.

    Thanks for helping me!

    Edit: Temps seem to be ok, like 30ºc while idle and 72ºc on full load (running Furmark, on games it doesnt reach 60ºc)ç
    And Tdr's also happen using online Googlemaps 3d, and that's not an intensive software
    Reply to ChrisCamm
  6. basically it looks like your system had a power problem the motherboard reset the CPU. The power supply should keep the CPU reset until the power is stable but it did not. It let the CPU restart while the power was not stable. The CPU started rebooting but then got an internal error on its bus this cause the CPU to call the bugcheck 0x124 and shutdown and produce the memory dump.

    the total system uptime was 7 seconds,
    the internal error was
    Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
    (error reading from cpu core 0 from cache memory bank 4)

    this is pretty common with some power supplies that fake the power_OK signal to the motherboard.

    you would have to find the cause of the initial reset of the CPU and you will avoid this secondary symptom of the bugcheck.

    since this was a panic bugcheck during boot, there is very little info in the memory dump that is useful, I can not read your BIOS info or your hardware info but you are running a very old build and you have a very old driver for your ATI PCIE Driver. AtiPcie.sys Tue May 5 08:00:22 2009

    normally, you would want to update your BIOS and all of your motherboard drivers to the most current version you can get. if this is a old machine you might find the cooling fans in the CPU, GPU, or the power supply are not working. You might even consider underclocking your GPU to get past the problem. Be sure to look for updated AMD chipset drivers and to update or reset the BIOS back to defaults and reconfigure. (do not overclock the PCI/e bus)
    Reply to johnbl
  7. Do you think that the graphical artifacts and TDR's are related to it?

    Fans are working, (monitoring them with Speed Fan)
    I opened the case also and they seem to be working fine


    Or do I just have to update bios and wait?
    Reply to ChrisCamm
  8. - overall, update the BIOS and drivers from the motherboard vendor
    if you still have graphics artifacts you can apply heat or cooling to see if a chip is not properly connected

    graphics artifacts tend to be overheating problem, or chip legs that have become detached from the graphics board.
    The chips legs can make contact, heat up and break contact some of the older GPU used the first generation of the new lead free solder and the solder can be brittle and the connection can break away from the solder pad.

    you can get the TDR timeouts for various reasons also, the graphics timeout is short, I think it is 2 seconds but I have seen graphics cards get the timeouts because they were blocked by a slow USB device on a 30 second timeout.
    generally, these were bugs in BIOS or old usb drivers (mostly some of the first generation USB 3 drivers before about march of 2013 or old usb 2.x driver before first march of 2012 (dates when the specifications for usb changed)
    the drivers for sata and USB 2 or usb 3 are tied to your motherboard bios date, so update them together)

    ChrisCamm said:
    Do you think that the graphical artifacts and TDR's are related to it?

    Fans are working, (monitoring them with Speed Fan)
    I opened the case also and they seem to be working fine


    Or do I just have to update bios and wait?

    Reply to johnbl
  9. All I can do is update Bios?

    How can I do without bricking it?

    Im not a tech savy, that's why I make all these noobish questions
    Reply to ChrisCamm
  10. Go to the ASUS site. Looks like you're 2 BIOS updates behind. Download BIOS 2104.

    Extract it put it on a flash drive, go into the BIOS find ez flash select it. Point it to the flash drive. Wait for it to finish. Reboot

    https://www.asus.com/nz/Motherboards/M4A785TDM_EVO/HelpDesk_Download/
    Reply to Paul NZ
  11. Is there a way to confirm visually those detached or burnt chip legs?
    Reply to ChrisCamm
  12. most of the time you have to isolate the bad connection location using a heat gun or a can of compressed air.
    Then take off the heat sinks and do a visual inspection using a stereoscope so you can see the crack.
    If you can find it you might be able to repair it. Most of the time it is too hard to find and will be under a heat sink. It could even be a different component on the card. The age of the electronics also has to be factored in as to what you look for. Each piece of the electronics has a different failure rate and expected lifespan. I have a old viewsonic monitor on my old xbox, It will not turn on until it gets to about 78 degrees. I just put a heater behind it, heat it up for a few minutes before I try to turn it on and it works. Just too lazy to tear the old monitor apart and fix the bad connection and have not wanted to go out and buy another monitor.


    ChrisCamm said:
    Is there a way to confirm visually those detached or burnt chip legs?
    Reply to johnbl
  13. johnbl said:
    most of the time you have to isolate the bad connection location using a heat gun or a can of compressed air.
    Then take off the heat sinks and do a visual inspection using a stereoscope so you can see the crack.
    If you can find it you might be able to repair it. Most of the time it is too hard to find and will be under a heat sink. It could even be a different component on the card. The age of the electronics also has to be factored in as to what you look for. Each piece of the electronics has a different failure rate and expected lifespan. I have a old viewsonic monitor on my old xbox, It will not turn on until it gets to about 78 degrees. I just put a heater behind it, heat it up for a few minutes before I try to turn it on and it works. Just too lazy to tear the old monitor apart and fix the bad connection and have not wanted to go out and buy another monitor.


    ChrisCamm said:
    Is there a way to confirm visually those detached or burnt chip legs?



    I didnt knew how fancy electronics could be

    Even if I don't find a way to solve my issue, you lend me a hand.
    Thank you for sharing such knowledge!

    Tomorrow I will try updating my BIOS, then switching to onboard graphic, to see if it works
    Reply to ChrisCamm
  14. Today it crashed again, same error:

    On Thu 23/03/2017 20:00:21 your computer crashed
    crash dump file: C:\Windows\Minidump\032317-38220-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x4AD47C)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA8008094038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    This time I think I can reproduce the crash: Google Maps on mozilla with hardware acceleration off.

    Im giving up, it's time to bury this 7750 once for all.

    Any recomendations of GPU based on my sistem described above? I'd like the same specs, nothing too fancy and cheap, without underperforming my actual card


    Promise it's my last post
    Reply to ChrisCamm
  15. Did you update the bios
    Reply to Paul NZ
Ask a new question Answer

Read More

Blue Screen Skyrim