Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD related to display drivers


  • Please log in to reply
9 replies to this topic

#1 hoopz

hoopz

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:11:28 PM

Posted 23 May 2015 - 01:11 AM

I installed a new MOBO, RAM and CPU a week ago, and ever since I've been struggling with instability. Display drivers stop responding every 5-10 minutes. And I've had 2 BSODs. 

 

· Windows 7
· 64-bit
· Windows 7
· Purchased disc from retail
· CPU, RAM and MOBO are 1 week old. Power Supply, liquid cooling and SSD are 8 months old. The rest are 3 years old.
· Re-installed OS fresh 2 days ago

· CPU: i7-5820k
· Video Card: ASUS 7870HD
· MotherBoard - Gigabyte GA X99 Gaming G1 WIFI
· Power Supply - Corsair CX750M

· System Manufacturer: Custom built
· Exact model number: N/A

· Laptop or Desktop? Desktop

 

EDIT: Running Driver Verifier results in 100% reproducible BSOD. BSOD happens immediately after logging into Windows. Dump file attached.

 

EDIT 2: Added dump file for latest BSOD related to gdrv.sys

 

Attached Files


Edited by hoopz, 23 May 2015 - 01:34 PM.


BC AdBot (Login to Remove)

 


#2 hoopz

hoopz
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:11:28 PM

Posted 23 May 2015 - 03:44 AM

After the last BSOD I ran BlueScreenView and it highlighted a file called "rzpmgrk.sys" which is related to Razer. I have a Razer Blackwidow Ultimate hooked up to my system. Doing a google seach for Razer Blackwidow + Gigabyte GA X99 Gaming G1 reveals 2 - 3 posts where other people are experiencing BSODs. However, no resolutions were posted. This may be a red herring, but thought it might help.



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:28 AM

Posted 23 May 2015 - 05:15 AM

Issues w/new systems always suggest (to me) double or triple checking the connections.  Unplug and replug everything, making sure that the slots/plugs are free of dirt/dust.  Make sure that the power is off and that you are grounded.  I had this problem with a large video card I installed on a Dell computer - and the fix was to reseat the card!

 

The Razer drivers have, in the past, caused BSOD issues - but I haven't seen any significant number recently (for the last year or two)

Still it won't hurt to test them:

- remove/uninstall the Razer drivers

- use another mouse (temporarily) - as there could be a hardware problem with the mouse also.  It never hurts to have a spare mouse around in case yours dies in the middle of the night.

 

I'll try to have a look at the reports after work today.

Meanwhile:

