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: Numerous BSODs on fresh install/new build after windows updates..


28 Mar 2012   #1

Windows 7 Home Premium 64 bit
 
 
Numerous BSODs on fresh install/new build after windows updates..

Hello, all. I built my first gaming PC last week. The build went well, but the following day, I got 2 or 3 random bsod's, mainly on start up. Updated mobo bios hoping it would solve the problem. System was stable for a couple days, then started getting bsod's again. One on start up, one after computer was idle. After another crash after booting up my PC last night, I decided to do a clean reinstall of Windows 7 (64 bit) and just start over. Got all "up to date" drivers for all components, did not install any extra programs other than Steam and Norton. Everything was running fine... until I started performing the numerous Windows Updates. Then, it started happening again. BSOD's. I have ran checks on the RAM, SSD, etc, but have come up with no issues. Must be a conflict with 1 (or more) of the windows updates/drivers? I restored from a previous point where windows was working last night, but am getting crashes again now this morning. I tried uninstalling Norton to see if that was the issue, but that did not help. I would really like to figure out what is causing this? I have already had 3 or 4 random bsod's this morning... Any help would be greatly appreciated. I have uploaded the data/reports requested in the "how to post on this thread" with this post. I am new at this, but am somewhat technically sound, and can give you any info you need to provide me with any help. Once again, thank you.
P.S.
My set up- (just in case you need it)

Windows 7 (64 bit OEM)
i7 2600k
Asus P8z68-v/gen3
Corsair Force 3 120gb SSD
EVGA gtx 480
Seasonic x650 power supply
Corsair h100 cpu cooling
Corsair 500r case
Corsair Vengeance RAM 1600 8gb

My System SpecsSystem Spec
.

28 Mar 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Re-install Norton. It most likely is not the culprit (assuming it is up to date and the 2012 version) in your crashes and you need a security program installed on your system.


Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\breakingadam\Windows_NT6_BSOD_jcgriff2\032812-7815-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03250650
Debug session time: Wed Mar 28 09:26:19.788 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:02.505
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d898470709, b3b7465eeac3d65f, fffff8000303f817, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

4: 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: a3a039d898470709, Reserved
Arg2: b3b7465eeac3d65f, Reserved
Arg3: fffff8000303f817, 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 fffff80003088d40

STACK_TEXT:  
fffff880`03377498 00000000`00000000 : 00000000`00000109 a3a039d8`98470709 b3b7465e`eac3d65f fffff800`0303f817 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8000303f8d5 - nt! ?? ::FNODOBFM::`string'+2e04e
	[ ff:7f ]
1 error : !nt (fffff8000303f8d5)

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
---------
This crash points to either Memory problems... Drivers...
  • If you are overclocking any hardware, please stop.

  • 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 205249
    • 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.

Also, since you have an SSD, the crashes may be related to the SSD. Make sure your firmware is up to date, you have the most up to date chipset drivers from Intel® Driver Update Utility (even if it says it is valid, go to the link provided and download the latest driver; valid does not mean up to date), and your SATA controllers are all up to date from their manufacturers. Use ASUS - Motherboards- ASUS P8Z68-V/GEN3 to find the storage controller manufacturers (one is Intel and can be updated the same way as the chipset described above, the other is jmicron and appears to be up to date on the motherboard site).
My System SpecsSystem Spec
Reply

 Numerous BSODs on fresh install/new build after windows updates..




Thread Tools



Similar help and support threads for2: Numerous BSODs on fresh install/new build after windows updates..
Thread Forum
Freezes & BSODs Even After fresh Windows Install BSOD Help and Support
Solved random BSODs on windows 7 fresh install BSOD Help and Support
Solved Unable to install updates on fresh Windows 7 SP1 install Windows Updates & Activation
Solved Fresh Install - Updates download (Windows 7 ) Installation & Setup
BSOD numerous different messages even after a fresh install of win7 BSOD Help and Support
Solved BSODs after Fresh Windows 7 Install (new hard drive) BSOD Help and Support
Repeated BSOD after fresh install, possibly due to windows updates BSOD Help and Support

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 08:31 PM.
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