Help with random BSOD and Freezing.

[xilolee]

The bsod isn't included... By the way, you still have these files:

\??\c:\program files (x86)\msi afterburner\rtcore64.sys
\??\c:\windows\gdrv.sys

gdrv.sys shouldn't be there, if you have uninstalled it...
rtcore64.sys could also be a problem. Are you actually over/under-clocking?
If yes, try to boot without over/under-clocking.
If you aren't over/under-clocking, and if the problem appears also after you stopped to over/under-clock your machine, try to remove msi afterburner completely (you will always be able to reinstall it later, right?).

 

[Rogue7]

Sorry forgot to mention my computer spazed out on me giving me blue screens on the simplest of tasks at random times, had to reset it to get back to the internet, No I am not clocking the gpu or the cpu I use afterburner for temp monitoring and fan control, the only problem I had today with my pc is it froze in game, no bsod it just became unresponsive and stuck on the last frame, looked for a crash report and I couldn't find anything so I looked in the event viewer and at the time of the crash there was this log:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

[Rogue7]

So Got a new bsod I havn't seen before, I have uninstalled msi completely and deleted the file gdrv.sys, here is the new scan:

 

[xilolee]

(I'm starting to think your PSU isn't enough, but I'm not an expert even in hardware)

You could try to run driver verifier to get more precise informations; please read CAREFULLY the following instructions:

• Change the bcdedit bootmenupolicy setting from standard to legacy:
  Read More:

  From an elevated command prompt, launch:

  bcdedit

  Then:

  bcdedit /set bootmenupolicy legacy

  Then:

  bcdedit

  You should get something like (see bold strings):

  c:\>bcdedit
  Windows Boot Manager
  --------------------
  identifier {bootmgr}
  device partition=\Device\HarddiskVolume2
  path \EFI\Microsoft\Boot\bootmgfw.efi
  description Windows Boot Manager
  locale it-IT
  inherit {globalsettings}
  default {current}
  resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
  displayorder {current}
  toolsdisplayorder {memdiag}
  timeout 30
  Windows Boot Loader
  -------------------
  identifier {current}
  device partition=C:
  path \WINDOWS\system32\winload.efi
  description Windows 10
  locale it-IT
  inherit {bootloadersettings}
  recoverysequence {5d5a201b-d643-11e4-a71c-9001aae18364}
  recoveryenabled Yes
  isolatedcontext Yes
  allowedinmemorysettings 0x15000075
  osdevice partition=C:
  systemroot \WINDOWS
  resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
  nx OptIn
  bootmenupolicy Standard
  
  C:\>bcdedit /set bootmenupolicy legacy
  The operation completed successfully.
  
  c:\>bcdedit
  Windows Boot Manager
  --------------------
  identifier {bootmgr}
  device partition=\Device\HarddiskVolume2
  path \EFI\Microsoft\Boot\bootmgfw.efi
  description Windows Boot Manager
  locale it-IT
  inherit {globalsettings}
  default {current}
  resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
  displayorder {current}
  toolsdisplayorder {memdiag}
  timeout 30
  Windows Boot Loader
  -------------------
  identifier {current}
  device partition=C:
  path \WINDOWS\system32\winload.efi
  description Windows 10
  locale it-IT
  inherit {bootloadersettings}
  recoverysequence {5d5a201b-d643-11e4-a71c-9001aae18364}
  recoveryenabled Yes
  isolatedcontext Yes
  allowedinmemorysettings 0x15000075
  osdevice partition=C:
  systemroot \WINDOWS
  resumeobject {5d5a2019-d643-11e4-a71c-9001aae18364}
  nx OptIn
  bootmenupolicy Legacy

  Restart your PC and see if you are able to make appear windows advanced boot options (SAFE MODE included!) with the good old F8 key.
• 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 (check the EXPERIMENTAL instructions at the end of this post)
• 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

• 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):
  • http://www.nirsoft.net/utils/driverview-x64.zip (for 64bit versions)
  • http://www.nirsoft.net/utils/driverview.zip (for 32bit versions)
