Help me escape these awful crashes.
Help me escape these awful crashes.
I am just sooooo freakin' tired of these BSoDs that my brain has stopped figuring out the real cause of them. Now, it's a pretty erratic system behavior. Here's the current status: I deleted all the 4 ssd partitions incl. recovery, and system reserved MSR (which I normally do while installing a fresh OS copy). Then I just had 3 random BSoDs until now in three tries while the files were getting ready for installation: IRQL-NOT-EQUAL-OR-LESS-THAN, Kmode Failure and Cache Manager. I am installing it from a san disk 3.1 flash drive. Before this, I was running RS4 with all the July updates and driver updates but still I kept on having like 10-20 discrete BSODs/day depending on the pc usage. I tried googling and researching on them despite of having very less time for this bullshit but I literally found nothing that could be useful in this scenario. For eg. they say try sfc /scannow and run windows memory diagnostic, now how can I even perform any of those when ny system can't even boot properly. i don't know if my BIOS is bad or whether the drivers are messing with the BIOS (moreover I don't know how to cure such problems out of the OS environment in the first place cuz the C drive is already formatted and I don't have any recovery images). Now, to be clear, I have always been aware of all the silly things that can trigger these BSODs like missing drivers or anything shit like that and I never O.C. my A10 7890k beyond 4.5 GHz (given that it's factory 4.3 max turbo unlocked) nor do I mess with my 1600 mhz (max freq.) gskill ram because of my mobo (asus a88x-ma/usb3.1) that doesn't allow me to go beyond that. So, I'm just trying over and over again to at least install a fresh, newly updated RS4 OS and then deal with all the possible cures. I am seriously so fucked up with these BSODs that I can't describe my frustration in words! UPDATE: Windows 10 Pro RS4 Build 17134.167 ver.1803 has been successfully installed. My rig: a10 7890k (presently oc'd to 4.5) with stock wraith cooling gskill 128cl1000 8 gb -1600 mhz a88x-ma/usb3.1 mobo Kingston 120 sata ssd msi gaming x 4G 1050ti 580w Deepcool DE-580 PSU WD 2TB GREEN HDD SEAGATE 2TB BUP SLIM PORTABLE STORAGE
Consider alternative approaches instead of relying on programs for testing memory or scanning system files. It’s unnecessary since hardware issues are likely if you can’t even install Windows properly. Give other methods a try—reconnect and power on again, remove one memory card and test with half the RAM, detach the graphics card to see if booting works with integrated graphics, use an X.M.P. profile for your memory or disable it if enabled, adjust frequency settings, or lower it to auto. Experiment with free options first, and always verify your hardware before checking software. Using faulty equipment longer can cause serious damage.
Everything is finished. Just completed the setup. Tested the single RAM stick in all four slots after inflating air pressure inside them. Normally I clean my PC weekly or biweekly. I always reattach all power and SATA cables for each device. Once tried Windows installation (last month) with g. card disabled and running on integrated graphics, but frequent BSODs didn’t occur then. My motherboard doesn’t support XMP, so I can only adjust latencies and timings—which is quite limited—or tweak settings between 1333 and 1600 MHz. Beyond those limits, the system won’t boot. I’ve done this many times. In fact, during two months of college, I spent time optimizing CPU voltage, memory timings, VDDNB voltage, LOAD LINE calibration, and voltage frequency. Still, these problems persist. Recently, I installed the latest RS4 build and the PC is running smoothly with sfc /scannow finishing its check. I’ll keep you posted. No more BSODs right now (maybe because I shorted the CLRTC on the motherboard, clearing CMOS before my last installation attempt?). Thank you!
In my view, Kingston is the worst manufacturer for SSD/USB memory. I don’t understand why they have such a positive opinion. I’d like to avoid having a V300. Personally, I favor AData more than Kingston. Of course, it might be an SSD problem, but you should try installing the OS on your other drive first to confirm. Make sure the SSD is unplugged.
I'll give it a shot. I only have two partitions on my WD disk, and both require resizing to make room for the operating system. I’m worried it might impact my data if I handle it improperly. In the meantime, I want to let you know I’m still experiencing the same BSOD (system service exception) quite frequently.
Begin by generating a Ubuntu USB image, disconnect the SSD, and start from the USB boot. Adjusting partitions here can be somewhat dangerous. If everything works fine with live Ubuntu, you might attempt resizing using Minitool Partition Wizard—a useful tool for this purpose. It’s wise to create extra space at the end of your drive, as it may reduce the amount of data to transfer. To ensure safety, run a full defragmentation beforehand; most tools handle this securely, helping you avoid data loss. In extreme scenarios, a hardware issue could arise, but testing on a live Ubuntu system is recommended (boot from USB without installation). Purchasing a second SSD is a smart move—it allows you to maintain two separate systems. You can clone one drive onto another while the main system runs, which speeds up cloning and lets you restore everything quickly with all settings intact.
I managed to set up my rig within the limited budget I had from the start, so a newer SSD isn't on the horizon anytime soon because they're still quite expensive (particularly the PCI-E and NVMe options). The system is functioning properly now since those corrupt files were fixed during the sfc scan in admin mode. I'll continue to consider the Ubuntu approach moving forward.