BSOD when placing 4 of 4 dimms


  1. Posts : 4
    Windows 7 home premium 64 bit
       #1

    BSOD when placing 4 of 4 dimms


    I've tried everything so far, replacing the motherboard, replacing the ram dimms, replacing the processor, replacing the video card, replacing even the dvd burner. The only thing that has NOT been replaced is the case. I keep having issues with bsod when I start the computer running with 4 dimms. If I have 2 of the 4 dimms it works just fine, it does not matter WHICH dimms I use however, so any random combination of any of the 2 of 4 works just fine.

    I am running a fresh install of windows, and I have not yet installed much of anything on the computer, nor have I downloaded anything. This has happened WHILE INSTALLING WINDOWS on a freshly formatted hard drive so don't tell me it's a virus.

    I have also found I have random bsod's when the machine is running, have not yet found a correlation for what the cause is for these. I'll post all of them that came in the report attached.

    Let me know if you know what is causing this or if you need more information.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard.

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

    Driver Verifier - Enable and Disable

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  3. Posts : 4
    Windows 7 home premium 64 bit
    Thread Starter
       #3

    didn't work


    I tried to run the verify option, followed the instructions and then my computer could not boot past the welcome screen before getting a bsod referencing gdrv.sys has tried to corrupt the files in my computer. I renamed the file to gdrvbroken.sys and it still would not boot, and still referenced the same (original gdrv.sys) file name which no longer exists in it's original form.

    I've uploaded a new copy of the file report in juxtarose2.zip

    I also had to disable the verify.exe in order to get my computer to boot.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Worked actually.

    Without taking ownership, if a system file is somehow changed, that does not take place actually.

    Yes, it is caused by gdrv.sys. Gigabyte Easy Saver - mobo power utility driver
    Code:
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {f6, 13c, fffffa8010438b30, fffff88007312809}
    
    Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2
    *** 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 )
    
    Followup: MachineOwner
    ---------
    And, it is very old.

    Code:
    0: kd> lmvm gdrv
    start             end                 module name
    fffff880`07311000 fffff880`0731a000   gdrv     T (no symbols)           
        Loaded symbol image file: gdrv.sys
        Image path: \??\C:\Windows\gdrv.sys
        Image name: gdrv.sys
        Timestamp:        Fri Mar 13 08:52:29 2009 (49B9D175)
        CheckSum:         000105CE
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    You are suggested to go to the manufacturer's website and download the latest version.

    Anyway, if you dont install this stuff at all, it does not make a difference.
      My Computer


  5. Posts : 4
    Windows 7 home premium 64 bit
    Thread Starter
       #5

    What do you mean by:

    "Anyway, if you dont install this stuff at all, it does not make a difference." ?

    Are you saying I'll get a BSOD even if I don't install my motherboard's drivers?
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    juxtarose, Gigabyte Utility is not a motherboard driver, but some junk bundled with the motherboard driver CD. During installation, if you dont install it, it will not make any bad, but good.

    You must to install the chipset drivers. But Gigabite utility is not a must.

    On that post, my wise friend Golden said a humble word in my profile --
    Those Gigabyte utilities cause far more trouble than good.
    OK here is an example for you ... it is the screenshot of my motherboard driver cd.
    Attachment 232227
    The unchecked things are already installed, and the checked items are yet to be installed. But they will never ve installed. Why, coz those are not needed at all.

    You can see that I have not installed Intel desktop utilities. I have installed Chipset, Network and Audio drivers only.

    Is it clear now? :)

    If there are any more questions, feel free to ask.
      My Computer


  7. Posts : 4
    Windows 7 home premium 64 bit
    Thread Starter
       #7

    Still no go for 4 of 4 dimms


    OK, so I deleted the program which gdrv.sys came from and now with 2 dimms it's more stable, still though when I put the other 2 dimms in, I get BSOD. It's bad enough that I can't even get to the welcome screen of windows booting without getting a BSOD.

    Maybe 3rd time is the charm?
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Your latest dump indicates hardware.
    Code:
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000096, fffff960001d9848, 1, 100}
    
    Probably caused by : hardware ( win32k!KeepMachineUp+9c )
    
    Followup: MachineOwner
    ---------
    As hardware is a vast area, let us start checking from the CPU, run a stress test.
    Hardware - Stress Test With Prime95

    And, you disable driver verifier now, that is not required in this stage.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:41.
Find Us