New
#11
It is most preferrable to use the pc as you normally would, that usually causes the offending driver to be caught.
It is most preferrable to use the pc as you normally would, that usually causes the offending driver to be caught.
I thought so .. there is a problem ,,, while running the verifier it will not let me open battlelog on battlefield , so I cannot play it ,, and its in bf4 that I am getting the bsod
hi axe0 I had trouble running the verifier as you said so I ran it last night with only a few drivers selected ( the bottom 5)
nvhda64v.sys
nvlddmkm.sys
e22w7x64.sys
rtkvhd64.sys
bflwfx64.sys
I had a bsod but it was after I had to plug in my mouse .then after the 1st bsod I had many trying to get the pc back on.so I have uploaded the main dump for you..
Please update the drivers of your razer device(s) and/or software via the support page of razer.
The flagged driver is 11 years old, if no driver update is available then the only option is to remove the device(s) and/or software.
Code:4: kd> lmvm Razerlow Browse full module list start end module name fffff880`05b81000 fffff880`05b86280 Razerlow T (no symbols) Loaded symbol image file: Razerlow.sys Image path: Razerlow.sys Image name: Razerlow.sys Browse all global symbols functions data Timestamp: Mon Nov 07 07:33:11 2005 (436EF527) CheckSum: 0000B007 ImageSize: 00005280 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
hi axe0 I am still testing with a totally new mouse and sofar no bsod . I will give it till after this weekend then mark this thread as solved
thnk you very much for all your help and time