- Update BIOS/UEFI from withing Windows (if it's only able to be updated with a bootable disk outside of Windows - skip it for now)

- Update all drivers from the motherboard manufacturer's page

- Ensure that you have ALL available Windows Updates

- Run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

 

Good luck!

-


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#4 hoopz

hoopz
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:11:28 PM

Posted 23 May 2015 - 01:33 PM

Here's a run down of the latest testing I've done:

 

  • Replaced all Razer peripherals and drivers with generic Dell Keyboard and Mouse. Using Driver Verifier still results in 100% BSOD immediately after login. However, now BlueScreenView highlights gdrv.sys (dump file attached in initial post)
  • I tested 2 video cards (both tested and working in other systems):
    • ASUS 7870HD: Display Drivers stop responding every 5 - 10 minutes. Screen tearing happens during game play. General video lag is experienced. BSODs happen immediately after Display Drivers fail.
    • Geforce GTX Titan: Display Drivers no not stop responding. But screen tearing still happens during game play. General video lag is experienced. BSODs only happen using Driver Verifier.
  • I tested RAM: no issues
  • I tested SSD: no issues
  • I tested CPU (using Intel's diagnostic tools): no issues
  • I've run a variety of benchmarks and scores seem low compared to scores from other similar systems. For example Passmark gave my CPU a 4000 score but average Passmark score for i7-5820k is 12000+
  • One other thing maybe worth mentioning is: Intel lists the 5820k CPU as being compatible with DDR4 1333/1600/2133 and I have DDR-2400 installed (but frequency is set to 2133)

I'm suspecting a faulty Motherboard since I've now experienced instability with 2 working video cards. I'm shipping in another Motherboard to continue testing. 

 

Any help is hugely appreciated.



#5 hoopz

hoopz
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:11:28 PM

Posted 23 May 2015 - 02:54 PM

I figured out how to remove gdrv.sys, and after doing so, I was able to get past login with Driver Verifier on. Having said that, my system still feels unstable. Still getting screen tearing and lag while playing games. I feel like there's a deeper issue going on.

 

Also, is there any chance this could be related to a faulty CPU? It doesn't seem like it, but might as well ask while I still have time to exchange the CPU at the store.


Edited by hoopz, 23 May 2015 - 03:49 PM.


#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:28 AM

Posted 24 May 2015 - 07:38 AM

Sorry for not getting back to you sooner - it was busy around here yesterday :(

 

I'd have suggested removing gdrv.sys after running the dump files - so that's a good thing.
As you can see, sometimes there's multiple drivers involved.  We'll even find that fixing one driver will then break another - or even will stop the BSOD"s but leave you with other problems.

These situations are move complex and usually take longer to fix.

 

CPU is possible (but nothing indicates it at this point) - but if you can hold off, wait until you run Prime 95 and the CPU stress tests from here:  http://www.carrona.org/hwdiag.html

When running Prime95 - run all 3 tests (Blend, Small FFT, Large FFT) - the Blend test stresses RAM mostly, but it does have some CPU impact.  With an i7, the Small and Large FFT's are more

CPU oriented.

 

Just FYI - here's how I do BSOD analysis':
- first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
- then I rule out hardware (less than 10% of BSOD's are due to this)
- then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).

So, i'll post the analysis here.......

 

No device drivers installed for the AudioBox USB.  I'd suggest uninstalling any software for this device and then physically removing it from the system while we're troubleshooting.  I've seen frequent problems with these devices and it's better to test them on a stable machine.

 

Only 210 Windows Updates installed.  Most systems have 300 or more.  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

If the problems continue after all of this, then please submit this report:

 

Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

While waiting for a reply, please monitor your temps with this free utility:  http://www.cpuid.com/softwares/hwmonitor.html

 

Then run Driver Verifier for as long as you can stand it (48 hours max).  It will slow down your system, but if we can get it to crash we may be able to isolate the faulty driver more quickly.

 

I haven't run Win7 dumps in a while, but the scripts are having problems with your dump files:

- they keep checking online symbols - even though the symbols should be stored on my system after the first run (I ran them 3 times)

- there is no output for the template.txt file.  While it's not a big problem, this is the only time that it's happened (and I've run at least one other set of Win7 dumps recently that had it).  I can work without it, but it makes me curious about why it's happening.

 

These are essential parts of the memory dumps:

Debug session time: Sat May 23 13:16:45.894 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\052315-6427-01.dmp]
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
System Uptime: 0 days 0:00:25.799
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
BugCheck C4, {f6, 348, fffffa800f1cc060, fffff8800d7f5809}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000348, Handle value being referenced.
Arg3: fffffa800f1cc060, Address of the current process.
Arg4: fffff8800d7f5809, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  SmiInfo.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = F9
BiosReleaseDate = 01/29/2015
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat May 23 04:22:04.982 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\052315-6505-01.dmp]
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
System Uptime: 0 days 0:00:19.887
*** WARNING: Unable to verify timestamp for rzpmgrk.sys
*** ERROR: Module load completed but symbols could not be loaded for rzpmgrk.sys
Probably caused by : rzpmgrk.sys ( rzpmgrk+1430 )
BugCheck C4, {f6, 60, fffffa800f0e1060, fffff8800acb5430}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000060, Handle value being referenced.
Arg3: fffffa800f0e1060, Address of the current process.
Arg4: fffff8800acb5430, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  userinit.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_rzpmgrk+1430
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = F9
BiosReleaseDate = 01/29/2015
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat May 23 01:23:00.128 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\052215-7534-01.dmp]
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
System Uptime: 0 days 0:19:31.406
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b848 )
BugCheck 116, {fffffa800fd70010, fffff880040e8848, 0, 2}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Bugcheck code 00000116
Arguments:
Arg1: fffffa800fd70010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880040e8848, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = F9
BiosReleaseDate = 01/29/2015
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri May 22 00:52:35.834 2015 (UTC - 4:00)
Loading Dump File [C:\Users\John\SysnativeBSODApps\052115-10998-01.dmp]
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
System Uptime: 0 days 0:16:23.050
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+3a783 )
BugCheck 119, {1, 2a5dc, 2a5de, 2a5dd}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_SCHEDULER_INTERNAL_ERROR (119)[/url]
Bugcheck code 00000119
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000002a5dc
Arg3: 000000000002a5de
Arg4: 000000000002a5dd
BUGCHECK_STR:  0x119
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+3a783
MaxSpeed:     3300
CurrentSpeed: 3300
BiosVersion = F9
BiosReleaseDate = 01/29/2015
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

