Tracking down bad RAM can often take more than a handful of passes unfortunately, but that's seldom the issue anyway frankly so it's probably best to move on to trying other avenues, at least until that becomes a last resort if nothing else fixes it. This PROCESS_NAME interested me as it used to be as System It appears more often during normal work like browsing the web, coding, watching movies etc.Īlso got a BSOD during writing this post, GPU was exactly 45C then. it's funny as I'm playing games quite often and the BSOD rarely throws during gaming. CPU ~34C (don't know what's "Core n Distance to TjMax" but it shows about 66C for all 4 cores)ītw. However looking on HWiNFO and temperatures look quite good: Cleaned precisely as far as I could with canned air (didn't put new thermalpaste though as forgot to buy one) and unfortunately it didn't help. About overclocking - If I remember correctly, I didn't do any overclocking on GPU nor on CPU however will check in BIOS and restore to defaults to be sure.Ībout cleaning the PC - I did it few months ago after BSOD case appeared. I'm still interested in any help as bsods still throw, last one at Sunday though. Please disregard if someone else has more knowledge about analyzing crashes and can offer better advice, these are just a few ideas I would likely try if it were my system. You could also take the system to a PC repair shop or knowledgeable friend or family member if they are familiar with building and repairing PC's. With the system being a few years old then it may require a new application of thermal paste for the CPU and/or GPU if either component is overheating (you want your GPU in the low 80's C or lower and your CPU well under 100C, ideally low 70's C or lower though it can run up to 100+ C without throttling/crashing from heat), however if you are not familiar with doing so then I wouldn't advise attempting it, but if you are then it might help. ![]() You should also check your temperatures with a tool such as HWiNFO to see what kinds of temps your components are running at. If that doesn't help, try shutting down the system, turning off the power, unplugging it from the wall and turn the switch on the power supply to the off position, then open your computer case and remove your graphics card and check it for dust, hair and any other debris that might have collected in the fan(s) and air flow channels on the card, and if it is badly clogged up, try cleaning it carefully using canned air if you have any along with a tool to dig debris out of the fans and other spots you can easily reach (again, carefully, without damaging the card) such as a Q-tip, pen, or screwdriver just don't pry into anything or use any real force so that you avoid damaging your card. If you are overclocking your GPU, please restore it to default clocks. I'm not knowledgeable when it comes to reading crash reports and BSOD's, however I am aware of some issues with overclocking and the error you describe, and from the sound of it, this could be related to your graphics card since those are NVIDIA filenames listed by WinDbg. If you are still seeking assistance I'll do my best to help. I'm sorry that no one has responded to your topic yet. Tried to attach zip from SysnativeBSOD but it goes into a loop with "waiting for SystemInfo - Specified service does not exist as installed service" error GPU - Zotac GeForce GTX1070 AMP Edition 8GB GDDR5 (256 bit) OS - Windows 10 64bit (Installed by myself)Īge of OS installation might be like 2 years but that's just guessing. ![]() If memory dmp will be useful I can upload it somewhere too Sharing those 16 minidumps in attachments as zip. I have like 16 minidumps and one memory dump of 1.3GB size. I was also searching for solution by FAILURE_BUCKET_ID which is ZEROED_STACK_0x133, 0x133_ISR_nvlddmkm!unknown_function and once it was 0x133_ISR_nt!KeAccumulateTicks but also couldn't find anything that helped I couldn't find any relation between BSODs - they appears in random moments for me. Ah, before BSOD whole system freezes for like 30 seconds to minute. Once I was checking minidumps with WhoCrashed program which said it's a problem with ntoskrnl.exe. Previously there were some situations where PC freezed for like minute and then unfreezed without any BSOD but audio driver crashed and I had no sound (until just restarting it in device manager). ![]() Last time it was ntkrnlmp.exe which was something new but still couldn't get the solution for that. WinDbg says randomly the problem is with either nvlddmkm or unknown_module. I tried anything I could with my knowledge but nothing helped. It used to be thrown like once per couple of days, now it's almost everyday. I got a problem with BSOD with DPC_WATCHDOG_VIOLATION code since like half a year or more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |