A1Mike_W

Still very insightful and allows me to clarify my points, thank you. Performing digital forensics after an attack is impossible unless data has been captured to begin with (since you can't capture data of an event that has passed, like taking a picture of something that already happened) - from what i understand, data capture happens continuously - and so the act of finding evidence would fall under the analysis stage of the whole process. Here I'm asking about the process for capturing the data that can be analysed to use as evidence if an incident occurs. More angled towards what logs what and where. So for example: – Cloud Platform – VM deployment, migration, state of network – Server / hypervisor – VM scheduling, provisioning, resource consumption – User access – who, when, how where, accessed what, etc. I'm asking about data logging and other methods of obtaining forensic data, if any.

Hey all, I'm looking to further my knowledge and learn something new but have been struggling to find/understand two topics that seem in-line with this thread. I've been looking into digital forensics and cloud forensics but I'm struggling with the following: What are some sources of forensic information in networks and what are the collection processes involved? And the same for cloud networks - how does network data collection differ in a cloud environment? Aside from legal issues with jurisdiction that are easy enough to find, I'm more angling towards technical and organisational points of view that are best understood from a provider perspective. I would also appreciate any info on threats that are specific to cloud environments - stuff like hyperjacking I'm familiar with, but I would love to hear about others. Thanks in advance, and I look forward to hearing from you

Didn't work, but that's a useful shortcut. Thanks @Faisal A Yeah that's what I tried, didn't help at all unfortunately. Like I said, the problem exists even when the only cable plugged in is the power cable, so I suspect the panel is dying rather than a faulty connection/wrong settings. Thanks for the suggestions anyway

@Faisal A Thank you. Just tried it, still nothing. Is the monitor bust then?

Thanks for the suggestions guys. I reset pixel clock and played around with refresh rates. The effect is worst at 144hz, gets better at 100, best (though still not great) at 60hz, and goes downhill again below 60. Messing with the pixel clock manually does not yield better results, but then again I'm no expert. What's this auto adjust? Sucks considering I've only had it under 1.5 years, but I've already got a new one coming so I'm more hoping to get this one in good shape before I sell it on.

Hey guys, The top of my screen seems to overlap the bottom, with some of the bottom overlapping that as well. It's confusing when I explain it so I'll just link a video. I am not covered under warranty so my best attempt would be to fix it myself or sell it to someone who can. I checked if any data cables are loose but they seem fine. Anyone have suggestions on what it could be? It's not resolution/framerate/anything specific, it happens from the moment the monitor is turned on even when not plugged in to anything. Thanks in advance.

What happened to this? ? As for legit case suggestions, I'd recommend giving the gamersnexus chart a glance. The noise and temp graphs really help in choosing a case above all the gimmicky stuff. (https://www.gamersnexus.net/guides/3397-best-and-worst-pc-cases-of-2018) Most cases are dust RESISTANT nowadays, but there's nothing dust-proof so you'd have to give it a clean every few months at least.

No matter the multiplier set, the BCLK is unstable past 100.25. It just irks me that out of the box it could hold 100mhz but now setting it to 100mhz only gets 99.6. I know the performance loss is negligible but my OCD really doesn't agree with it. it's not completely bricked and still works fine with overclocking the rest of the system, I've just never had BCLK behave like this so I just wanted to use it as a learning point really. Thanks for all your advice

Clearing cmos and bios updates haven't fixed anything unfortunately. I'm not blaming any part in my system. I'm not trying to get a refund or a replacement, and I'm well aware my actions are likely the cause of the problems I'm seeing. I just wanted to know where I went wrong so I could avoid it in the future or better yet fix it. I haven't set unsafe voltages anywhere, my temps were in check, and I was under the impression that setting the clock speed of anything too high would be very unlikely to damage or brick it. Is it still possible that I have damaged the motherboard simply by setting a speed too high?

I'm not doing it for the performance ? I just like playing with numbers. It physically bothers me that I'm now unable to even reach stock speeds now. Besides, it might indicate a bigger problem which is why I want to get to the bottom of it.

It helps me see just how far I can push the CPU and RAM speeds. Going at 100mhz steps isn't optimal. Imagine overclocking your GPU but you could only go 100mhz either way. I'm p sure on lga 1151 cpu's it only affects CPU and RAM speeds. When fine-tuning my CPU overclock I'll underclock RAM by however much the BCLK would OC it, etc etc. Resetting to optimised defaults didn't fix the problem I'm having. My BCLK refuses to hit 100mhz and setting it anything past 100.25 (which wouldnt even make up for the 0.4 drop) makes the system power off before it boots. Voltages are set to stock (except for vcore), and increasing them does not help with stability.

Just a disclaimer for anyone that gets the same idea as my cousin, pure water isn't "safe" to use on electronics. It'll pick up ions from whatever it's on and become conductive really quickly.

I've got a gigabyte z370 Aorus ultra gaming mobo with an i5 9600k. The BCLK for my system is completely whack. When I first assembled it, the system was at 100.2 BCLK which is within margin of error and not an issue. I've tried overclocking the BCLK but every failed attempt drops the stable BCLK. At this point if I set BCLK to the stock 100 i'll get 99.6 actual, and this drops with every unsuccessful OC. I haven't been playing around with extreme voltage and all of my temps are in check. If I set BCLK past 100.25 and try to boot, the system turns off immediately and will keep turning off the moment it starts to boot. I used to be able to boot in with BCLK set to 102.7 but with failed OC attempts (not increasing voltage, only speed) that value dropped down to 100.25. After a few failed cycles it'll load in BIOS @ whatever the BCLK was set to but vcore will also shoot up to 1.45v-1.5v from stock (or whatever I actually had it set to). I don't let it load windows at that voltage just because it'll likely fry my chip. The BCLK bug appears despite what speed I set my memory and CPU to. I can underclock both while overclocking the BCLK and the same thing happens no matter if I'm at 4.9ghz on my CPU or if I'm at 3.6ghz. My BCLK is being picky for some reason and something I'm doing is wearing it down to the point where it's unable to stick to the stock 100mhz setting anymore, but I have no clue what it could be as I've never had this problem before. Any idea what it could be?

Resin and paint will cover most of it up if you're not too picky (or if you're skilled enough to make it look good), but honestly it'd be cheaper and easier to get a replacement set. Sounds like you enjoy aesthetics anyway so it should be right up your alley Individual keys are out there for sale (https://www.ebay.co.uk/i/323454828401?chn=ps) but at £4 per key (when a full set is £15-30ish) it isn't really worth it.

