Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: gdrv.sys = BSOD in windows 7




  1. #11
    Join Date
    Dec 2009
    Location
    Fla Orange Country
    Posts
    20

    Default Re: gdrv.sys = BSOD in windows 7

    I don't see any info about Dynamic Energy Saver Advanced here ?
    Whats a DDK Driver do ?
    from the error log

    Fault bucket X64_0x3B_gdrv+332d, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1:
    P2:
    P3:
    P4:
    P5:
    P6:
    P7:
    P8:
    P9:
    P10:

    Attached files:
    C:\Windows\Minidump\121009-16380-01.dmp
    C:\Users\Cliff\AppData\Local\Temp\WER-16235070-0.sysdata.xml
    C:\Users\Cliff\AppData\Local\Temp\WER40A.tmp.WERIn ternalMetadata.xml

    These files may be available here:
    C:\Users\Cliff\AppData\Local\Microsoft\Windows\WER \ReportArchive\Kernel_0_0_cab_0bf04177

    Analysis symbol: X64_0x3B_gdrv+332d
    Rechecking for solution: 0
    Report Id: 121009-16380-01
    Report Status: 16
    Last edited by clsA; 12-12-2009 at 05:51 AM.
    Motherboard: Model:GA-EP45-UD3R Rev#: 1.1 Bios Version: F9
    Cpu: Intel® Core™2 Duo Processor E5200 R0 Stepping
    Ram: Patriot Viper 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
    PSU: Corsair HX520
    Cooler Master 690 Case
    Cooler Master Hyper TX3 heatsink

  2. #12
    Join Date
    Aug 2009
    Location
    Birmingham,Great Britain
    Posts
    9,250

    Default Re: gdrv.sys = BSOD in windows 7

    another user has been having the same blue screens with gdrv.sys error he says its something to do with dynamic power saver and that easytune installs it,he cured the blue screens by renaming the gdrv.sys file,try it and see if it stops it,you can always change it back to original name
    Gigabyte z77x UP4-TH F11c Modded Bios
    Intel i7 3770k 24/7@4.8ghz 1.38v Turbo llc +0.165v dvid multithreading enabled
    Samsung Green(MV-3V4G3D/US) 8GB @2133mhz 9-10-10-21-1t 1.55v
    Thermalright Silver Arrow Cpu Cooler
    1xSamsung 840 pro 256 Gb SSD windows 8.1 pro 64bit
    1xSamsung f4 HD204UI 2tb hard drive Storage
    Powercolor 7970 3gb V3 @1150mhz core/1700mhz mem,1.150v Accelero aftermarket air cooler 55c max
    Razer Lycosa Keyboard
    Logitech X-530 5.1 Speakers
    Lite-On iHAS124-19 24x Sata DVDRW
    K-World Hybrid DVB-T 210SE Digital T.V Card
    L.G E2260V L.E.D 1920x1080 Monitor
    Xfx Pro 750w silver rated Psu 80+
    Fractal Arc Midi Case

    http://i38.tinypic.com/14myvfa.jpg x58 ud5 <=3.8ghz + 4.2ghz Overclock Template!!
    http://www.youtube.com/user/warren304#p/u Visit Me On Youtube

    Lots Of Gaming Videos With X58 Ud5 System And Gpu On My Youtube Channel!!
    Just Uploaded New Battlefield 4 Video!!!!!!!!!!!!!!!!!!!!!!

  3. #13
    Join Date
    Dec 2009
    Location
    Fla Orange Country
    Posts
    20

    Default Re: gdrv.sys = BSOD in windows 7

    Quote Originally Posted by wazza300 View Post
    another user has been having the same blue screens with gdrv.sys error he says its something to do with dynamic power saver and that easytune installs it,he cured the blue screens by renaming the gdrv.sys file,try it and see if it stops it,you can always change it back to original name

    lol yeah I searched before posting my problem.

    If your refering to this >> http://forums.tweaktown.com/337167-post7.html
    thats me ...
    Motherboard: Model:GA-EP45-UD3R Rev#: 1.1 Bios Version: F9
    Cpu: Intel® Core™2 Duo Processor E5200 R0 Stepping
    Ram: Patriot Viper 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
    PSU: Corsair HX520
    Cooler Master 690 Case
    Cooler Master Hyper TX3 heatsink

  4. #14
    Join Date
    Aug 2009
    Location
    Birmingham,Great Britain
    Posts
    9,250

    Default Re: gdrv.sys = BSOD in windows 7

    Quote Originally Posted by clsA View Post
    lol yeah I searched before posting my problem.

    If your refering to this >> http://forums.tweaktown.com/337167-post7.html
    thats me ...
    haha and did it stop the blue screening? have you installed easytune yet?
    Gigabyte z77x UP4-TH F11c Modded Bios
    Intel i7 3770k 24/7@4.8ghz 1.38v Turbo llc +0.165v dvid multithreading enabled
    Samsung Green(MV-3V4G3D/US) 8GB @2133mhz 9-10-10-21-1t 1.55v
    Thermalright Silver Arrow Cpu Cooler
    1xSamsung 840 pro 256 Gb SSD windows 8.1 pro 64bit
    1xSamsung f4 HD204UI 2tb hard drive Storage
    Powercolor 7970 3gb V3 @1150mhz core/1700mhz mem,1.150v Accelero aftermarket air cooler 55c max
    Razer Lycosa Keyboard
    Logitech X-530 5.1 Speakers
    Lite-On iHAS124-19 24x Sata DVDRW
    K-World Hybrid DVB-T 210SE Digital T.V Card
    L.G E2260V L.E.D 1920x1080 Monitor
    Xfx Pro 750w silver rated Psu 80+
    Fractal Arc Midi Case

    http://i38.tinypic.com/14myvfa.jpg x58 ud5 <=3.8ghz + 4.2ghz Overclock Template!!
    http://www.youtube.com/user/warren304#p/u Visit Me On Youtube

    Lots Of Gaming Videos With X58 Ud5 System And Gpu On My Youtube Channel!!
    Just Uploaded New Battlefield 4 Video!!!!!!!!!!!!!!!!!!!!!!

  5. #15
    Join Date
    Dec 2009
    Location
    Fla Orange Country
    Posts
    20

    Default Re: gdrv.sys = BSOD in windows 7

    yes just renaming the file stops the problem
    maybe it's just an x64 issue
    Motherboard: Model:GA-EP45-UD3R Rev#: 1.1 Bios Version: F9
    Cpu: Intel® Core™2 Duo Processor E5200 R0 Stepping
    Ram: Patriot Viper 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
    PSU: Corsair HX520
    Cooler Master 690 Case
    Cooler Master Hyper TX3 heatsink

  6. #16
    Join Date
    Apr 2009
    Location
    J'Habite En Angleterre
    Posts
    2,431

    Default Re: gdrv.sys = BSOD in windows 7

    You have the file installed, fair enough. It installs when you install ET6, fine. I don't, and it doesn't install for me. There's no need to try and justify what you've said. Nobody's questioning you. The point of me posting the picture was to show you that the file isn't needed for ET to work and you can delete it without issue.

    If it were extremely common that this file causes BSOD's on a lot of configs then it would have been posted about way before now. As it is it seems pretty isolated as you are the only one to report it here in the 2 months of the RTM release and the 6+ months of the beta and RC. This is why I asked about BSOD data. The law of probability in this case says "Question system stability before questioning the file". Why? because you say you're "struggling" with settings to keep things stable and you haven't (or haven't mentioned) backing down to stock to see if you get the same issues. Is the machine currently with the settings that experienced BSOD's with that file able to pass 24 hours of Prime and a couple dozen IBT runs? If not then it could very possibly be your rig that's the cause. If someone gets smashed in the head with a hammer, what killed them? The hammer or the hole in the head? The hammer killed them, the hole in the head was a consequence of that blow. Like wise the instability could have caused the BSOD and gdrv.sys could have been the file hit by the hammer. I can cause a BSOD that blames the OS Kernel if I were to try running my RAM at 5-4-4-12. That's because the Kernel is getting corrupted in RAM, not because the file is screwed up or causing problems.

    The main point to take from this is, ET works fine without it. Delete it if it's on there and causing issues.

    This is useful info if any others have the problem. They also now know (from a very easy 2 second test) that ET6 can run without the file just fine so it can be deleted. What would also be useful is more info on the BSOD and in the system logs to try and establish if it's the file or if the file is vulnerable to subtle system instabilities. Even a rig that fails Prime after 12 hours and 1 second may be stable enough to be fine, but one day could encounter a certain file that brings it crashing down every time it's loaded.

    Not saying your Rig is unstable. Just that in general, people NEVER think there over clock is at fault. Dunno why. Ego? The strong will never to admit defeat? Who knows. The golden rule with BSOD's and software crashes is to always get rid of the over clock, even if you think it's stable, then test. This is because there's no such thing as stable, just varying degrees of stability.
    Coolermaster CM 690 II advance Case
    Corsair HX750 (CWT, 91%(80+ Gold rated @230V) single 62A 12V rail
    P55A-UD4 v2.0 @ F14
    Core i5 760 @ 20 x 201, 4.02GHz
    TRUE Black with a single Noctua NF-P12 pumping out 55 CFM @ 19db .
    2 x 2GB Mushkin Ridgeback (996902), @ 7-10-8-27, 2010-DDR, 1.66v
    2 x Gigabyte GTX 460 1024MB in SLI (Pre OC'd to 715MHz core and 1800MHz VRAM) @ 850 Core / 4100 Mem.
    Intel X25-M Boot Drive (OS and Programs) 200MB/s Read & 90MB/s Write
    Corsair X32 200MB/s Read & 100MB/s Write
    WD Caviar Blue 640GB C (Steam, Games, Storage, Temp Files & Folders, etc)
    Samsung F3 500GB Backup/Images
    Noctua 1300RPM 19dB case fan (rear extraction)
    3 x 140 MM Coolermaster LED fans (one front intake, one top extraction, one side intake)
    Dell Ultra Sharp 2209WAf E-IPS @ 1680x1050

  7. #17
    Join Date
    Dec 2009
    Location
    Fla Orange Country
    Posts
    20

    Default Re: gdrv.sys = BSOD in windows 7

    Psycho101
    Thanks for your input...but you never answer either of my questions.
    where in the file description does it mention DES or DESA ?

    it's listed as a Server 2003 DDK driver ? what does this mean ?

    Yes Easytune6 works fine without it.
    I'm running a modest overclock and the first thing i did after the blue screen was reset to the optimized defaults and try to recreate the problem. (before renaming the file)

    the 3rd blue screen occurred the next day again after I had left for work and the system went to sleep.
    all 3 times the event log says the same thing:

    Fault bucket X64_0x3B_gdrv+332d, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0

    it's not a big deal ...I just posted the info to try and help anyone else with the same experience and how i fixed mine
    Motherboard: Model:GA-EP45-UD3R Rev#: 1.1 Bios Version: F9
    Cpu: Intel® Core™2 Duo Processor E5200 R0 Stepping
    Ram: Patriot Viper 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
    PSU: Corsair HX520
    Cooler Master 690 Case
    Cooler Master Hyper TX3 heatsink

  8. #18
    Join Date
    Apr 2009
    Location
    J'Habite En Angleterre
    Posts
    2,431

    Default Re: gdrv.sys = BSOD in windows 7

    Sorry I didn't see your questions. I didn't say anything about it being labeled for DES/DESA in the files tag/desctiption. It is however listed on several processes sites (that describe exactly what most common files are for, if they are suspicious etc) that it belongs to or is linked to DESA in some way, mainly installed with it. As I couldn't get it to install with ET6 and am still unwilling to install DESA as I'm highly OC'd I'm not able to verify its presence 100% in the DESA installer. Maybe somebody else can.

    Win 2003 DDK is as far as I know the Driver Development kit designed for creating drivers for use in Win Server 2003. Server 2003 is XP based. This probably just refers to that SDK being the one used to create the driver.

    The Fault Bucket part of the error can just be a misbehaving program accessing RAM that it is not allowed to, causing a BSOD but is usually more indicative of a RAM issue in hardware. Have you had any RAM trouble recently? Any dead or faulty sticks? Any OCing done on the RAM or stability issues tue to either OCing or to simply being at stock? If not then unfortunately this is inconclusive, sadly, as like I say it could be either of the two outcomes that are likely (SW or HW error).

    The install or non install of this file may even be down to something as innocuous as BIOS version (one requiring a driver pass through for something, mine not needing it), or BIOS settings used, EG if using PWM Fan controll it installs/doesn't install and visa versa. A BIOS update (F11 is available) may fix the issue too, or may not. That's the problem with BSOD's, it can be a pain to diagnose but you can narrow things down a little, sometimes by enough other times not.
    Coolermaster CM 690 II advance Case
    Corsair HX750 (CWT, 91%(80+ Gold rated @230V) single 62A 12V rail
    P55A-UD4 v2.0 @ F14
    Core i5 760 @ 20 x 201, 4.02GHz
    TRUE Black with a single Noctua NF-P12 pumping out 55 CFM @ 19db .
    2 x 2GB Mushkin Ridgeback (996902), @ 7-10-8-27, 2010-DDR, 1.66v
    2 x Gigabyte GTX 460 1024MB in SLI (Pre OC'd to 715MHz core and 1800MHz VRAM) @ 850 Core / 4100 Mem.
    Intel X25-M Boot Drive (OS and Programs) 200MB/s Read & 90MB/s Write
    Corsair X32 200MB/s Read & 100MB/s Write
    WD Caviar Blue 640GB C (Steam, Games, Storage, Temp Files & Folders, etc)
    Samsung F3 500GB Backup/Images
    Noctua 1300RPM 19dB case fan (rear extraction)
    3 x 140 MM Coolermaster LED fans (one front intake, one top extraction, one side intake)
    Dell Ultra Sharp 2209WAf E-IPS @ 1680x1050

  9. #19
    Join Date
    Dec 2009
    Location
    Fla Orange Country
    Posts
    20

    Default Re: gdrv.sys = BSOD in windows 7

    I agree 100% that nearly every time i have had BSOD problems it was Ram related.
    and was fixable by lowering settings or upping voltage or a combination of the 2.

    But in this case it seemed different, and a simple rename of the offending file seems to solve the problem.
    I'm back to my Saved OC setting of 9x370 with the ram set to 2.40b (450mhz) and all is well.
    I'm not going to say it's 24hr prime stable but it's running pretty well the 5-6 hrs a day I get to use it :)

    thanks agian for all your help
    Motherboard: Model:GA-EP45-UD3R Rev#: 1.1 Bios Version: F9
    Cpu: Intel® Core™2 Duo Processor E5200 R0 Stepping
    Ram: Patriot Viper 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
    PSU: Corsair HX520
    Cooler Master 690 Case
    Cooler Master Hyper TX3 heatsink

  10. #20
    Lsdmeasap's Avatar
    Lsdmeasap is offline GIGABYTE Guru
    Join Date
    Jan 2008
    Location
    PCB Island
    Posts
    25,940

    Default Re: gdrv.sys = BSOD in windows 7

    I am using x64, so it's not a x64 issue. I still would like to know why that is installing that file, as I do not have it at all. I agree with Psycho though, just rename it or delete it as you have been.

    I am curious why though you have J.Micron drivers installed? Do you have RAID Setup on those ports? If not please uninstall this, if not and you didn't know why or what it was it likely was installed if you used "Express Install" off the motherboard CD, which would have also originally installed DES.

    Just test installed DES for you, and this file is also not installed by DES either it looks like

    Latest Version Dynamic Energy Saver Advanced B9.0904.1



    I do notice odd P35 BIOS files though, these are always included??? Those guys are so silly sometimes!

    *Also*

    If you don't mind, will you please upload a copy of this file for me, thanks!
    Last edited by Lsdmeasap; 12-13-2009 at 03:27 PM.

Page 2 of 3 FirstFirst 123 LastLast

Thread Information

Users Browsing this Thread

There are currently 6 users browsing this thread. (0 members and 6 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •