Windows 8 BSOD Issue

[linkster3769]

Hey, my computer has been bluescreening for quite a while, but it isn't invasive(it just goes away after a restart or two, and then never comes back until after i shut my computer down/restart it again. After troubleshooting it off and on after a couple OS reinstalls I believe that it is related to my videocard drivers, as i remember working pretty flawlessly for a few days up to that point. I used to have an AMD 270x and i blamed that, got the Gtx 970, and still had the issue once i installed the drivers.

It's been all different kinds of errors, like 5 or 6 different error types, with the same result, but memtest has passed flawlessly twice. sfc scannow passes as well

Is updating the BIOS what I need to do?

CPU: AMD FX 8320
GPU: Asus Strix Gtx 970
Storage: Toshiba Q Series Pro 128GB, Seagate 1 TB HDD
Motherboard: Gigabyte GA?990FXA?UD3
Windows 8.1
WLAN: ASUS PCE?AC66 Dual?Band Network Adapter

Last 4 minidumps:
https://drive.google.com/folderview?id=0B2UCZVsmvuiIazRUSTA2MjR0Q1U&usp=sharing

 

[johnbl]

I would be running hardware tests on the machine independently of winodws. (memtest86)
update or reset your BIOS if you can.
--
overall it looks like a pirate version of windows running on a machine that has BIOS or hardware problems.
Sometimes these versions have rootkits and malware installed.

I would update the BIOS or reset it to defaults and install a clean version of windows.
or you might be able to run cmd.exe as an admin then run
sfc.exe /scannow
then run
dism.exe /online /cleanup-image /restorehealth
then run a malwarebytes scan, reboot the machine and run
the sfc.exe /scannow command again. (to confirm fixes are still fixed after a reboot)

Note: you could also just have a very out of date BIOS, it is very common to have USB problems that cause memory corruption. I could not check because I could not read your BIOS info.

-------------
third bughcek was ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
while running WRSA.exe Webroot® SecureAnywhere™ - Antivirus

looks like it was using a invalid page table entry. This could be from a error from a storage driver or actual storage.
(or just in memory corruption)



----------
second bugcheck, looks like you have verifier enabled. The cdrom driver used a bad memory address and was caught by verifier. Can not read the bios info from the memory dump.
----------------
first one was caused because the actual nt kernel binary had a single bit corruption in it, windows detected the corruption and shut the system down. can not read the BIOS info from the memory dump.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff803faa8f96f - nt!RtlpNewSecurityObject+121f
[ 66:62 ]
1 error : !nt (fffff803faa8f96f)
FOLLOWUP_NAME: memory_corruption

basically the code was corrupted and caused the CPU to attempt to execute a invalid CPU instruction.
system was up 8 seconds. This often indicates that the system rebooted because of a power problem.
IE GPU uses too much power and caused the CPU power to fall too low and reset the CPU.

 

[linkster3769]

Hm... after all the danger and risk about "don't flash your BIOS unless you know it's the problem" that seemed to have worked completely.

I haven't bluescreened in the last hour, so it had to have just been an incompatibility. All I had to do was Qflash my rev 4.0 board from F2 to F3.

I really appreciate it man, thanks a lot johnbl

 

[linkster3769]

aaaaand I spoke too soon, it happened, and i upgraded to windows 10, and it's still happening. I'm going to try to reset every and reinstall but I am not too hopeful. This OS is not pirated, but i did reinstall it from the recovery media of a USB once or twice. It has to be some sort of hardware issue.

 

[johnbl]

try running memtest86 and confirm it works with out any errors.

aaaaand I spoke too soon, it happened, and i upgraded to windows 10, and it's still happening. I'm going to try to reset every and reinstall but I am not too hopeful. This OS is not pirated, but i did reinstall it from the recovery media of a USB once or twice. It has to be some sort of hardware issue.