Grimmkyu

While checking event viewer periodically I noticed this event from ESENT in warnings " SettingSyncHost (2372) {CDF7FF77-25B9-4C7A-9FAA-875499EC5006}: A request to write to the file "C:\Users\Owner\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\meta.edb" at offset 1032192 (0x00000000000fc000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (16 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for " this is the first time I've ever noticed it and the first time it's ever happened. I've not noticed any strange behavior or lack of performance in any way at all and even around the exact time of this error. I only knew of the warning by me simply checking logs like I always do. I've ran sfc /scannow, CrystalDiskInfo, HDDTune Pro, and the SanDisk SSD utility from their site for my SanDisk SSD. No errors were uncovered but the "This problem is likely due to faulty hardware." line has got me worried. I have no idea what's going on or if it's from my SSD or windows. What should i do? Is this basically saying my SSD is on its way out? Is windiwe corrupt? Is the update being weird? Any help appreciated!

While checking event viewer periodically I noticed this event from ESENT in warnings " SettingSyncHost (2372) {CDF7FF77-25B9-4C7A-9FAA-875499EC5006}: A request to write to the file "C:\Users\Owner\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\meta.edb" at offset 1032192 (0x00000000000fc000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (16 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for " this is the first time I've ever noticed it and the first time it's ever happened. I've not noticed any strange behavior or lack of performance in any way at all and even around the exact time of this error. I only knew of the warning by me simply checking logs like I always do. I've ran sfc /scannow, CrystalDiskInfo, HDDTune Pro, and the SanDisk SSD utility from their site for my SanDisk SSD. No errors were uncovered but the "This problem is likely due to faulty hardware." line has got me worried. I have no idea what's going on or if it's from my SSD or windows. What should i do? Is this basically saying my SSD is on its way out? Is windiwe corrupt? Is the update being weird? Any help appreciated!

I just noticed I hear a semi audible hissing sound come from one of my fans for a split second as the reading goes whack. Maybe a coincidence but idk I also installed hwmonitor and it also gives the same odd readings too. When I get home later I'll check speed in the BIOS, but it's got me worried now

ack, running on my Asrock Fatal1ty mobo with Killer Networking Suite network drivers- when I attempted to uninstall the suite program as I felt it had no use at all, upon reaching a certain file of uninstallation my PC would go black and restart on its own suddenly. Eventually I got tired of trying to uninstall so I let it be. One day however I attempted to play Black Desert online for the first time, and upon loading the game as soon as the anticheat finishes loading my screen would go black and restart. I downgraded from Windows 10 to 7 and tried the same game, works like a charm! Then eventually wanted to go back to 10 and when i finished upgrading my OS and reinstalling the game it worked fine. i was still slightly paranoid and looked up the symptoms online to find a lot of posts on Tom's Hardware and other sites stating its usually a PSU issue not delivering enough. Because the game worked after reinstalling and everything else has been fine, too. Am I safe to say that it may have been attributed to corrupt OS, drivers, etc, stuff other than my hardware? Running memory tests found no issues, and prime95/fur mark pushes my gpu/CPU like crazy but temps are definitely safe. Just trying to figure out why it might have restarted like that.

True- My cpu voltage fluctuates between 1.2-1.350 or so. Is that okay then?

Yeah, maybe so. Not as technically versed as some others, haha. I just came here to confirm whether or not that was a normal reading to see.

Oh really? I was playing WoW when I saw it pop up so I shouldn't worry bout it? Slightly freaked me out thanks to reading some comments by others suggesting it was only 4-6 and mine was 3-4 times that. Thanks!

I know this is an odd question, but monitoring my HWInfo a hidden value (I guess) of "CPU:" popped up, saying "CPU: 15.938A" and then inexplicably vanished o.O. Looking up how many amps computers draw some have been as high as 47 and some have said 4-6? I'm confused. I use an EVGA SuperNova P2 650w PSU and an Intel i7-6700k processor non-overclocked. Mainly strange the sensor doesn't exist until randomly, but when it does, it's greyed out and I assume the 15.938 A stand for Amps. I could be wrong?

Yeah the only reason it freaked me out is because after owning my PC for 3 months it suddenly gave readings like that, that I haven't yet seen happen before hence the worry, haha. So I should just let it go and forget about it? I appreciate your response very much!

Hi there guys. I've been keeping hwinfo up typically when playing games and using my computer to monitor temps/voltages and in general to observe system info. Today it started storming when I was away from my PC, and the lights flickered a few times so I went to turn off my system in event of a surge when I noticed that the fan readings said case fan 1 and 2 (my only fans besides CPU cooler) had jumped to a maximum of 45000 and 40909 rpm. Obviously realistic and I'm certain they would have broken at such a speed. I rebooted my PC after the storm and when observing it typically stays around 800-1400rpm on load but with no actual change in fan speed, sound, or component temperature the readings will say the maximum jumped to 30-45k RPM. Makes me slightly concerned considering I never noticed this until after my lights flickered. My CPU fan stays totally normal though. I haven't checked anything other than hwinfos reading admittedly but it slightly worries me thinking maybe my PC was surged and the fan sensor was taken out? Should I worry at all or just let it be? Is there some way to diagnose component failure just in case? Or maybe I'm just being paranoid.Nonetheless I know it's an atypical thread but I'm still new to having a strong gaming PC and I can't replace it if it breaks so I want to be sure everything is spiffy. Thank you sincerely whomever responds!

The only errors were the standard Kernel41 errors that I can find. Some other errors happen at the exact same time but none are the exact same each time I replicated the issue.

The only errors were the standard Kernel41 errors that I can find. Some other errors happen at the exact same time but none are the exact same each time I replicated the issue.

Hi random issue I know but I have a question concerning the title. So a while ago I tried to uninstall Killer Network Suite, and when it would reach a certain part of uninstallation, the computer would suddenly go black and reset. Under a light load mind you. I thought it was the uninstallation until when attempting to load Black Desert Online for the first time, as soon as the anticheat would load, boom black screen reboot. At first after looking it up I thought it was a PSU issue, cause the game is demanding, right? Well when I did a system recovery completely redoing Windows 10 the game would load normally and no issues whatsoever. I've tested the RAM, no errors. Both installations were on SSDs both during the failure/successful boots of the game, and my CPU and GPU are fine. I haven't tried to uninstall killer network anymore just in case. But what are the chances that the reboots under those conditions could be started by corrupt drivers, OS, or an update that had hit before that? Would be comforting to know without a doubt my hardware is okay if possible.

So even though I felt an electric pulsing (100-120hz I would guess) it should be okay? Like I said I haven't felt it in over a month since the one time I checked for the first but it still worried me that maybe it was intermittently doing that. Thank you for your help very much. Eases the mind of a PC gamer who can't afford to lose his PC ^^;

I'm not sure. I can't tell as I'm writing this from work on one of my breaks. Would that be a likely cause then if it was touching it? And in that circumstance could that spawn an issue?