Jump to content

CASSIEisGRAPHIC

Member
  • Posts

    2
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

CASSIEisGRAPHIC's Achievements

  1. I was unable to install a Linux based system. It repeatedly crashed just like Windows, giving error codes like “kernel panic bad rip value.” I also tried to install Windows 10 using a functional build onto my new SSD, but the same error occurred.
  2. I've just completed a new build. It boots fine with no errors, and I can get to BIOS, but when I try to install Windows 10, I get BSOD. (Stop code: page fault in non paged area, what failed: WimFsf.sys) The system restarts itself and BSODs in an endless loop. All parts are both visibly working and detected correctly in BIOS. ASUS Prime Z390-A i7 8700 Corsair Vengeance LPX 16GB (2 x 8GB) Cryorig H7 cooler Samsung 860 EVO 1TB 2.5 Inch SATA III Internal SSD EVGA SuperNOVA 650 G3, 80 Plus Gold 650W PSU ASUS Dual-fan Geforce GTX 1070 ***not currently installed due to this issue What I've already tried: swapping out the RAM from a working build one stick of RAM in all of the slots swapping out the CPU (i7 8700k) from a working build using a purchased Windows 10 USB downloading Windows 10 ISO to a working USB updating BIOS to latest version: 0602 Windows Memory Diagnostics Tool (gets stuck and won't finish/BSOD) checking for SSD firmware update via Samsung Magician (latest firmware already installed) resetting CMOS All settings in BIOS are currently default, but I think it's odd that the SSD isn't shown as a possible boot option with default settings. Any ideas? With the CPU, RAM, and SSD firmware ruled out... bad motherboard? Settings to be tweaked in BIOS? Thank you in advance. EDIT: I have now also tried taking the M.2 SSD (boot drive containing Windows and all storage data) out of a fully functional build and putting my new empty SSD into it and tried installing Windows. Same WimFsf.sys BSOD. I’ve ordered an M.2 drive to try in the new build. Could that really be the issue?
×