This is the list of 3rd party drivers found in the memory dumps.

If there's more than one of the same name, it usually means that another with a different timestamp was found in another of the dumps.

This is usually an indication that you've updated the driver.

This does not mean that all of the drivers were found in all of the dumps.  It may be that the driver was just found in one of the dumps.

 

These lists are just meant to help with researching driver updates.  If you have any problems, just post back and we'll help out.

AtihdW76.sys                Sat Jun 21 22:31:21 2014 (53A63FF9)
Netwsw02.sys                Sat May  3 17:39:36 2014 (53656218)
NvStreamKms.sys             Tue Mar 17 02:19:52 2015 (5507C788)
TeeDriverx64.sys            Tue Sep 23 16:01:14 2014 (5421D18A)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys                Thu Nov 20 21:30:27 2014 (546EA3C3)
atikmpag.sys                Thu Nov 20 21:08:54 2014 (546E9EB6)
bflwfx64.sys                Thu Apr 10 11:40:47 2014 (5346BB7F)
btmaux.sys                  Wed Mar 26 04:15:03 2014 (53328C87)
btmhsf.sys                  Fri Apr 18 08:17:24 2014 (535117D4)
cthda.sys                   Wed Aug 27 05:15:28 2014 (53FDA1B0)
e1d62x64.sys                Fri Mar 14 14:22:47 2014 (532348F7)
e22w7x64.sys                Wed Mar 12 12:44:57 2014 (53208F09)
gdrv.sys                    Thu Mar 12 23:22:29 2009 (49B9D175)
iaStorA.sys                 Fri May  2 19:06:56 2014 (53642510)
iaStorF.sys                 Fri May  2 19:07:00 2014 (53642514)
ibtusb.sys                  Fri May  9 18:22:57 2014 (536D5541)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
iqvw64e.sys                 Thu Nov 14 10:22:43 2013 (5284EAC3)
iusb3hcs.sys                Fri May 30 09:18:22 2014 (5388851E)
iusb3hub.sys                Fri May 30 09:16:45 2014 (538884BD)
iusb3xhc.sys                Fri May 30 09:16:48 2014 (538884C0)
lvrs64.sys                  Wed Jan 18 01:40:36 2012 (4F166964)
lvuvc64.sys                 Wed Jan 18 01:41:08 2012 (4F166984)
nvhda64v.sys                Thu Apr 16 15:03:16 2015 (55300774)
nvlddmkm.sys                Mon May 11 21:59:00 2015 (55515E64)
nvvad64v.sys                Thu Nov 20 10:33:54 2014 (546E09E2)
rzendpt.sys                 Tue Dec 30 04:32:47 2014 (54A2713F)
rzpmgrk.sys                 Thu Apr 17 15:36:12 2014 (53502D2C)
rzpnk.sys                   Fri Oct 17 15:38:10 2014 (54417022)
rzudd.sys                   Tue Dec 30 04:32:50 2014 (54A27142)

