[SOLVED] Random Black Screen when playing a game

P

pasranno

Well-known member
Joined
Mar 24, 2016
Posts
51
Location
NYC
Hello everyone,

I encounter one of the worse problem I ever had with my computer. This one is randomly crashing/freezing when i am playing a game for no reason (the screen goes black stating "No signal" and there is a sound loop but the computer is still running you can see the fans spinning however the system isn't responding).
I directly though that it should be software related and more precisely a problem with my gpu drivers. I tried to clean install it with DDU 3 times and still the same. After that I stress-tested my gpu with both Furmark and Unigine's Valley for 30 minutes and no crash happened while the GPU temp stays under 63°C.
I also run a sfc scan and a chkdsk to see if some corrupted files were the origin of this mess but everything seems to be ok (You can find the CBS log down here).
Finally I read some posts about this problem and some users having the same problem with a Fury X said that it's because of downclocking so I gave it a shot and I installed clockblocker. It actually didn't work but for the first time my computer didn't went into a blackscreen but a blue one so I finally have something to work with thanks to the minidump and the error : atikmpag.sys .

Finally I tried to run Driver verifier but it keeps crashing my computer on boot with two different BSOD reasons so i decided to turn it off. You can find all the minidump attached to this post the first one is related to the initial crash and the 3 following ones are related to driver verifier crash. I didn't uploaded the Sysnative BSOD dump + system file collection App results because everytime I try to run it it never end. I mean it keeps stating "Waiting for SystemInfo" for hours so I always have to stop the process manually.

Hardware information·
· OS W7x64
· What was original installed OS on system? W7x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? RV
· Age of system (hardware) 3.5 years
· Age of OS installation - have you re-installed the OS? 3.5 years (never)

· CPU- I5 - 3570
· Video Card - Sapphire Radeon HD 7850
· MotherBoard - AsRock Z77 Extreme 4
· Power Supply - Corsair GS600 - 600W
· Laptop or Desktop? Desktop

Edit: I forgot to mention that I was abroad during the past 6 months and last time I played on it in February everything was working well (the gpu driver version was Crimson 16.1). I even tried to downgrade the gpu driver to this particular (assumed working) version but crash is still happening.
 

Attachments

Hi Pasranno,

The dump files list a couple of things, the likely cause to me looks to be your proxy.
Code: 
fffff880`0c4b30b8 fffff800`03d0e4ec : 00000000`000000c4 00000000`000000f6 00000000`00000160 fffffa80`07e4f7e0 : nt!KeBugCheckEx
fffff880`0c4b30c0 fffff800`03d23aa4 : 00000000`00000160 fffffa80`07e4f7e0 00000000`00000006 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0c4b3100 fffff800`03bbd310 : fffff880`0c4b31e0 fffff880`0c4b3358 fffff880`0c4b3500 fffff880`0c4b36d8 : nt!VfCheckUserHandle+0x1b4
fffff880`0c4b31e0 fffff800`03b53e25 : 00000000`00000000 fffff880`00000000 fffffa80`069fc4b0 fffff800`038a6500 : nt! ?? ::NNGAKEGL::`string'+0x18a2e
fffff880`0c4b32b0 fffff800`03b99edb : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`038a6770 : nt!ObReferenceObjectByHandle+0x25
fffff880`0c4b3300 fffff800`03b9aa46 : 00000000`00000050 ffffffff`80000b44 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x15b
fffff880`0c4b3440 fffff800`03879693 : fffffa80`07e60db0 fffff800`03d29099 fffffa80`0cc363e0 00000000`000007ff : nt!NtDeviceIoControlFile+0x56
fffff880`0c4b34b0 fffff800`03875c50 : fffff800`03d14936 00000000`00000000 00000000`00000002 fffffa80`0cc363e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c4b36b8 fffff800`03d14936 : 00000000`00000000 00000000`00000002 fffffa80`0cc363e0 00000000`00000000 : nt!KiServiceLinkage
fffff880`0c4b36c0 fffff880`0494c670 : fffffa80`0cc363e0 fffff980`3e3eafe0 fffffa80`0775f8c0 fffff800`03b765e9 : nt!VfZwDeviceIoControlFile+0xc6
fffff880`0c4b3740 fffffa80`0cc363e0 : fffff980`3e3eafe0 fffffa80`0775f8c0 fffff800`03b765e9 fffff880`0c4b3790 : [COLOR=#ff0000][B]FNETURPX[/B][/COLOR]+0x1670
fffff880`0c4b3748 fffff980`3e3eafe0 : fffffa80`0775f8c0 fffff800`03b765e9 fffff880`0c4b3790 fffffa80`00220424 : 0xfffffa80`0cc363e0
fffff880`0c4b3750 fffffa80`0775f8c0 : fffff800`03b765e9 fffff880`0c4b3790 fffffa80`00220424 fffffa80`0b80e9c0 : 0xfffff980`3e3eafe0
fffff880`0c4b3758 fffff800`03b765e9 : fffff880`0c4b3790 fffffa80`00220424 fffffa80`0b80e9c0 fffff800`00000200 : 0xfffffa80`0775f8c0
fffff880`0c4b3760 fffffa80`0d0b4ec0 : fffffa80`0cc363e0 00000000`00000000 fffff800`03b9a5b5 fffff880`03565180 : nt!ObpCreateHandle+0x1f9
fffff880`0c4b3870 fffffa80`0cc363e0 : 00000000`00000000 fffff800`03b9a5b5 fffff880`03565180 00000000`00000200 : 0xfffffa80`0d0b4ec0
fffff880`0c4b3878 00000000`00000000 : fffff800`03b9a5b5 fffff880`03565180 00000000`00000200 00000000`00000200 : 0xfffffa80`0cc363e0

Uninstall your FNet User Proxy and see if the crash continues. If the crash goes away, you can try just re-installing the proxy, or installing a different version, and see if the issue continues.
 
Xer said:
Hi Pasranno,

The dump files list a couple of things, the likely cause to me looks to be your proxy.
Code: 
fffff880`0c4b30b8 fffff800`03d0e4ec : 00000000`000000c4 00000000`000000f6 00000000`00000160 fffffa80`07e4f7e0 : nt!KeBugCheckEx
fffff880`0c4b30c0 fffff800`03d23aa4 : 00000000`00000160 fffffa80`07e4f7e0 00000000`00000006 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0c4b3100 fffff800`03bbd310 : fffff880`0c4b31e0 fffff880`0c4b3358 fffff880`0c4b3500 fffff880`0c4b36d8 : nt!VfCheckUserHandle+0x1b4
fffff880`0c4b31e0 fffff800`03b53e25 : 00000000`00000000 fffff880`00000000 fffffa80`069fc4b0 fffff800`038a6500 : nt! ?? ::NNGAKEGL::`string'+0x18a2e
fffff880`0c4b32b0 fffff800`03b99edb : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`038a6770 : nt!ObReferenceObjectByHandle+0x25
fffff880`0c4b3300 fffff800`03b9aa46 : 00000000`00000050 ffffffff`80000b44 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x15b
fffff880`0c4b3440 fffff800`03879693 : fffffa80`07e60db0 fffff800`03d29099 fffffa80`0cc363e0 00000000`000007ff : nt!NtDeviceIoControlFile+0x56
fffff880`0c4b34b0 fffff800`03875c50 : fffff800`03d14936 00000000`00000000 00000000`00000002 fffffa80`0cc363e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c4b36b8 fffff800`03d14936 : 00000000`00000000 00000000`00000002 fffffa80`0cc363e0 00000000`00000000 : nt!KiServiceLinkage
fffff880`0c4b36c0 fffff880`0494c670 : fffffa80`0cc363e0 fffff980`3e3eafe0 fffffa80`0775f8c0 fffff800`03b765e9 : nt!VfZwDeviceIoControlFile+0xc6
fffff880`0c4b3740 fffffa80`0cc363e0 : fffff980`3e3eafe0 fffffa80`0775f8c0 fffff800`03b765e9 fffff880`0c4b3790 : [COLOR=#ff0000][B]FNETURPX[/B][/COLOR]+0x1670
fffff880`0c4b3748 fffff980`3e3eafe0 : fffffa80`0775f8c0 fffff800`03b765e9 fffff880`0c4b3790 fffffa80`00220424 : 0xfffffa80`0cc363e0
fffff880`0c4b3750 fffffa80`0775f8c0 : fffff800`03b765e9 fffff880`0c4b3790 fffffa80`00220424 fffffa80`0b80e9c0 : 0xfffff980`3e3eafe0
fffff880`0c4b3758 fffff800`03b765e9 : fffff880`0c4b3790 fffffa80`00220424 fffffa80`0b80e9c0 fffff800`00000200 : 0xfffffa80`0775f8c0
fffff880`0c4b3760 fffffa80`0d0b4ec0 : fffffa80`0cc363e0 00000000`00000000 fffff800`03b9a5b5 fffff880`03565180 : nt!ObpCreateHandle+0x1f9
fffff880`0c4b3870 fffffa80`0cc363e0 : 00000000`00000000 fffff800`03b9a5b5 fffff880`03565180 00000000`00000200 : 0xfffffa80`0d0b4ec0
fffff880`0c4b3878 00000000`00000000 : fffff800`03b9a5b5 fffff880`03565180 00000000`00000200 00000000`00000200 : 0xfffffa80`0cc363e0

Uninstall your FNet User Proxy and see if the crash continues. If the crash goes away, you can try just re-installing the proxy, or installing a different version, and see if the issue continues.
Click to expand...

Hi Xer,

I don't think that it will fix anything but I will try to uninstall it as soon as you could give me some advice on how to do that. I just read on some forums that it is very risky to uninstall this driver because if you fail to uninstall it completely the system could be damaged and would need a complete reset. Therefore I'm a bit scared to make it.

Secondly I don't know if you get it from my previous message (as english is not my native language and I know that I make alot of mistakes) but the only dump that is really related to the initial blackscreen/sound loop crash is "080716-19297-01". The 3 other one are related to some crash that occured after I enabled driver verifier. Just saying that because you are talking about FNETURPX.Sys which is the file that caused this driver verifier crash.

Thank you very much for your quick reply!
 
pasranno said:
Secondly I don't know if you get it from my previous message (as english is not my native language and I know that I make alot of mistakes) but the only dump that is really related to the initial blackscreen/sound loop crash is "080716-19297-01". The 3 other one are related to some crash that occured after I enabled driver verifier. Just saying that because you are talking about FNETURPX.Sys which is the file that caused this driver verifier crash.
Click to expand...

There isn't a lot of info from the sole minidump that blamed your video driver. As you've already said, you tried doing a clean re-install of the driver, I assume you've tried other driver versions (old/beta)? The Catalyst Suite can also be problematic in some cases, have you tried installing only the video drivers upon a clean installation? Unfortunately your MEMORY.DMP file from the 0x116 would likely already be overwritten by now from the Verifier crashes.

Here is a pretty comprehensive list of troubleshooting suggestions for a 0x116, courtesy of usasma: Video TDR Timeout - 0x116 + 0x117
 
Xer said:
pasranno said:
Secondly I don't know if you get it from my previous message (as english is not my native language and I know that I make alot of mistakes) but the only dump that is really related to the initial blackscreen/sound loop crash is "080716-19297-01". The 3 other one are related to some crash that occured after I enabled driver verifier. Just saying that because you are talking about FNETURPX.Sys which is the file that caused this driver verifier crash.
Click to expand...
There isn't a lot of info from the sole minidump that blamed your video driver. As you've already said, you tried doing a clean re-install of the driver, I assume you've tried other driver versions (old/beta)? The Catalyst Suite can also be problematic in some cases, have you tried installing only the video drivers upon a clean installation? Unfortunately your MEMORY.DMP file from the 0x116 would likely already be overwritten by now from the Verifier crashes.Here is a pretty comprehensive list of troubleshooting suggestions for a 0x116, courtesy of usasma: Video TDR Timeout - 0x116 + 0x117
Click to expand...

Alright I just wanted to put a reminder on this information in order to be sure you understood what I was meaning. Otherwise since I downgraded to Crimson 16.1 (assumed working version) my computer only crash once a day at max (today everything has been working great). I run a Prime95 stress test last night and no errors or warnings after 12 hours so I guess my CPU is fine. Just wanted to ask you, the temperature reached 72°C at max is that something I should be worried about ?

I am going to launch a memtest86+ tonight to check if my memory is also doing its part of the job. Finally what should I do with the Fneturpx.sys uninstalling that you adviced on 2 posts ago ?
 
You could try to run driver verifier to get more precise informations.
Try first to enable it using the automatic method at the end of this post, because I excluded your Fneturpx.sys (given that you think it's not the cause).
If you get some errors with that special code, please inform me.
You can exclude it also from verifier itself (just don't select it).
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):
    Read More:
  • Create a restore point
  • Create a system image
  • Make sure you have the Windows installation (or repair) cd (or usb drive) at hand.
    In case the system won't start in its Advanced Startup Options even after many reboots, you'll be forced to use it to restore your PC with the restore point or the system image previously created
  • Read Jcgriff2's 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
  • 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:
    Code: 
    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): nirsoft.net - driverview-x64.zip (click) (for 64bit versions)
  • open notepad, copy the following text and save the file on your desktop as EnableVerifier.ps1:
    Note:
    Code modified to exclude Fneturpx.sys; it should work from WinVista x64 onwards
    Read More:
  • From an elevated command prompt, run:
    powershell -executionpolicy unrestricted "c:\users\%username%\desktop\EnableVerifier.ps1"
    Click to expand...
  • It should appear something like:
    Read More:
  • Reboot your machine and wait the verifier dump (i.e., verifier should force a new BSOD, identifying the problem).
 
Last edited:
Sorry but in previous post, in the powershell code, I used my driverview path...
The correct powershell code is:
Read More:
 
xilolee said:
Sorry but in previous post, in the powershell code, I used my driverview path...
The correct powershell code is:
Read More:
Click to expand...

Sorry for the huge delay to answer your post but I moved on August and I struggled to get an internet connexion in my new home. I just tried what you asked but the powershell command returns 4 errors caused by uncorrect path for the following 2 files extdrivers.txt & temp.txt. Look at the precise powershell returns below (I let it in french as it seems to be comprehensible even if you don't speak french as the microsoft errors are automaticaly returned in English however feel free to ask for the translation if you don't understand something that seems important to you.

Secondly Xiolee I would like to know your advice about this Fneturpx.sys, Do you think I should uninstall it ? (If yes I would be glad to get some explanation on how to do that).

Thank you very much for your help!
Pasranno

Code: 
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.


C:\Windows\system32>powershell -executionpolicy unrestricted "c:\users\%username
%\desktop\EnableVerifier.ps1"
Le chemin d'accès spécifié est introuvable.
Get-Content : Impossible de trouver le chemin d'accès « C:\users\Pas-Ranno\desk
top\extdrivers.txt », car il n'existe pas.
Au niveau de C:\users\Pas-Ranno\desktop\EnableVerifier.ps1 : 7 Caractère : 5
+ type <<<<  $extdrivers | find /i "driver name" | out-file $extdrivers2
    + CategoryInfo          : ObjectNotFound: (C:\users\Pas-Ra...\extdrivers.t
   xt:String) [Get-Content], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo
   ntentCommand


Get-Content : Impossible de trouver le chemin d'accès « C:\users\Pas-Ranno\desk
top\temp.txt », car il n'existe pas.
Au niveau de C:\users\Pas-Ranno\desktop\EnableVerifier.ps1 : 17 Caractère : 19
+ $tmp = get-content <<<<  $tempfile | sort
    + CategoryInfo          : ObjectNotFound: (C:\users\Pas-Ranno\desktop\temp
   .txt:String) [Get-Content], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo
   ntentCommand


Avertissement - Paramètre inattendu ignoré : /bootmode.
Avertissement - Paramètre inattendu ignoré : resetonbootfail.




Nouveaux paramètres de vérificateur :


Pool spécial: Activé
Suivi de pool: Activé
Vérification IRQL forcée: Activé
Vérification d'E/S: Désactivé
Détection de blocage: Activé
Test DMA: Désactivé
Vérifications de sécurité: Activé
Forcer les demandes d'E/S en attente: Désactivé
Simuler ressources faibles: Désactivé
Journalisation IRP: Désactivé
Vérifications diverses: Activé


Pilotes vérifiés :


Aucun




Vous devez redémarrer votre ordinateur pour que les modifications soient prises
en compte.
Remove-Item : Impossible de trouver le chemin d'accès « C:\users\Pas-Ranno\desk
top\extdrivers.txt », car il n'existe pas.
Au niveau de C:\users\Pas-Ranno\desktop\EnableVerifier.ps1 : 24 Caractère : 4
+ del <<<<  $extdrivers, $extdrivers2 , $tempfile, $output
    + CategoryInfo          : ObjectNotFound: (C:\users\Pas-Ra...\extdrivers.t
   xt:String) [Remove-Item], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.Remov
   eItemCommand


Remove-Item : Impossible de trouver le chemin d'accès « C:\users\Pas-Ranno\desk
top\temp.txt », car il n'existe pas.
Au niveau de C:\users\Pas-Ranno\desktop\EnableVerifier.ps1 : 24 Caractère : 4
+ del <<<<  $extdrivers, $extdrivers2 , $tempfile, $output
    + CategoryInfo          : ObjectNotFound: (C:\users\Pas-Ranno\desktop\temp
   .txt:String) [Remove-Item], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.Remov
   eItemCommand
 
xilolee said:
Try this command from a command prompt (simple or elevated):
C:\Users\%username%\Desktop\driverview-x64\driverview.exe /sort 1 /stext c:\users\%username%\desktop\extdrivers.txt
Click to expand...
Click to expand...

I just did it and I think it's now fixed tell me if i'm wrong.

Code: 
Microsoft Windows [version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.


C:\Windows\system32>C:\Users\%username%\Desktop\driverview-x64\driverview.exe /s
ort 1 /stext c:\users\%username%\desktop\extdrivers.txt


C:\Windows\system32>powershell -executionpolicy unrestricted "c:\users\%username
%\desktop\EnableVerifier.ps1"
Avertissement - Paramètre inattendu ignoré : /bootmode.
Avertissement - Paramètre inattendu ignoré : resetonbootfail.




Nouveaux paramètres de vérificateur :


Pool spécial: Activé
Suivi de pool: Activé
Vérification IRQL forcée: Activé
Vérification d'E/S: Désactivé
Détection de blocage: Activé
Test DMA: Désactivé
Vérifications de sécurité: Activé
Forcer les demandes d'E/S en attente: Désactivé
Simuler ressources faibles: Désactivé
Journalisation IRP: Désactivé
Vérifications diverses: Activé


Pilotes vérifiés :


ACPI.sys,AgileVpn.sys,AsrAppCharger.sys,AsrRamDisk.sys,AtihdW76.sys,ATMFD.DLL,ba
mchameleon.sys,bdfwfpf.sys,bdvedisk.sys,Beep.SYS,blbdrive.sys,bowser.sys,bus.sys
,c3.sys,cdd.dll,cdrom.sys,cfosspeed6.sys,CI.dll,ci.sys,ckf.sys,CLASSPNP.SYS,CLFS
.SYS,cng.sys,CompositeBus.sys,crashdmp.sys,csc.sys,cupdate_GenuineIntel.dll,dbss
.sys,dfsc.sys,discache.sys,disk.sys,dpbus.sys,dpdr.sys,dpencdd.sys,dprefmp.sys,d
rmk.sys,drvroot.sys,dtsoftbus01.sys,dump_dumpfve.sys,dump_iaStor.sys,dxata.sys,d
xgkrnl.sys,dxgmms1.sys,dyboost.sys,ETIO.SYS,fd.sys,fileinfo.sys,FLTMGR.SYS,FNETU
RPX.SYS,Fs_Rec.sys,fvevol.sys,fwpkclnt.sys,ga.sys,gdkmd64.sys,GEARAspiWDM.sys,ge
hlp.dll,gnis.sys,gzflt.sys,hal.dll,hcmon.sys,HDAudBus.sys,HIDCLASS.SYS,HIDPARSE.
SYS,hidusb.sys,HTTP.sys,HWiNFO64A.SYS,hwpolicy.sys,IntcDAud.sys,ISCTD.sys,k57nd6
0a.sys,kbdclass.sys,kbdhid.sys,kbevent.sys,kdcom.dll,ks.sys,ksecdd.sys,ksecpkg.s
ys,ksthunk.sys,lltdio.sys,luafv.sys,MBfilt64.sys,Msfs.SYS,ndis.sys,ndistapi.sys,
ndisuio.sys,ndiswan.sys,netadapter.sys,netbios.sys,netbridge.sys,netbt.sys,netus
erif.sys,nsiproxy.sys,ntdll.dll,ntelppm.sys,ntoskrnl.exe,nwifi.sys,ole32.dll,olm
gr.sys,olmgrx.sys,olsnap.sys,onitor.sys,ouclass.sys,ouhid.sys,ountmgr.sys,pacer.
sys,partmgr.sys,pci.sys,PCIIDEX.SYS,pcw.sys,peauth.sys,pfs.SYS,pisetschema.dll,p
mserenum.sys,portcls.sys,Proxy.SYS,psdrv.sys,PSHED.dll,RDPCDD.sys,RDPWD.SYS,RTKV
HD64.sys,sahci.sys,sahci64.sys,serial.sys,sevent.sys,shell32.dll,shidkmdf.sys,si
sadrv.sys,sl2tp.sys,smthub3.sys,smtxhci.sys,sock.sys,spldr.sys,spndr.sys,spppoe.
sys,spptp.sys,spsys.sys,srpc.sys,srv.sys,srv2.sys,srvnet.sys,ssmbios.sys,ssstp.s
ys,sstor64.sys,Stor.sys,stor2-mntapi20-shared.sys,storfl.sys,storport.sys,svcrt.
dll,swenum.sys,tapi.sys,taport.SYS,tcpip.sys,tcpipreg.sys,TDI.SYS,tdtcp.sys,tdx.
sys,TeeDriverx64.sys,termdd.sys,tfs.sys,tikmdag.sys,tikmpag.sys,trufos.sys,TSDDD
.dll,tssecsrv.sys,tunnel.sys,ull.SYS,umbus.sys,up.sys,usb3hcs.sys,usb3hub.sys,us
b3xhc.sys,usbccgp.sys,USBD.SYS,usbehci.sys,usbhub.sys,USBPORT.SYS,utochk.exe,VID
EOPRT.SYS,VMNET.SYS,wanarp.sys,watchdog.sys,Wdf01000.sys,WDFLDR.SYS,wfplwf.sys,w
ififlt.sys,win32k.sys,winhv.sys,wmiacpi.sys,WMILIB.SYS,WPRO_41_2001.sys,ws2ifsl.
sys,x86.sys,xapi.sys,xsmb.sys,xsmb10.sys,xsmb20.sys,zp1endpt.sys,zpmgrk.sys,zpnk
.sys,zudd.sys,zvmouse.sys




Vous devez redémarrer votre ordinateur pour que les modifications soient prises
en compte.

Am I ready to go for the reboot and test ?
 
It seems the /bootmode (resetonbootfail) verifier parameter appeared in windows 8 (or 8.1?) and later OSs, hence it has been ignored by your Win7.
It also seems driverview got a lot of your windows drivers (maybe are they not signed?) and fneturpx.sys wasn't removed from the list.
Re-try with this code:
Read More:
 
xilolee said:
It seems the /bootmode (resetonbootfail) verifier parameter appeared in windows 8 (or 8.1?) and later OSs, hence it has been ignored by your Win7.
It also seems driverview got a lot of your windows drivers (maybe are they not signed?) and fneturpx.sys wasn't removed from the list.
Re-try with this code:
Read More:
Click to expand...

I tried your new code and I got almost no return from it just no parameter has been modified.

Code: 
Microsoft Windows [version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.


C:\Windows\system32>powershell -executionpolicy unrestricted "c:\users\%username
%\desktop\EnableVerifier.ps1"
Aucun paramètre n'a été modifié.

However during the past week I encoutered multiple BSOD I just recovered the minidump files and I will add them here. If you could look at it I would be glad.

View attachment logs.rar
 
xilolee said:
Try to reset the settings and re-try the command.
Click to expand...

Code: 
Microsoft Windows [version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.


C:\Windows\system32>verifier /reset
Aucun paramètre n'a été modifié.


C:\Windows\system32>powershell -executionpolicy unrestricted "c:\users\%username
%\desktop\EnableVerifier.ps1"




Nouveaux paramètres de vérificateur :


Pool spécial: Activé
Suivi de pool: Activé
Vérification IRQL forcée: Activé
Vérification d'E/S: Désactivé
Détection de blocage: Activé
Test DMA: Désactivé
Vérifications de sécurité: Activé
Forcer les demandes d'E/S en attente: Désactivé
Simuler ressources faibles: Désactivé
Journalisation IRP: Désactivé
Vérifications diverses: Activé


Pilotes vérifiés :


32.dll,ACPI.sys,AgileVpn.sys,AsrAppCharger.sys,AsrRamDisk.sys,AtihdW76.sys,ATMFD
.DLL,bamchameleon.sys,bdfwfpf.sys,bdvedisk.sys,Beep.SYS,blbdrive.sys,bowser.sys,
bus.sys,c3.sys,cdd.dll,cdrom.sys,cfgmgr32.dll,cfosspeed6.sys,CI.dll,ci.sys,ckf.s
ys,CLASSPNP.SYS,clbcatq.dll,CLFS.SYS,cng.sys,comctl32.dll,comdlg32.dll,Composite
Bus.sys,cpuz139_x64.sys,crashdmp.sys,crypt32.dll,csc.sys,cupdate_GenuineIntel.dl
l,dbss.sys,devobj.dll,dfsc.sys,difxapi.dll,discache.sys,disk.sys,dpbus.sys,dpdr.
sys,dpencdd.sys,dprefmp.sys,drmk.sys,drvroot.sys,dtsoftbus01.sys,dump_dumpfve.sy
s,dump_iaStor.sys,dvapi32.dll,dxata.sys,dxgkrnl.sys,dxgmms1.sys,dyboost.sys,ETIO
.SYS,fd.sys,fileinfo.sys,FLTMGR.SYS,Fs_Rec.sys,fvevol.sys,fwpkclnt.sys,ga.sys,gd
i32.dll,gdkmd64.sys,GEARAspiWDM.sys,gehlp.dll,gnis.sys,gzflt.sys,hal.dll,hcmon.s
ys,HDAudBus.sys,HIDCLASS.SYS,HIDPARSE.SYS,hidusb.sys,HTTP.sys,HWiNFO64A.SYS,hwpo
licy.sys,IntcDAud.sys,ISCTD.sys,k57nd60a.sys,kbdclass.sys,kbdhid.sys,kbevent.sys
,kdcom.dll,kernel32.dll,KernelBase.dll,ks.sys,ksecdd.sys,ksecpkg.sys,ksthunk.sys
,lltdio.sys,lpk.dll,luafv.sys,MBfilt64.sys,Msfs.SYS,ndis.sys,ndistapi.sys,ndisui
o.sys,ndiswan.sys,netadapter.sys,netbios.sys,netbridge.sys,netbt.sys,netuserif.s
ys,normaliz.dll,normaliz.dll,nsi.dll,nsiproxy.sys,ntdll.dll,ntelppm.sys,ntoskrnl
.exe,nwifi.sys,ole32.dll,oleaut32.dll,olmgr.sys,olmgrx.sys,olsnap.sys,onitor.sys
,ouclass.sys,ouhid.sys,ountmgr.sys,pacer.sys,partmgr.sys,pci.sys,PCIIDEX.SYS,pcr
t4.dll,pcw.sys,peauth.sys,pfs.SYS,pi-ms-win-downlevel-advapi32-l1-1-0.dll,pi-ms-
win-downlevel-normaliz-l1-1-0.dll,pi-ms-win-downlevel-ole32-l1-1-0.dll,pi-ms-win
-downlevel-shlwapi-l1-1-0.dll,pi-ms-win-downlevel-user32-l1-1-0.dll,pi-ms-win-do
wnlevel-version-l1-1-0.dll,pisetschema.dll,pmserenum.sys,portcls.sys,profapi.dll
,Proxy.SYS,psapi.dll,psdrv.sys,PSHED.dll,RDPCDD.sys,RDPWD.SYS,RTKVHD64.sys,sahci
.sys,sahci64.sys,sasn1.dll,sctf.dll,sechost.dll,serial.sys,setupapi.dll,sevent.s
ys,shell32.dll,shidkmdf.sys,shlwapi.dll,sisadrv.sys,sl2tp.sys,smthub3.sys,smtxhc
i.sys,sock.sys,spldr.sys,spndr.sys,spppoe.sys,spptp.sys,spsys.sys,srpc.sys,srv.s
ys,srv2.sys,srvnet.sys,ssmbios.sys,ssstp.sys,sstor64.sys,Stor.sys,stor2-mntapi20
-shared.sys,storfl.sys,storport.sys,svcrt.dll,swenum.sys,syncmac.sys,tapi.sys,ta
port.SYS,tcpip.sys,tcpipreg.sys,TDI.SYS,tdtcp.sys,tdx.sys,TeeDriverx64.sys,termd
d.sys,tfs.sys,tikmdag.sys,tikmpag.sys,trufos.sys,TSDDD.dll,tssecsrv.sys,tunnel.s
ys,tutil.dll,ull.SYS,umbus.sys,up.sys,urlmon.dll,usb3hcs.sys,usb3hub.sys,usb3xhc
.sys,usbccgp.sys,USBD.SYS,usbehci.sys,usbhub.sys,USBPORT.SYS,user32.dll,userenv.
dll,usp10.dll,utochk.exe,VIDEOPRT.SYS,VMNET.SYS,wanarp.sys,watchdog.sys,Wdf01000
.sys,WDFLDR.SYS,wfplwf.sys,wififlt.sys,win32k.sys,winhv.sys,wininet.dll,wintrust
.dll,Wldap32.dll,wmiacpi.sys,WMILIB.SYS,WPRO_41_2001.sys,ws2_32.dll,ws2ifsl.sys,
x86.sys,xapi.sys,xsmb.sys,xsmb10.sys,xsmb20.sys,zp1endpt.sys,zpmgrk.sys,zpnk.sys
,zudd.sys,zvmouse.sys




Vous devez redémarrer votre ordinateur pour que les modifications soient prises
en compte.

Did you found something interesting in the minidump files I uploaded in the previous post ?
 
I still didn't check them, but I'm not a bsod analyst (hence I'm not able to find anything useful).

This time it seems fneturpx.sys isn't present between drivers: you can restart your machine and see if there will be any new dumps.
 
xilolee said:
I still didn't check them, but I'm not a bsod analyst (hence I'm not able to find anything useful).

This time it seems fneturpx.sys isn't present between drivers: you can restart your machine and see if there will be any new dumps.
Click to expand...

I run my computer during the last two days without any BSOD so I guess there is nothing else to blame than what I already gave you. I mean the 4 BSOD I encoutered this week before turning on driver verifier.

Edit: Acutally I'm not sure that driver verifier is really enable, I just try the following command verifier /query
Code: 
Microsoft Windows [version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.


C:\Windows\system32>verifier /query
06/09/2016, 15:53:00
Level : 0002892B
RaiseIrqls : 0
AcquireSpinLocks : 0
SynchronizeExecutions : 0
AllocationsAttempted : 0
AllocationsSucceeded : 0
AllocationsSucceededSpecialPool : 0
AllocationsWithNoTag : 0
AllocationsFailed : 0
AllocationsFailedDeliberately : 0
Trims : 0
UnTrackedPool : 0


Drivers verified :


CurrentPagedPoolAllocations : 0
CurrentNonPagedPoolAllocations : 0
PeakPagedPoolAllocations : 0
PeakNonPagedPoolAllocations : 0
PagedPoolUsageInBytes : 0
NonPagedPoolUsageInBytes : 0
PeakPagedPoolUsageInBytes : 0
PeakNonPagedPoolUsageInBytes : 0
 
xilolee said:
It seems it's enabled, but try also this command: verifier /querysettings
Click to expand...

In fact It is enabled. I assume everything is fine because I didn't disabled it during the last days no BSOD occured. However I would be glad if an analyst could take a look at the minidumps from the BSOD I encoutered before enabling Driver Verifier. Btw can I disable it now ?

Code: 
Microsoft Windows [version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.


C:\Windows\system32>verifier /querysettings
Pool spécial: Activé
Suivi de pool: Activé
Vérification IRQL forcée: Activé
Vérification d'E/S: Désactivé
Détection de blocage: Activé
Test DMA: Désactivé
Vérifications de sécurité: Activé
Forcer les demandes d'E/S en attente: Désactivé
Simuler ressources faibles: Désactivé
Journalisation IRP: Désactivé
Vérifications diverses: Activé


Pilotes vérifiés :


32.dll,ACPI.sys,AgileVpn.sys,AsrAppCharger.sys,AsrRamDisk.sys,AtihdW76.sys,ATMFD
.DLL,bamchameleon.sys,bdfwfpf.sys,bdvedisk.sys,Beep.SYS,blbdrive.sys,bowser.sys,
bus.sys,c3.sys,cdd.dll,cdrom.sys,cfgmgr32.dll,cfosspeed6.sys,CI.dll,ci.sys,ckf.s
ys,CLASSPNP.SYS,clbcatq.dll,CLFS.SYS,cng.sys,comctl32.dll,comdlg32.dll,Composite
Bus.sys,cpuz139_x64.sys,crashdmp.sys,crypt32.dll,csc.sys,cupdate_GenuineIntel.dl
l,dbss.sys,devobj.dll,dfsc.sys,difxapi.dll,discache.sys,disk.sys,dpbus.sys,dpdr.
sys,dpencdd.sys,dprefmp.sys,drmk.sys,drvroot.sys,dtsoftbus01.sys,dump_dumpfve.sy
s,dump_iaStor.sys,dvapi32.dll,dxata.sys,dxgkrnl.sys,dxgmms1.sys,dyboost.sys,ETIO
.SYS,fd.sys,fileinfo.sys,FLTMGR.SYS,Fs_Rec.sys,fvevol.sys,fwpkclnt.sys,ga.sys,gd
i32.dll,gdkmd64.sys,GEARAspiWDM.sys,gehlp.dll,gnis.sys,gzflt.sys,hal.dll,hcmon.s
ys,HDAudBus.sys,HIDCLASS.SYS,HIDPARSE.SYS,hidusb.sys,HTTP.sys,HWiNFO64A.SYS,hwpo
licy.sys,IntcDAud.sys,ISCTD.sys,k57nd60a.sys,kbdclass.sys,kbdhid.sys,kbevent.sys
,kdcom.dll,kernel32.dll,KernelBase.dll,ks.sys,ksecdd.sys,ksecpkg.sys,ksthunk.sys
,lltdio.sys,lpk.dll,luafv.sys,MBfilt64.sys,Msfs.SYS,ndis.sys,ndistapi.sys,ndisui
o.sys,ndiswan.sys,netadapter.sys,netbios.sys,netbridge.sys,netbt.sys,netuserif.s
ys,normaliz.dll,normaliz.dll,nsi.dll,nsiproxy.sys,ntdll.dll,ntelppm.sys,ntoskrnl
.exe,nwifi.sys,ole32.dll,oleaut32.dll,olmgr.sys,olmgrx.sys,olsnap.sys,onitor.sys
,ouclass.sys,ouhid.sys,ountmgr.sys,pacer.sys,partmgr.sys,pci.sys,PCIIDEX.SYS,pcr
t4.dll,pcw.sys,peauth.sys,pfs.SYS,pi-ms-win-downlevel-advapi32-l1-1-0.dll,pi-ms-
win-downlevel-normaliz-l1-1-0.dll,pi-ms-win-downlevel-ole32-l1-1-0.dll,pi-ms-win
-downlevel-shlwapi-l1-1-0.dll,pi-ms-win-downlevel-user32-l1-1-0.dll,pi-ms-win-do
wnlevel-version-l1-1-0.dll,pisetschema.dll,pmserenum.sys,portcls.sys,profapi.dll
,Proxy.SYS,psapi.dll,psdrv.sys,PSHED.dll,RDPCDD.sys,RDPWD.SYS,RTKVHD64.sys,sahci
.sys,sahci64.sys,sasn1.dll,sctf.dll,sechost.dll,serial.sys,setupapi.dll,sevent.s
ys,shell32.dll,shidkmdf.sys,shlwapi.dll,sisadrv.sys,sl2tp.sys,smthub3.sys,smtxhc
i.sys,sock.sys,spldr.sys,spndr.sys,spppoe.sys,spptp.sys,spsys.sys,srpc.sys,srv.s
ys,srv2.sys,srvnet.sys,ssmbios.sys,ssstp.sys,sstor64.sys,Stor.sys,stor2-mntapi20
-shared.sys,storfl.sys,storport.sys,svcrt.dll,swenum.sys,syncmac.sys,tapi.sys,ta
port.SYS,tcpip.sys,tcpipreg.sys,TDI.SYS,tdtcp.sys,tdx.sys,TeeDriverx64.sys,termd
d.sys,tfs.sys,tikmdag.sys,tikmpag.sys,trufos.sys,TSDDD.dll,tssecsrv.sys,tunnel.s
ys,tutil.dll,ull.SYS,umbus.sys,up.sys,urlmon.dll,usb3hcs.sys,usb3hub.sys,usb3xhc
.sys,usbccgp.sys,USBD.SYS,usbehci.sys,usbhub.sys,USBPORT.SYS,user32.dll,userenv.
dll,usp10.dll,utochk.exe,VIDEOPRT.SYS,VMNET.SYS,wanarp.sys,watchdog.sys,Wdf01000
.sys,WDFLDR.SYS,wfplwf.sys,wififlt.sys,win32k.sys,winhv.sys,wininet.dll,wintrust
.dll,Wldap32.dll,wmiacpi.sys,WMILIB.SYS,WPRO_41_2001.sys,ws2_32.dll,ws2ifsl.sys,
x86.sys,xapi.sys,xsmb.sys,xsmb10.sys,xsmb20.sys,zp1endpt.sys,zpmgrk.sys,zpnk.sys
,zudd.sys,zvmouse.sys
 
Yes, you can disable verifier (from an elevated command prompt run verifier /reset then restart windows).
Given that the problem seems to be fneturpx.sys, you could try to uninstall ASRock XFast USB Utility ver:3.02.31, from windows control panel (programs - uninstall a program).
Because it seems that program installs fneturpx.sys.
 
Also, atikmpag.sys shows:
- timestamp Mon Jul 18 22:32:52 2016 (578D3CF4)
- size (if I'm not wrong) 516 kB (528 384 bytes)
- I can't find the version

But the driver I extracted from AMD Radeon Software Crimson Edition 16.7.1_X64 (NON-WHQL edition) (taken from sapphiretech.com - HD 7850 2G D5 - downloads - windows 7 x64 (click)) shows:
- timestamp Wednesday July 6th 2016 04:13:44
- size 486 kB (498 176 bytes)
- version 8.14.1.6512

Hence you could try to update the drivers for your graphic card with that...
Another thing you could check is if you have dust to remove inside your pc, especially from fans and air slits, and if your cpu wants a bit of new thermal past (thermal compound).
Check also the graphic card connector and its slot (remove it, clean the slot and the card connector, re-insert it).
Not sure if you can also change the thermal past on your GPU (I never did it, but it seems it's possible).
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top