The reset functionality wouldn't work either. Languages would randomly swap and function keys were unresponsive so it was impossible to reset. It was really bizarre and reached a point where most keys wouldn't work anymore so my problem actually got worse than what I described. Changing USB ports or updating firmware did nothing. Restarting would fix the issue for a minute or so but that's about it. It also has a plastic cover on the inside to prevent shorts, so the problem persisted with the case off. PCB is pristine, but I went over the whole PCB with alcohol and took a bunch of tiny solder specks off that my previous cleaning missed. Still, that did nothing to help me. The stupid thing is, this problem had the easiest fix (which I still don't fully understand). I just plugged it into a different PC for a few mins. That's it. Problem solved. Haven't had the problem on any PC since. I say it's stupid because I have no idea if there's an actual problem with something and would like to find out before it gets worse, but I've never encountered anything like this so I'm clueless. I guess my issue is fixed but I welcome any and all insight into the matter ? Edit: I jinxed it. I'll have to wait until morning before I can get access to a different PC and see if that still works.

I changed the keyswitches on my Vortex Vibe, not my first rodeo and no accidents happened. All the keys work fine and they are not shorting out but for some reason the features of the keyboard don't work 90% of the time. Stuff like changing layers or layouts using the keyboard shortcuts in the manual might show the LED change so the keyboard knows what's happening but it won't actually change anything. Another problem that keeps popping up is randomly a modifier key will get stuck (like ctrl or alt) and it remains stuck on individual applications. For example the ctrl key will get stuck on my browser so if I press the ctrl key while tabbed into the browser it'll go away and behave as normal, HOWEVER if I then go to my desktop the PC still thinks I'm pressing ctrl even though the browser already knows I'm not. I tried plugging a different keyboard in and the issue disappeared after a restart as long as the Vortex Vibe was unplugged. Is there any chance these issues are related to drivers or maybe a corrupt OS rather than a hardware problem with the keyboard? I would have no idea what's causing issues as I've double checked the connections and cleaned the board thrice to make sure nothing is shorting out.

3rd CPU 2nd board? It could just be the bios settings you set up for your overclock. How is your PSU holding up? What model have you got and when did you get it?

MCE off, BCLK adaptive voltage off, turbo boost off, speed shift off, c states off, voltage optimisation off, energy efficient turbo off, etc etc. Basically everything non-essential off. Altering memory values manually in any way shape or form whether that be increasing/decreasing voltage/timings/speed results in vcore shooting up to 1.5v or thereabouts. Only the stock speeds and XMP profile don't mess with it. Wouldn't there be at least one person out there who has this problem then? To my knowledge there have been no reports on this forum and looking for it on google didn't yield results. Most people don't report a link between RAM overclock and vcore with the exception that you might need to manually increase vcore to stabilise your OC after overclocking RAM (but that's not the issue here). I'll get in touch with the mobo manufacturer, but in the meantime if you have any other ideas I'll be more than happy to hear them.

I have a 5ghz overclock on 1.38v on my i5 9600k using a gigabyte ultra gaming z370 motherboard. I'm using 2x8gb of 3000mhz ram with it. My problem is that touching any settings outside of the XMP basically screws with my vcore. Unless my RAM is at stock or on the XMP profile, my vcore will shoot up to 1.43-1.5v which is way too high for my liking and completely unnecessary. I know RAM might require you to set the vcore a bit higher to ensure OC stability but I've never heard of it raising the vcore automatically by 0.05-0.12v. Even if I manually set the RAM to the same values as the XMP profile the same ends up happening. I noticed that this vcore boost only occurs in windows - bios still reports 1.38v. I can confirm the readout from hwinfo in windows is accurate due to the temp difference alone - the cpu hits the 90's while idle and the fan speeds up accordingly. Any idea what could be causing it?

For anyone with the same problem, I figured it out. Adaptive bclk voltage was enabled and messing with the vcore. After turning it off it stays exactly where I want it.

@thegreengamers @-rascal- Do you know of any settings that override vcore? I set my LLC to high and dropped my vcore in bios to compensate but saw no change in output vcore. The vcore setting in my bios does nothing right now - I can set it to 1v and it'll output 1.35-1.4v.

Okay so turning MCE off clearly helped as the voltage variation is much lower now. It is, however, still there. Instead of going up by 0.15 it now goes up by 0.05-0.10. Is this normal enough or is there cause for concern?

I'll have a look and get back to you. Generally I tried to turn off any "adaptive voltage" settings I could find so it might be I just overlooked MCE

Manually setting the voltage still results in the 0.15v offset, which is why I was looking to see if there are other settings that affect voltage that I could turn off.

Turning the LLC from standard to high made my system really unstable and it wouldn't boot into windows. I'll play around with it more but it doesn't look promising.