Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after fresh install of win 7 ultimate x64

22 Mar 2012   #1

Windows 7 Ultimate x64 SP1
 
 
BSOD after fresh install of win 7 ultimate x64

So I know there a few other people have the same issue but I think mine might be different. I'm currently running in Safe Mode right now because I can't sit on standard boot too long before I have a random BSOD. It's completely random and very annoying, I need help as soon as I can get it. I'll be back with my minidump file shortly, in the mean time here are my specs:

CPU: Intel i5 2300
PSU:diablotek 600W
Memory: PNY Optima PC3-10666 2x4GB
GPU: Geforce 550 Ti
Mobo: GIGABYTE Z68AP-D3
Soundcard: none
Case: Custom
PS. I thought maybe this was an install issue so I reinstalled Windows 7 x64 again without downloading any updates and its still giving me grief.

My System SpecsSystem Spec
.

22 Mar 2012   #2

Windows 7 Ultimate x64
 
 

As soon as we have the dump, we can assist you
My System SpecsSystem Spec
22 Mar 2012   #3

Windows 7 Ultimate x64 SP1
 
 

Alright here my info, have a crack at it
My System SpecsSystem Spec
.


22 Mar 2012   #4

Windows 7 Ultimate x64 SP1
 
 

I have read the BSOD reporting sticky, and it looks like I've followed it nearly to the T. Has anyone looked at my dump files yet?

Thanks in advance,

Inous
My System SpecsSystem Spec
22 Mar 2012   #5

Windows 7 Home Premium 64 Bit
 
 

Security Software: ???

Possible out of date driver:
Code:
gdrv	fffff880`0774e000	fffff880`07757000	Thu Mar 12 21:22:29 2009 (49b9d175)	000105ce		gdrv.sys
Remove Gigabyte Easy Saver - mobo power utility.


Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\Inous\Dump Data\032112-23337-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03298e90 Debug session time: Wed Mar 21 23:23:03.471 2012 (UTC - 6:00) System Uptime: 0 days 0:02:32.330 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffe2802dbd9cda, 1, fffff88000d5aa5a, 7} Could not read faulting driver name Probably caused by : memory_corruption Followup: memory_corruption --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffe2802dbd9cda, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff88000d5aa5a, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800033040e8 ffffe2802dbd9cda FAULTING_IP: CLFS!CClfsBaseFilePersisted::OpenImage+2a6 fffff880`00d5aa5a 8c24a8 mov word ptr [rax+rbp*4],fs MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000 STACK_TEXT: 00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0 STACK_COMMAND: .bugcheck ; kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !CLFS fffff88000d5aa58 - CLFS!CClfsBaseFilePersisted::OpenImage+2a4 [ 44:04 ] 1 error : !CLFS (fffff88000d5aa58) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\Inous\Dump Data\032112-19422-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`03294e90 Debug session time: Wed Mar 21 23:19:12.245 2012 (UTC - 6:00) System Uptime: 0 days 0:17:55.104 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d89bbed72e, b3b7465eee3ba684, fffff800034027bf, 1} Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d89bbed72e, Reserved Arg2: b3b7465eee3ba684, Reserved Arg3: fffff800034027bf, Failure type dependent information Arg4: 0000000000000001, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000 STACK_TEXT: 00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff800034029af - nt! ?? ::NNGAKEGL::`string'+14095 [ 80:00 ] 1 error : !nt (fffff800034029af) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------
  1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Antivirus Software... Drivers...
  2. Possible causes are Memory problems... Drivers...
Thanks to Dave76 for help understanding possible causes.


Do the following to determine which is causing issues, your drivers or your memory:
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. In Windows 7:
    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      Attachment 203957
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
My System SpecsSystem Spec
22 Mar 2012   #6

Windows 7 Ultimate x64 SP1
 
 

Thanks for the timely response!

I forgot to mention this is a brand new computer that I just built two days ago. I too thought it was memory to beign with so i did a memtest that revealed no problems. I suspect the culprit is the video card drivers as I noticed it started doing this right after a restart with the new drivers installed. I am curently using the drivers that came with the card itself and stress testing it to see if it will cause a BSOD. I'll report back with further information.

PS I uninstalled the Energy saver and it still BSOD so that rules that out.
My System SpecsSystem Spec
22 Mar 2012   #7

Windows 7 Ultimate x64 SP1
 
 

UPDATE: alright, doesnt seem to be the drivers for gfx card as I'm still getting the Blue screen. I used the verifier, and it seems to crash on gdrv.sys.

I'm starting to think that this whole GIGABYTE motherboard is beginning tobecome too much of hassle and I'm going to return it for a different motherboard.

Next crash I'll upload dump files
My System SpecsSystem Spec
22 Mar 2012   #8

Windows 7 Home Premium 64 Bit
 
 

I recommended that you remove the Gigabyte Easy Saver - mobo power utility before running Verifier for that reason... See my previous post.
My System SpecsSystem Spec
22 Mar 2012   #9

Windows 7 Ultimate x64 SP1
 
 

I removed it and I was still getting the BSOD. heres the files

EDIT: I just swapped GFX cards from my other computer to see if it will still produce the same BSOD. So far so good
My System SpecsSystem Spec
23 Mar 2012   #10

Windows 7 Home Premium 64 Bit
 
 

The last two crashes were still pointing to memory. It could be graphics card memory. See how things go with the other display card. Is there any difference between the cards; does one require more power than the other?
My System SpecsSystem Spec
Reply

 BSOD after fresh install of win 7 ultimate x64




Thread Tools




Our Sites

Site Links

About Us

Find 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 11:12 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33