[SOLVED] [Win10 x64] Random BSOD over a long time now

[Mikedabike]

attached is the only dump i did not already send, plus the one i think you got that was corrupted. Rufus will not burn that image.

 

[Mikedabike]

Ok, using Prime 95 early morning my heat still went straight up to the 90's even though abient temps were a good 10 degrees lower, yet still 30 degrees in the morning :) BUT and i stress this during gaming, for many hours i never see a heat issue of above 76 degrees which considering the air temps of summer is not an unrealistic expectation. So what would you advise me to do in this situation, obviously it is running way to hot under stress, but acceptable given conditions in normal hard gaming use (The game i judge it on is ARK which does demmand a fair amount form all parts). GPU testing stayed at a steady 79 - 80 degrees for 10 mins, not a long test but was similar to what i had last time i tested for a bit longer. Again a little hot but given air temps not unexpected. Still trying to source a usb version of hdd tester. Mem test i will do again when i have free time from using comp.
Many thanks mike.

 

[Mikedabike]

Have another new one as of 20 mins ago, not sure if they are of any use to you just hoping something can help narrow any hardware down a bit. Cant run the stress test at present due to really hot weather and no AC here.

 

[Mikedabike]

next one although it seems no more are needed? But just incase, been a week since last one.

 

[Mikedabike]

and another, both the last 2 were while gaming. I have a new UPS coming tomorrow i hope so i can start checking with clean power as a sure thing.

 

[xilolee]

The new dumps show (I tried to show only relevant things...):

Read More:

Loading Dump File [D:\Downloads\mike\041017-4281-01.dmp]
Debug session time: Mon Apr 10 09:11:27.731 2017 (UTC + 2:00)
System Uptime: 0days 0:05:31.349
BugCheck D1, {fffff8026e831670, ff, c7, fffff8026e831670}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8026e831670, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000c7, value 0 = read operation, 1 = write operation
Arg4: fffff8026e831670, address which referenced memory
ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.
BUGCHECK_STR: DISABLED_INTERRUPT_FAULT
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System


Loading Dump File [D:\Downloads\mike\041717-4437-01.dmp]
Debug session time: Mon Apr 17 14:07:05.883 2017 (UTC + 2:00)
System Uptime: 3 days 8:55:51.155
BugCheck 1000007F, {8, ffff8c00dcca6bf0, d65860f1, fffff80321e5e70d}
Probably caused by : ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+10d )
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc). Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff8c00dcca6bf0
Arg3: 00000000d65860f1
Arg4: fffff80321e5e70d
BUGCHECK_STR: 0x7f_8
BAD_STACK_POINTER: 00000000d65860f1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
UNALIGNED_STACK_POINTER: 00000000d65860f1


Loading Dump File [D:\Downloads\mike\042417-4218-01.dmp]
Debug session time: Mon Apr 24 14:27:31.682 2017 (UTC + 2:00)
System Uptime: 0 days 1:32:23.393
BugCheck A, {5d80b6, ff, 2c, fffff80017adf17f}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+4f )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace.
Arg1: 00000000005d80b6, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000002c, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80017adf17f, address which referenced memory
DUMP_FILE_ATTRIBUTES: 0x8
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System


Loading Dump File [D:\Downloads\mike\042417-4578-01.dmp]
Debug session time: Mon Apr 24 17:22:19.373 2017 (UTC + 2:00)
System Uptime: 0 days 2:54:20.082
BugCheck 124, {0, ffff9002de326028, be000000, 200135}
Probably caused by : GenuineIntel
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon.
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_CACHE
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache

You could try to run driver verifier; please read CAREFULLY the following instructions:

