Using my NVIDIA GeForce GTX 1070
Asrock Fatal1ty z370 professional gaming i7
Intel core i7-8700k
Noctua - NH-D15 82.5 CFM CPU Cooler
G.Skill - Trident Z RGB 16GB (2 x 8GB) DDR4-3200
Samsung - 960 EVO 500GB M.2-2280
SAMSUNG 850 EVO 2.5" 500GB SATA III 3D NAND
WD Black 4TB 256MB
Seasonic PRIME Ultra 750W 80+ Titanium Power Supply, Full Modular
Corsair - 750D Airflow Edition ATX Full Tower Case
I would love to tell you that it is as much fun as it looks. I had it put together, and installed with the great care every single cable and driver. Bios and Windows 10 pro updates. I even Upgraded my Office. I checked every driver just before setup, picking and choosing the ones that were reliable and recommended. The next day, my Logitech G700s mouse quit work, because it did not receive and charge overnight. After a few weeks of trial and error, research and more updates, I found the answer buried down in the Faq about the update that broke it the same day i setup. I have razer basilisk now. During the time between updates, i managed to install Steam and one game. Shortly after this, and while troubleshooting the mouse, I had a succession of BSOD events.
Booting Clean,memetest(s) 86 and windows, three times, reseating. Basically you can go to any Microsoft site and find forum post filed with canned responses, wash rinse post dmp file, repost dmp file they didn't get.. Download and run “tried and true” tools, ‘I swear it can make you a sandwich’, if you follow, to the letter the following redownloading, resetting, backing up, renaming and Reinstalling. The driver verifier(s), dumpcheck, degging kept telling me everything is fine.. The Rattmann was right.
On my second install I took even greater care. I read my Asrock installation guide line by line. Double checked every driver, update, install.reboot. Picking and choosing the ones that were reliable and recommended. Checked that every connection tested, cables not too tight, pins set correctly. Ran Magician Again, Firmware confirmed, Mark tests, conflict checks. Went line by line through the bios, Had already tweakd, the ram, using jedec setting, No Overclocking, voltage at recommend spec, timing top dead center. At this point I have had 36 BSOD events. SFC.. Local rights vs MS account.. Defender On Defender off. Seagate tools, Deep scans. Kernel Security, IRQL not equal , APC Index mismatch, Memory Management, Resource not owed, System Thread exception, Kernel Security check failure, Unexpected Kernel mode trap, Bad pool Header, Kernel Thread Priority Floor Violation. .. Run as Admin, Compatibility mode, Update, verify, Win32full.sys,CPU-z., custom event logs, Watchdog violation.No PlugnPlay, No lane sharing, just a train wreck. Page Fault In Nonpaged Area…. Diagnostics in safe mode, on boot. Why did i install the firmware. The only firmware available. The firmware i had not installed because I hadn't checked it I know why, because it was the only thing i did not install to complete the entire updates. You know you’re in trouble when what they want you to do, keep telling you to do, with big arrows begins with “ If you do this, its on you” And the people they got it from just shrug.
On the third reinstall, week two I spent more time trying to keep GLaDos off my machine. I am not collecting a paycheck for all this work. . Five morning BSODs go by. The whole time, the privileged scene kidz HelloBus, & Dcom are running Stupid.bat checks, logging errors,whining like emos at their Local Host because they cant do something like. They can do it, they just don't know it. If you notice them, you’ll be told to ignore them, make them invisible.
PERFLIB_INCORRECT_OBJECT_LENGTH, Microsoft-Windows-Bits-Client.. . App manifest validation warning:,..Service Control Manager bedaisy.sys
It's not like i don't have other things to do. There's that mystery, “is it windows or is it battleye” . Also I get lots of other reading in, How broke was Visual C ++.2015. Will the shader compiler ever get attention, and remove deadmaus code? Is seizing directx a controlled dissent or thunder crack before impact. The Cake is a Lie.
Parity Tuesday comes again.
New week, new install, pulled battery off board, temp jumper, purge power. Sanitize drives. Spend the day scouring the web, searching for any small hint that the Coffelake uses will get the fixes needed. Dropped by Intel's site, looked at all the commits they’ve dropped and whoa.. Looks like they don't know coffee lake exists, except they do. They Advise going to MaMafacturer. https://www.windowscentral.com/intel-releases-new-spectre-fixes-skylake-kaby-lake-and-coffee-lake-chips.
The next article dated today
https://www.windowscentral.com/intel-releases-new-spectre-fixes-skylake-kaby-lake-and-coffee-lake-chips
if you have a custom build, motherboard manufacturers like ASRock, Gigabyte, and MSI are worth keeping an eye on as well.
I go and well, yeah they have it, I found it NOT by going to Bios Updates, but Beta Updates. AND, it's a good thing I did pull the cmos, since I HAD 1.60 from last week, upgraded from 1.50 the week i installed it NEW. The last BSOD i had, i ran another dumpchk : read file returned error win32kfull xxx ClientCallDitThread 1cb.. If you ever get this just know.. Google can't find it either.
Facebook
Twitter
Instagram