• open notepad, copy the following text and save the file on your desktop as EnableVerifier.ps1:
  
  Note:

  Code for 64bit windows versions
  Read More:

  $extdrivers="c:\users\$env:username\desktop\extdrivers.txt"
  $extdrivers2="c:\users\$env:username\desktop\extdrivers2.txt"
  $tempfile="c:\users\$env:username\desktop\temp.txt"
  $output="c:\users\$env:username\desktop\Non-ms-drivers.txt"
  $command = {c:\windows\system32\cmd.exe /c C:\Users\%username%\Desktop\driverview-x64\driverview.exe /sort 1 /stext c:\users\%username%\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 | out-file $output
  verifier /flags 0x2892B /bootmode resetonbootfail /driver $tmpdel $tmp
  del $output, $extdrivers, $tempfile
  rv tmp, tempfile, output, i, extdrivers2, drivers
  Note:

  Code for 32bit windows versions
  Read More:

  $extdrivers="c:\users\$env:username\desktop\extdrivers.txt"
  $extdrivers2="c:\users\$env:username\desktop\extdrivers2.txt"
  $tempfile="c:\users\$env:username\desktop\temp.txt"
  $output="c:\users\$env:username\desktop\Non-ms-drivers.txt"
  $command = {c:\windows\system32\cmd.exe /c C:\Users\%username%\Desktop\driverview\driverview.exe /sort 1 /stext c:\users\%username%\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 | out-file $output
  verifier /flags 0x2892B /bootmode resetonbootfail /driver $tmpdel $tmp
  del $output, $extdrivers, $tempfile
  rv tmp, tempfile, output, i, extdrivers2, drivers
• From an elevated command prompt, run:

  powershell -executionpolicy unrestricted "c:\users\%username%\desktop\EnableVerifier.ps1"

• It should appear something like:
  Read More:

  C:\>powershell -executionpolicy unrestricted "c:\users\%username%\desktop\EnableVerifier.ps1"
  
  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
  
  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).

 

[Rogue7]

Just as an update I did the first portion, I ran driver verifier and rebooted with no blue screens. Lately it has been only stopping on the last frame in game with thees errors in event viewer:

-The User Data Access_2de05 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

-The User Data Storage_2de05 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

-The Sync Host_2de05 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

-Your computer has lost the lease to its IP address 2601:901:8000:2470:428d:5cff:fe19:b7ea on the Network Card with network address 0x408D5C19B7EA.

if that helps at all that's really the only type of error message I can find at the moment. have to head to work will do the second part when I get back. thank you

 

[xilolee]

What first portion? (the part at the end of the post should allow you to enable verifier without actually open verifier and modify its settings, but it isn't needed if you did it manually)

I get your same errors (on windows shutdown/restart) and I think each windows 10 user get them (and maybe also windows 8.1 users); sorry but now I'm using Italian language on my system:

• Event ID: 7031
  Il servizio Accesso dati utente_2b309 è stato arrestato in modo imprevisto. Questo problema si è verificato 1 volta/e. Le seguenti azioni di correzione saranno eseguite tra 10000 millisecondi: Riavvia il servizio.
• Event ID: 7031
  Il servizio Archiviazione dati utente_2b309 è stato arrestato in modo imprevisto. Questo problema si è verificato 1 volta/e. Le seguenti azioni di correzione saranno eseguite tra 10000 millisecondi: Riavvia il servizio.
• Event ID: 7031
  Il servizio Dati contatti_2b309 è stato arrestato in modo imprevisto. Questo problema si è verificato 1 volta/e. Le seguenti azioni di correzione saranno eseguite tra 10000 millisecondi: Riavvia il servizio.
• Event ID: 7031
  Il servizio Sincronizza host_2b309 è stato arrestato in modo imprevisto. Questo problema si è verificato 1 volta/e. Le seguenti azioni di correzione saranno eseguite tra 10000 millisecondi: Riavvia il servizio.

 

[Rogue7]

Ok yeah now I get it, Yes I did run driver verifier but came up with no crash on the reboot.

 

[Rogue7]

How would I go about checking to see if my psu amount is adequate?

 

[Rogue7]

The more I read about it the more it seems to fit all the symptoms, random bsod's, freezes and application errors, granted this may just be wishful thinking on my part but my roomate has almost an identical pc only real diffrence is I think he has an extra 8 gb of ram and a gtx 960, but my point is he has a 850w PSU and his system has never had a problem my PSU is only 600w.

 

[Rogue7]

something new :

Description
A problem with your hardware caused Windows to stop working correctly.


Problem signature
Problem Event Name: LiveKernelEvent
Code: 144
Parameter 1: 101e
Parameter 2: ffffd001fb7cd970
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_10586
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.10586.2.0.0.768.101
Locale ID: 1033


Extra information about the problem
Bucket ID: LKD_0x144_INVALID_TRANSFER_EVENT_PTR_ED_1_USBXHCI!TelemetryData_CreateReport_VEN_1106_DEV_3483_REV_01_FW_136D9

 

[axe0]

The more I read about it the more it seems to fit all the symptoms, random bsod's, freezes and application errors, granted this may just be wishful thinking on my part but my roomate has almost an identical pc only real diffrence is I think he has an extra 8 gb of ram and a gtx 960, but my point is he has a 850w PSU and his system has never had a problem my PSU is only 600w.

You could be correct, although the power consumption specs the gtx950 shows is with i7 3.2GHz, so we do not know if the same amount of power is used with your AMD FX-9590.
If we would assume it is and including the power consumption your AMD CPU uses per what I found on the dutch tech site Tweakers.net stating the CPU uses 220W you would come to a 570W power consumption for the GPU & CPU.

I do not know how much power your other components use, but it is a bit tight with this assumption. A small spike could be causing problems with this assumption.

 

[Rogue7]

So theoretically with those 2 components combined I am almost at my max Watt, Does playing games or rather putting the Gpu under load increase power consumption, because that's were these freezes seem to be happening most of the time. The only other components I have are 2x8gb ram sticks.

 

[axe0]

Of course, per what I understand it starts with 90W consumption. The more load there is the more power is required.

What about your motherboard, mouse and keyboard? They also use power, though a lot less, but like I mentioned a small spike is enough to use more than the 30W that is left. This is why the recommendation is to get a PSU that provides at least 25% more wattage than necessary. In your case you would be on a safer side with at least a 650W or 700W PSU if you're not planning on adding stuff that require a lot of power when under load.

 

[xilolee]

something new:
Description
A problem with your hardware caused Windows to stop working correctly.
...
Bucket ID: LKD_0x144_INVALID_TRANSFER_EVENT_PTR_ED_1_USBXHCI!TelemetryData_CreateReport_VEN_1106_DEV_3483_REV_01_FW_136D9

Is that a new BSOD caused by driver verifier? If yes, post here the new dump.
Are you still running verifier?
Jcgriff2 (and also Jcgriff1 ) says it should "run for 24 hours minimum".

Why have I written this?

(I'm starting to think your PSU isn't enough, but I'm not an expert even in hardware)

Because I searched the web a bit and I found these threads:

tomshardware.co.uk - PSU not powerful enough I think :| (click), where SR-71 blackbird said:

Read More:

Not even close minimum is 850w. 1000w is recommended.
And the PSU is poor quality, new cooler is also needed minimum h100i
Warning: This power draw of this CPU is almost twice that of the average CPU. Due to this, AMD recommends using at minimum a 1000W power supply. For cooling, AMD recommends using either either closed loop liquid cooling or full system liquid cooling.

tomshardware.co.uk - Can silver certified PSUs handle High end gaming? (600w ATNG ATM-600FB) (click) , where 466gaming said:

Read More:

You should consider an upgrade because that PSU is pretty unstable.

I didn't find WHERE in amd website (excluding the community) "AMD recommends using at minimum a 1000W power supply", like said by SR-71 blackbird.
In amd shop, one of the reviewers (probably given in amazon website) said he's using XFX Pro Series 1000W Platinum Limited Black Edition.
Another one (from newegg) said he's using EVGA 220-P2-1000-XR.

Now I've tried another search and found these (real) buids: Completed Builds Using AMD FX-9590 4.7GHz 8-Core OEM/Tray Processor (click).

Those two guys are both using GeForce GTX 960 and Corsair Enthusiast 650W 80+ Certified ATX (the modular version, most likely...).

Just for curiosity I checked the xfx pro prices and it seems the 1250watt version cost less than the 1000 or 1050 version (about 200$ on amazon, against 484$ for the 1000w).

Now, same premise (I'm not a hardware expert): I'd search a PSU over 800W, from a high quality manufacturer...

 

[Rogue7]

if you can run driver verifier for 24 hours I must have messed up along the way somewhere because when I setup the driver verifier, It only asked for a reboot and that was it, I thought if I had a driver conflict ion or error It would give an automatic bsod. Also that last posted error was not even a bsod that was a system freeze where it just stopped on the last frame (only in-game lately), I found that error in Windows Reliability Monitor. So are we almost sure that all the problems I have been having are attributed to a inadequate PSU?

 

[Rogue7]

I only ask because I have the means to do so right now. I am very persistent on wanting to fix the problem as soon as I possibly can lol. Thank you for your help so much and the knowledge you have shared with me I am so inexplicably grateful to you!

 

[xilolee]

So are we almost sure that all the problems I have been having are attributed to a inadequate PSU?

No, I'm not totally and 100% sure of it.
To check verifier settings, open a command prompt (it should work with a simple command prompt, but it's better if you check it with an elevated command prompt) and copy/paste these commands:

verifier /query
verifier /querysettings

Output (important parts in bold - strange it uses English for the first command...):

Read More:

C:\>verifier /query
No drivers are currently verified.
C:\>verifier /querysettings
Flag verifica: 0x00000000
Flag standard:
[ ] 0x00000001 Pool speciale.
[ ] 0x00000002 Forzatura controllo IRQL.
[ ] 0x00000008 Monitoraggio pool.
[ ] 0x00000010 Verifica I/O.
[ ] 0x00000020 Rilevamento deadlock.
[ ] 0x00000080 Controllo DMA.
[ ] 0x00000100 Controlli di sicurezza.
[ ] 0x00000800 Altri controlli.
[ ] 0x00020000 Controllo conformità DDI.
Flag aggiuntivi:
[ ] 0x00000004 Simulazione casuale risorse in esaurimento.
[ ] 0x00000200 Forzatura richieste I/O in sospeso.
[ ] 0x00000400 Registrazione IRP.
[ ] 0x00002000 Verifica MDL invariante per stack.
[ ] 0x00004000 Verifica MDL invariante per driver.
[ ] 0x00008000 Test con dati casuali sui ritardi del framework di alimentazione.
[ ] 0x00010000 Controllo interfaccia porta/miniport.
[ ] 0x00040000 Simulazione sistematica risorse in esaurimento.
[ ] 0x00080000 Controllo conformità DDI (aggiuntivo).
[ ] 0x00200000 Verifica NDIS/WIFI.
[ ] 0x00800000 Test con dati casuali sui ritardi di sincronizzazione del kernel.
[ ] 0x01000000 Verifica commutatore macchina virtuale.
[ ] 0x02000000 Controlli integrità codice.
[X] indica che il flag è abilitato.
Modalità di avvio:
Persistent
Regole:
Tutte le regole utilizzano le impostazioni predefinite
Driver verificati:
Nessuno

If you read the BSOD posting instructions, you should have read also point 6:

6. While waiting for a reply -
· Run - Driver Verifier - Windows 10, 8.1, 8, 7 & Vista (for 24 hours minimum)
· Run HDD Diagnostics - http://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html
· Test RAM - http://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html

 

[Rogue7]

C:\WINDOWS\system32>ATM-600FB 600W
'ATM-600FB' is not recognized as an internal or external command,
operable program or batch file. pops up when I enter the command verfifier/ query

 

[xilolee]

From your post it seems you wrote ATM-600FB 600W as a command...

 

[Rogue7]

No, I went to cmd wrote verifier/query and at the end of the entry thats what it said