There are 2 ways with this crash for now
- A driver tried to acces an invalid memory address or wrong memory address
- A driver tried to acces a memory address that was corrupted
To rule out outdated drivers I have made a list of drivers NOT dating 2015
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arg1: fffff6fb400037a8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000006, (reserved)
iiwdbus iwdbus.sys Sat Oct 04 02:31:12 2014 (542F3FD0) // Intel driver
IntelPcc IntelPcc.sys Tue Aug 05 22:51:29 2014 (53E143D1) // Intel driver
HidEventFilter HidEventFilter.sys Tue Sep 17 23:49:33 2013 (5238CE6D) // Intel driver
DDDriver64Dcsa DDDriver64Dcsa.sys Wed May 28 21:58:54 2014 (53863FFE) // Dell driver, comes with the software for analysing the system, recommended to uninstall while troubleshooting.
This does NOT mean they are causing problems
Please test your memory to rule it out.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ needs to be run for at least 8 passes
for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero
errors here. Even a single error will indicate RAM failure.