New
#21
As soon as I turned my pc on same thing happened within 2 minutes
As soon as I turned my pc on same thing happened within 2 minutes
I don't know if Verifier will help ID the freezing cause or not. All you can do it try it.
I notice you have
See if there are updated drivers for either or both as Razer has been known to cause problems with Windows 10. If no new driver, can you replace them with normal USB keyboard and mouse and uninstall the Razer software and/or drivers. Do this just to test for awhile, see if it still freezes.Code:Keyboard Razer BlackWidow Ultimate Mouse Razer Naga
One other thing you can think about doing is doing a Clean Boot to see if that makes any difference:
How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
Ok I will try these, it blue screened just now so I'll upload the logs when home and will turn on the verifier:)
Provided the dumps, had 3 crashes very close to each other, however I think this was because the first one happened during an update and thus caused an issue. Razer synapse (the driver manager) was struggling to update, so I removed it with revo and am re installing it now. I have turned verifier on so next crash (fingers crossed) should be better recorded. I have also enabled the clean boot thing.
The 2/24 7:53PM dump indicates a problem with rt640x64.sys.
Driver Description: Realtek NICDRV 8169 PCIe GBE Family Controller driverCode:BugCheck 1E, {ffffffffc000001d, fffff800931354e0, ffffb200063fd1c8, ffffb200063fc9f0} *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
Driver Update Site: Realtek
The one you have is dated 05/05/2015 17:21:03 C:\WINDOWS\system32\drivers\rt640x64.sys.
There is one on the website for your board that is slightly newer and is for Windows 10 X64:
Realtek LAN Driver [10.001.0505.2015] 9.36 MB 2015/07/09
Give that a try, see if it helps.
So when checking this I uninstalled the driver, downloaded and installed the latest driver they have, however it still appears in device manager as the 05/05/2015 one, (it was properly uninstalled and installed I am sure), but it has the version 10.1.505.2015, so I believe it is up to date.
I have had more BSOD's and will provide the logs asap.
The latest dumpfile is
Usual causes:* Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service PackCode:BugCheck 1000007F, {8, ffffa10132a48b30, ffffa1013bc57bb0, fffff801712afdc3} Probably caused by : memory_corruption Followup: memory_corruption ---------
You have 1600 mhz modules but according the dumpfile they are running at 800 mhz.
Could you check this in the BIOS.
Also have you installed the modules in the same coloured slots, according your to your manual the recommend slots are Channel A -2 and Channel B - 1. See your manual GA-990XA-UD3 (rev. 3.0) - GIGABYTE - Motherboard , Graphics Card , Laptop , Mini-PC , Server , PC Peripherals and moreCode:Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm2 Bank Locator Node0_Bank0 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 800MHz Manufacturer Undefined Serial Number Asset Tag Number Part Number ST51264BA160B
Is this memory compatible with your Mobo, it is not listed on the QVL memory list?
Wow thats a lot of usual causes!
Just to clarify / remove some things of that list, as mentioned the RAM has passed memtest multiple times, none of my hardware is OC'd, BIOS is fully up to date.
As far as I'm aware this is because its the single ram speed, and with it being DDR its 800*2=1600, I could be mistaken though?
As for the slots basically I was having BSOD's whenever any module was installed in one of the channels, so I had to move both modules over to the other channel, and this seemed to fix it, however I can move them back around to see what happens.
As for the memory I could have sworn I saw it on the supported list a while ago, ill check with the vendor of my PC.
Thanks for all the help :)
So whats the next step?
Welp another BSOD, if you want me to stop spamming the logs let me know!