• Only for windows 8, 8.1, 10 users (Win7 users, WinVista users, XP users, shouldn't have this problem):
  • change the bcdedit {bootmgr} displaybootmenu setting from No to Yes
  • change the bcdedit {bootmgr} timeout setting to 30 seconds
  • change the bcdedit bootmenupolicy setting from standard to legacy
  • restart your PC and see if the boot menu appears and if it allows you to select windows advanced boot options (SAFE MODE included!).
  See the hidden instructions if you don't know how to do it.
  Read More:

  From an elevated command prompt, launch these commands:

  bcdedit
  bcdedit /set {bootmgr} displaybootmenu yes
  bcdedit /set {bootmgr} timeout 30
  bcdedit /set {current} bootmenupolicy legacy
  bcdedit

  You should get something like (see bold strings):

  Read More:

  c:\>bcdedit
  
  Windows Boot Manager
  --------------------
  identificatore {bootmgr}
  device partition=\Device\HarddiskVolume2
  path \EFI\Microsoft\Boot\bootmgfw.efi
  description Windows Boot Manager
  locale it-IT
  inherit {globalsettings}
  integrityservices Enable
  default {current}
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  displayorder {current}
  toolsdisplayorder {memdiag}
  timeout 30
  displaybootmenu No
  
  Caricatore di avvio di Windows
  -------------------
  identificatore {current}
  device partition=C:
  path \WINDOWS\system32\winload.efi
  description Windows 10 home x64
  locale it-IT
  inherit {bootloadersettings}
  recoverysequence {4a081ca8-71be-11e6-80cd-eca86b8ec766}
  integrityservices Enable
  recoveryenabled Yes
  isolatedcontext Yes
  allowedinmemorysettings 0x15000075
  osdevice partition=C:
  systemroot \WINDOWS
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  nx AlwaysOn
  bootmenupolicy Standard
  quietboot No
  
  C:\>bcdedit /set {bootmgr} displaybootmenu yes
  The operation completed successfully.
  
  C:\>bcdedit /set {bootmgr} timeout 30
  The operation completed successfully.
  
  C:\>bcdedit /set {current} bootmenupolicy legacy
  The operation completed successfully.
  
  c:\>bcdedit
  
  Windows Boot Manager
  --------------------
  identificatore {bootmgr}
  device partition=\Device\HarddiskVolume2
  path \EFI\Microsoft\Boot\bootmgfw.efi
  description Windows Boot Manager
  locale it-IT
  inherit {globalsettings}
  integrityservices Enable
  default {current}
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  displayorder {current}
  toolsdisplayorder {memdiag}
  timeout 30
  displaybootmenu Yes
  
  Caricatore di avvio di Windows
  -------------------
  identificatore {current}
  device partition=C:
  path \WINDOWS\system32\winload.efi
  description Windows 10 home x64
  locale it-IT
  inherit {bootloadersettings}
  recoverysequence {4a081ca8-71be-11e6-80cd-eca86b8ec766}
  integrityservices Enable
  recoveryenabled Yes
  isolatedcontext Yes
  allowedinmemorysettings 0x15000075
  osdevice partition=C:
  systemroot \WINDOWS
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  nx AlwaysOn
  bootmenupolicy Legacy
  quietboot No

• Create a restore point
• Create a system image
• Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
• Read some other tutorials/guides and WARNINGS on internet.
• Enable verifier
  You can use either the standard method, or the EXPERIMENTAL instructions at the end of this post.
  No need to use them both.
  By the way, in the experimental instructions I modified some verifier settings: I've added the parameter /bootmode resetonbootfail.
  This should reset driver verifier if it should cause the pc to go in BSOD loop state (see next point).
  This option is incompatible with windows 7 and windows vista (it should be skipped by them).
• If you'll get a very fast BSOD after you logged into windows, you'll need to go to safe mode to reset verifier settings.
  From an elevated command prompt:

  verifier /reset

• Post here the new verifier dump

---

Danger

I created the following method to speed up things a bit, to enable verifier settings like written in Jcgriff's verifier thread, using only third party drivers (hence excluding microsoft drivers).
This was tested only on Windows 10 home x64 (and partially on windows 7)

• download nirsoft driverview and decompress its folder (leaving its default name) on your desktop, i.e. on the desktop there should be the driverview folder (with its files in it):
  • nirsoft driverview x64 (you need this one if you are using a 64bit version of windows)
  • nirsoft driverview (x86) (you need this one if you are using a 32bit - x86 - version of windows)
• open notepad, copy the following text and save the file on your desktop as EnableVerifier.ps1:
  
  Note:

  Code for 64bit windows versions (you need this one if you are using a 64bit version of windows)
  
  
  Read More:

  
  $extdrivers="$env:userprofile\desktop\extdrivers.txt"
  $extdrivers2="$env:userprofile\desktop\extdrivers2.txt"
  $tempfile="$env:userprofile\desktop\temp.txt"
  $output="$env:userprofile\desktop\Non-ms-drivers.txt"
  $command = {c:\windows\system32\cmd.exe /c '%userprofile%\Desktop\driverview-x64\driverview.exe' /sort 1 /stext %userprofile%\desktop\extdrivers.txt}
  Invoke-Command -scriptblock $command
  type $extdrivers | find /i "driver name" | out-file $extdrivers2
  $drivers = Get-Content $extdrivers2
  FOR ($i=1; $i -lt $drivers.Length; $i++) {
  NV -Name "linea$i"
  SV -name "linea$i" -value ($drivers.GetValue($i))
  $tmp = GV -name linea$i -valueonly
  $tmp = ( $tmp.TrimStart("Driver Name : ") + " , " )
  $tmp | out-file $tempfile -append
  RV -Name "linea$i"
  }
  $tmp = get-content $tempfile | sort
  $tmp = $tmp -join ""
  $tmp = $tmp.TrimEnd(" , ")
  $tmp = $tmp.Replace(" , ", ",")
  $tmp | out-file $output
  verifier /flags 0x2892B /bootmode resetonbootfail /driver $tmp
  del $output, $extdrivers, $tempfile, $extdrivers2
  rv tmp, tempfile, output, i, extdrivers2, drivers
  
  
  
  
  Note:

  Code for 32bit windows versions (you need this one if you are using a 32bit - x86 - version of windows)
  
  
  Read More:

  
  $extdrivers="$env:userprofile\desktop\extdrivers.txt"
  $extdrivers2="$env:userprofile\desktop\extdrivers2.txt"
  $tempfile="$env:userprofile\desktop\temp.txt"
  $output="$env:userprofile\desktop\Non-ms-drivers.txt"
  $command = {c:\windows\system32\cmd.exe /c '%userprofile%\Desktop\driverview\driverview.exe' /sort 1 /stext %userprofile%\desktop\extdrivers.txt}
  Invoke-Command -scriptblock $command
  type $extdrivers | find /i "driver name" | out-file $extdrivers2
  $drivers = Get-Content $extdrivers2
  FOR ($i=1; $i -lt $drivers.Length; $i++) {
  NV -Name "linea$i"
  SV -name "linea$i" -value ($drivers.GetValue($i))
  $tmp = GV -name linea$i -valueonly
  $tmp = ( $tmp.TrimStart("Driver Name : ") + " , " )
  $tmp | out-file $tempfile -append
  RV -Name "linea$i"
  }
  $tmp = get-content $tempfile | sort
  $tmp = $tmp -join ""
  $tmp = $tmp.TrimEnd(" , ")
  $tmp = $tmp.Replace(" , ", ",")
  $tmp | out-file $output
  verifier /flags 0x2892B /bootmode resetonbootfail /driver $tmp
  del $output, $extdrivers, $tempfile, $extdrivers2
  rv tmp, tempfile, output, i, extdrivers2, drivers
  
• From an elevated command prompt, run:

  powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"

• It should appear something like:
  Read More:

  Verifier Flags: 0x0002892b
    Standard Flags:
      [X] 0x00000001 Special pool.
      [X] 0x00000002 Force IRQL checking.
      [X] 0x00000008 Pool tracking.
      [ ] 0x00000010 I/O verification.
      [X] 0x00000020 Deadlock detection.
      [ ] 0x00000080 DMA checking.
      [X] 0x00000100 Security checks.
      [X] 0x00000800 Miscellaneous checks.
      [X] 0x00020000 DDI compliance checking.
    Additional Flags:
      [ ] 0x00000004 Randomized low resources simulation.
      [ ] 0x00000200 Force pending I/O requests.
      [ ] 0x00000400 IRP logging.
      [ ] 0x00002000 Invariant MDL checking for stack.
      [ ] 0x00004000 Invariant MDL checking for driver.
      [X] 0x00008000 Power framework delay fuzzing.
      [ ] 0x00010000 Port/miniport interface checking.
      [ ] 0x00040000 Systematic low resources simulation.
      [ ] 0x00080000 DDI compliance checking (additional).
      [ ] 0x00200000 NDIS/WIFI verification.
      [ ] 0x00800000 Kernel synchronization delay fuzzing.
      [ ] 0x01000000 VM switch verification.
      [ ] 0x02000000 Code integrity checks.
      [X] Indicates flag is enabled.
    Boot Mode:
      Resetonbootfail
    Rules:
      All rules are using default settings
    Extensions:
      wdm: rules.default
      ndis: rules.default
    Verified Drivers:
  More data is available.
  The system reboot is required for the changes to take effect.

• Reboot your machine and wait the verifier dump (i.e., verifier should force a new BSOD, identifying the problem).

 

[Mikedabike]

Update to help anyone in a situation like this. After all the feedback, help ideas and suggestions for which i am eternally grateful for your time and expertise, i found a simple fix that has to date (4 months now) been working out for me. If i have a hardware issue or not i am still unsure but after doing 2 things i managed to stop all BSOD happening. 1st i got myself a UPS this was to rule out any dirty power that may have been having an effect, and 2ndly i removed the side panel from my comp case and run a house fan along side blowing air past the interior. Given that both my GPU and CPU temps were montered a lot during the period i was having issues and although hot they never showed danger, bsod, type temps. My conclusions from my use of the system lead me to belive that due to heat build up inside the case something was overheating that i could not monitor. So it was either dirty power or/and heat building up in case to a bsod on mb/ram something not CPU or GPU temperature. This may not be the most profesional of solutions in terms of running an external fan but living in ambient temps of a tropical 35 degrees as cool it is and has been my best solution to date. I hope all the info that went before this, and my little bit of clarrification on present situation can help someone else from having to go through the ...buying lots of expensive parts to teat with scenario.. Thanks again to those who gave their time :)