And here's the links to the DRT for the drivers in the above lists:

http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
Netwsw02.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=bflwfx64.sys
http://www.carrona.org/drivers/driver.php?id=btmaux.sys
http://www.carrona.org/drivers/driver.php?id=btmhsf.sys
http://www.carrona.org/drivers/driver.php?id=cthda.sys
http://www.carrona.org/drivers/driver.php?id=e1d62x64.sys
http://www.carrona.org/drivers/driver.php?id=e22w7x64.sys
http://www.carrona.org/drivers/driver.php?id=gdrv.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=iaStorF.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
 


Edited by usasma, 24 May 2015 - 07:42 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 hoopz

hoopz
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:11:28 PM

Posted 24 May 2015 - 01:02 PM

Thanks for all the great info! Really appreciate it!

 

I will go through all that you recommend. As a quick note, today I turned on Driver Verifier, and after about 20 mins of using it, the Display Drivers stopped responding. This happens every 10-15 mins. No BSOD yet. I will post again after doing more tests.



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:28 AM

Posted 24 May 2015 - 04:39 PM

In most cases, when you get a display drivers stopped responding error message, it's actually a Blue Screen that doesn't show (and actually, it doesn't happen).

The BSOD equivalent of this is a STOP 0x116 error - the version where you don't see/get the BSOD is a STOP 0x117 error.

Also, usually you won't get an easily accessible dump file either.

 

FWIW - here's my canned speech for that sort of error:

Please follow these troubleshooting suggestions:  http://www.sysnative.com/forums/bsod-kernel-dump-analysis-debugging-information/35-video-tdr-timeout-0x116-0x117.html#post29532
Also, please monitor your temps with this free utility:  http://www.cpuid.com/softwares/hwmonitor.html

As you've already tested other video cards, I'd have to wonder about the motherboard at this point.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 hoopz

hoopz
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:11:28 PM

Posted 03 June 2015 - 04:21 PM

Wanted to update my progress on this thread. First off, a big thank you to usasma for taking time to help. This has been a very enlightening experience.

 

To recap:

  • Display Drivers were crashing
  • BSOD was occurring on Login referencing gdrv.sys
  • BSOD was occurring on Login referencing rzpmgrk.sys

Current status:

  • Display Drivers: I ended up replacing my video card. I've had no issues since. It seems my old video card was on its last legs.
  • gdrv.sys: I couldn't figure out how to resolve this other than uninstalling Gigabytes software suite which I think is kind of a sucky solution since I'd like to able to use the suite. In the end, I replaced the motherboard with Asus x99 Deluxe and, obviously, no BSODs with gdrv.sys
  • rzpmgrk.sys: I am still getting 100% BSODs on login related to this file. The only solution I've found is to uninstall Razer Synapse which is also sucky cuz I want to use Synapse with my Razer peripherals. I'm currently stuck on this one and would love some help.

Thanks again!



#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:28 AM

Posted 05 June 2015 - 04:38 AM

Since you've significantly changed the system, please provide a new set of these reports so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

 

Razer drivers had, in the past, been known for causing BSOD's.

I haven't seen them recently, so I have to wonder what's with this one.

 

BSOD's are sometimes caused by one driver, but they're also sometimes caused by conflicts between different drivers.

 

The first step here would be to uninstall the Razer drivers and then run Driver Verifier to see if we can find the "other" driver.

Please use these instructions:  http://www.carrona.org/verifier.html

 

Next, if you don't get BSOD's w/o the Razer drivers, is to update to the latest, Win7 compatible drivers from the Razer website.

Should the BSOD's start again, then it's time for Driver Verifier again.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users