Jump to content

SM Phoo

Member
  • Posts

    150
  • 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. I tried to cover everything and forgot these details. We reapplied Thermal paste and checked all temps. When playing games, it sat nicely at 50-60 consistently. I even ran Prime95 on it and it didn't go crazy. He uses a Kraken Z73 One thing he just mentioned, when he turned it on yesterday, the LED screen of the cooler displays the current temps. First boot it cut out at 40, then each time he tried to turn it back on (This is straight after it cuts out) it seemed to creep up an extra 5 or so, so really, it's nowhere near a critical temp Yes, forgot some details. We did reapply thermal paste around 6 months ago. We used the grizzly kryonaut. The fans themselves are quite clean. We even used a pc blower to give the whole pc a blast to get rid of any dust. Such a weird problem as it's very intermittent, which suggests everything is fine. It just has a blip every now an then. It's a water cooler btw, and the fans do spin, and the pump is pumping
  2. Hi guys, writing this topic on behalf of a friend. We build him a PC when the 3080 released, so around 3-4 years ago. For the first year or so, the PC ran totally fine, but for the last 2 it's had a very unusual problem. So to get the specs out of the way first, he has a: 3080 Founders - 32gb - Ryzen 7 5800x - MSI B550 (Don't know the exact model) We're both at work today so I don't have the pc in front of me, so I will do my very best to give every detail. So what happens is, and it's probably a 1 a month thing is, my friend will boot his PC up and it will load to windows normally, but the fans will kick in really hard from the off and after around 10 minutes or so of just been inactive on the windows screen, the PC will shut down. When he then boots it up, before it even gets to the bios, he gets a white box with a warning saying CPU OVERHEATING ALERT. PLEASE CHECK CPU COOLER IS FIRMLY ATTACHED. This cycle will happen over and over when he tries to boot up the machine. If he leaves the PC for around 5 minutes before booting up, it will load further into the startup, but will still shut down. This cycle will continue, unless he leaves the PC for around 2 hours, then it will boot up normal and work. He uses the PC daily for gaming, and usually has stints of around 3-5 hours each day, so when it works, it works fine, but as said at the beginning of this, this error seems to crop up once a month, sometimes he wont see it for two months or so, so not really sure whats going on. Also, we live in the UK, so it's not very hot where we are, so the ambient temp definitely isn't an issue. Any help, or questions will be appreciated to try and solve this. Thank you
  3. @Okutida I am now away until after Christmas, so I wont be able to test anymore until then sorry, but it's been perfect for over a week, so I am hopeful. Definitely give it a go and let me know if it solves your issue also
  4. @Okutida Hey, I dunno if you're still encountering the same problem, but I think I've finally got to the bottom of mine... I hope. I had to update my audio driver from the motherboard manufacturer. Whenever I did searches, people did say a bad audio driver, but I just assumed windows always found the newest drivers. Apparently not always, especially when it comes to audio. I've not had a single crash since, and I've really tried to push the system to have one, so I am somewhat confident I may have sorted mine
  5. @Okutida The most frustrating thing for me is everytime I think I narrow it down to a cause, it surprises me. Today, I was able to borrow a GPU for the weekend, so hardware testing was the plan. I first loaded up Apex as yesterday it was being consistent with the crashing, and it crashed almost instantly, so that was a good thing as it gave me some consistency to work with. My first test was checking the cablemods cable. So I ran Apex again, it crashed after 2minutes, great, consistency. So I unhooked the cablemod extension cable, plugged in the standard, ran apex and it was running fine for around 15minutes. Fantastic, I think I've found the cause, but I want to make sure, so I hook up the extension again, ran the game, crashed quickly, so finally I think I've narrowed it down. I'll try again just to really confirm what I think is the problem... This time, the game ran fine for 30mins. I do a restart, test again, runs fine, so now I am back to not knowing. The crash is so inconsistent it's hard to even test. I only have the GPU for the weekend, but if I cant replicate the crashing consistently enough, it's hard to pin down a cause
  6. Just a quick update, after being posting this, I loaded the game up, got in fine, went to the shooting range, was in there for about a minute and the PC shut down
  7. Hey guys, so unfortunately I am back here, again, with this same error that is just destroying my soul day by day. So long story short, this has been plaguing me for around 4-5months, on and off. I've tried numerous software fixes, like updating the bios, removing XMP, updating all drivers, complete clean install of windows, memtest64, stress testing the CPU, GPU and PSU (All passed fine) but whatever I do, nothing has worked so far.... so I am going to leave that and just talk about the last week or so. The last thing I tried to do, to sort this problem, was turn off quick startup. For the last week or so, it's actually appeared to work, until today. I've played Skyrim and Halo for the last week or so, but today, after playing Skyrim for an hour, I decided to load up Apex. For anyone familiar with that game, it loads up, and you get a screen were you hit continue and it takes you into menu page, where you can pick game mode etc, anyway, as soon as it loaded into the menu section, my pc turned off. I repeated the same thing on 4 or so occasions and got the same result each time. I had another quick look online, somebody suggested loading up in safemode, using DDU to remove all GPU drivers, so I did all that, as well as resetting all bios settings, which removes any xmp overclock and loaded back into windows. I opened Apex, and the same thing happened. At this point, I felt like, the only thing I can try now is hardware trouble shooting. The only thing I can really test right now is the memory. So I took two sticks out, loaded apex and it crashed. So I switched out the memory for the other two sticks, tried again, and it worked!!! Hallelujah, but I wanted to make sure, so I swapped out the memory again, and it worked... So 2 sticks worked, and the other 2 sticks worked, so I tried all 4 at the same time... worked. It loaded in. So I messed around in the shooting range for about 20minutes, then I wanted to tab out to check something and the pc switched off...., so I decided to just try again, so when windows logged in, I opened apex, and crashed, at the same point.. The thing is, if I load up apex, but leave it on the loading page, and don't hit continue, it doesn't crash. So, as of today, I am blaming Apex, but in the passed, it could just be random times, but today, it just feels like Apex triggers it.... sometimes, or more times than not anyway. So I want to clear a few things up. The GPU, PSU and CPU were brand new. The ram and Mobo were bought used. Both the CPU (Monoblock) and GPU are custom watercooled (hence not really easy to just test other parts) The GPU uses a riser cable (PCIE 3.0, So I've gone into bios and ran PCIE slot in gen 3) The CPU, Mobo and GPU have custom extended sleeves from cablemods When I load into most games, my PSU does make a wining noise, which apparently seems normal (I will add a video were you can hear the PSU when in game and when I tab out) When taking the ram out, it is quite warm/hot to touch. Not hot that I cannot handle it, but it it is warm, I assume this is normal but I wanted to mention it anyway When the system turns off, the Mobo RGB stays on, but the PC wont turn back on, I need to turn off the PSU, wait until all power has left the mobo and then turn it back on This is the sysnative BSOD app results: https://drive.google.com/drive/folders/1rexxEKgWHrcqdXTPbnKVfHrhtf64TBed?usp=sharing I also ran the resource and performance monitor, but it doesn't actually do anything, it's just stuck on the 60 seconds screen. I know, testing new hardware is probably the only solution at this point, but if anyone can look at the files and find something that may cause this, it would be awesome! One thing I was thinking may have caused the crashes was the anticheat software that some games require, which would explain most of the crashing today, but not other days So, sorry for the long post, but I wanted to provide as much info as possible clicking continue then psu turning off.mp4 tab in and out of game.mp4
  8. Hey, sorry for the late replay, I didn't get a notification. So, no. (hence logging in) My PC has worked perfectly for over a week, so I thought turning on quick startup worked. For the last week or so I've been playing Skyrim, but today, after an hour or so on it, I decided to load up Apex and I got the crash. Restarted the PC, loaded up again, crash. Did this about 8 times in total, all resulting in crashes... Then it decides to work, so I messed around in the shooting range for a while, tabbed out.... crash
  9. Hey Not done it yet. So far so good for me turning fast boot off. Had my PC on for around 3 hours, sometiems restarting to see if I could force the problem, but nothing. Went back on later and played 3 hours of Apex fine. I don't think this is the solution I am looking for, but I only want to test one thing at a time, so, for now, turning fast boot off is working. Changing ram frequencies will be next on the list though
  10. You'll need to start by going to event viewer > windows logs > system and post your critical errors.
  11. I could try that again. I did actually lower my speeds to 3200 and from what I remember, I do think it worked (I cant fully remember though!) When I did my clean wipe of windows, I did actually take it back to 3600 and did a memtest and it cleared, so I just left it. Worth trying again though!
  12. I've been plagued with this error for a good few months now, and also at my witts end! I formatted my machine around 3 weeks ago, and everything seemed good, up until 4 days ago and now it's back, which screams software, but I just don't think it is. I've not done any hardware changes because my system is watercooled, so it's hard to just swap out parts. I mostly get the error when I wake from sleep or when the PC has just turned on, although it can happy at other points. I'm starting to troubleshoot the hardware side of things soon, so I'll see if that comes up with anything. I did a full memtest which came back clear. Ran stress tests on the CPU, GPU and PSU and had no crashes, so I feel I've tested them well enough. As of last night, I turned off quick startup, and so far so good, but I'm not filled with confidence. When I look into the crash reports, even though it's a kernal issue, it seems to do with Nvidia, so I think it's the GPU, so my next 3 options are: I use a riser cable so it could be that. I use custom extension cables for cablemod, so could be that. It could be a faulty GPU Today I am lucky enough to borrow another GPU, so I will connect that up, which will negate the rise cable, extension cable and GPU, and if I get no errors, I know it's one of them
  13. Hey guys, so this error has been plaguing me for a few months now. I'd get random freezes. The error actually used to be VIDEO_TDR_FAILURE (116), but that sort of fixed itself, but I also did remove a GPU overclock, but then I started getting a Kernel 41 error. After trying so many things, I decided to do a complete reset of everything. So, I did a complete fresh install of windows. I updated all drivers, through windows update, and everything seemed fine, up until a few days ago. I also updated the bios to the latest stable update. So, this error seems to crop up once I wake the machine from sleep. The computer will just reset, and the problem is, when it boots back up, less than a minute into windows, it will reset again, and again, and again... If I do a hard reset on it, fine, everything seems to work as normal, but as soon as I let it go into sleep mode, as long as I give it enough time, same thing happens again. So, things I've done to try and troubleshoot this. I ran memtest and that all came back clear I did some intensive tests on the GPU, CPU and PSU and the system was stable throughout. As my system is watercooled, is there anything I can do to test further, without trying to test the hardware which is going to be a bit of a pain without taking it all apart. Is there a way to test the mobo etc... I'm not at the PC right now, but the only change to the system since the crashes was I installed Lian Li L Connect software. Googling doesn't really bring any links between the error and the software. As of right now as I am not at the PC, I cannot do the Sysnative BSOD Dump, but I assume the file is similar if not the same as what you're asking for: https://drive.google.com/file/d/11W1hNYfGzhc7i8CGtRiqS-0iGIEAGU-b/view?usp=sharing Any help or suggestions will be massively appreciated right now. I am off to bed, but I will check back tomorrow morning. Thank you Info you require: OS - Windows 10 64bit Full retail Less than a year old (Mobo and memory were bought used off ebay, so not sure of age) Age of OS installation - 2-3weeks 5950x 3080fe Asus Rog X570-F Seasonic either 1200 or 1300w, gold, Can't remember which exactly Desktop
  14. Hey guys, so, sometimes when I boot up my pc, after 2 or so minutes of being on, it will freeze up. I tend to either get a complete freeze, or it will reboot back up. Once the lock up has happened and I reboot the machine, it runs without a problem. These freezes don't happen every day either. More 1, sometimes pushing twice a week After looking at the event viewer and running a dump checker, these are my results. The Big dump file is in C > Windows and is about 1.5gb The most recent file is in c > windows > minidump and is about 3mb A few things I can say to help with any solution. 1. GPU is a 3080fe 2. I have watercooled it 3. Its in a PCIE-4 board with a PCIE-3 riser cable, but I have changed the bios to run it at PCIE-3 4. It's not overlocked. I had overclocked it, and I thought that was causing the problem 5. Driver is fully up to date I also gave the machine a fresh install a few months ago Any help from you guys would be much appreciated. Thanks! big dump.txt most recent.txt
  15. Hey guys, I have a project I'm thinking of starting and I'd like to add a screen to it. (PC tower). I had a faulty port dvd player and removed the screen, but I'm not sure how it'd be powered or hooked up to the pc. I've looked at LCD controller boards, which seems like a step in the direction, but I'm not sure exactly what I'd need, or if it'd even be possible. Here are the connections. Any advice would be greatly appreciated
×