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: New Mobo, Fresh Win 7 BSODs

08 Dec 2011   #1
Microsoft MVP

Windows 7 Ultimate X64 SP1
New Mobo, Fresh Win 7 BSODs

Just installed a new motherboard, SSD and Windows 7 ult X64.
Keyboard isn't seen during bootup so can't make selections after BSOD, i.e., diag start, normal start, etc.
Tried to see a video on MSN=BSOD
Ran Performance Index=BSOD
Run elevated cmd with winsat mem=BSOD or stopped working
IE8 continually stops working
Running MSE Beta and updates fail or=BSOD
Attachment 187311

My System SpecsSystem Spec
08 Dec 2011   #2

Windows 7 Ultimate 64bit SP1

Hi and welcome to sevenforums!

Remove mse beta from your system.

Run RAM - Test with Memtest86+
Leave it to run overnight if needed.

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8958af880, b3b7465ee808d662, fffff8800162783d, 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

2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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
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.
Arg1: a3a039d8958af880, Reserved
Arg2: b3b7465ee808d662, Reserved
Arg3: fffff8800162783d, 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:






LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e8b5c0



STACK_COMMAND:  dds FFFFF8800317D600-0x20 ; kb

fffff880`0317d5e0  00000109
fffff880`0317d5e4  00000000
fffff880`0317d5e8  958af880
fffff880`0317d5ec  a3a039d8
fffff880`0317d5f0  e808d662
fffff880`0317d5f4  b3b7465e
fffff880`0317d5f8  0162783d
fffff880`0317d5fc  fffff880
fffff880`0317d600  00000001
fffff880`0317d604  00000000
fffff880`0317d608  00000000
fffff880`0317d60c  00000000
fffff880`0317d610  00000000
fffff880`0317d614  00000000
fffff880`0317d618  00000000
fffff880`0317d61c  00000000
fffff880`0317d620  00000000
fffff880`0317d624  00000000
fffff880`0317d628  00000000
fffff880`0317d62c  00000000
fffff880`0317d630  00000000
fffff880`0317d634  00000000
fffff880`0317d638  00000000
fffff880`0317d63c  00000000
fffff880`0317d640  00000000
fffff880`0317d644  00000000
fffff880`0317d648  00000000
fffff880`0317d64c  00000000
fffff880`0317d650  00000000
fffff880`0317d654  00000000
fffff880`0317d658  00000000
fffff880`0317d65c  00000000

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff8800162786d - ndis!NdisMAllocateNetBufferSGList+1bd
    [ 90:91 ]
1 error : !ndis (fffff8800162786d)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption





Followup: memory_corruption
My System SpecsSystem Spec
08 Dec 2011   #3
Microsoft MVP

Windows 7 Ultimate X64 SP1

Quote   Quote: Originally Posted by panais View Post
Hi and welcome to sevenforums!

I got another BSOD as soon as windows started, will collect dumps an attach to this post soon.soon.
My System SpecsSystem Spec

09 Dec 2011   #4

Win 7 Ultimate 64-bit. SP1.

> You might also run...
Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users[/B]

> Also suggest you update to SP1 asap.
My System SpecsSystem Spec
09 Dec 2011   #5
Microsoft MVP

Windows 7 Ultimate X64 SP1

OK Jan, SP1 installing now. I have no other dumps to upload at the moment, dunno where they went. Will give verifier a go.
Ram has passed memtest86+.
Edits: SP1 failed on first attempt, did install on 2nd attempt along with 10's of other updates, 63 of them.

First BSOD at 18:45 with verifier running while posting a youtube here.

Bad motherboard, disregard. PC is now in parts.
My System SpecsSystem Spec
10 Dec 2011   #6

Windows 7 Ultimate 64bit SP1

Before RMA the motherboard we can try 2-3 steps if you like.
My System SpecsSystem Spec

 New Mobo, Fresh Win 7 BSODs

Thread Tools

Similar help and support threads
Thread Forum
BSOD after formatting HDD for fresh windows install (new mobo)
So I fried my old motherboard last week and just replaced it with an Asus Z-77A. I used my roommates pc to format my old hard drive and did a fresh windows 7 Ultimate 64-bit install on it via USB drive. After installing windows and installing all drivers that came with the mobo CD and the most...
BSOD Help and Support
New mobo. Fresh win7 install?
Hi guys. Just received a new mobo, and somewhere I read that you need to do a fresh win7 install when swapping. Is this so? Thanks for any advice you can provide, J
Installation & Setup
How Do I Reset Mobo To Original In-The-Box State - Fresh Start Desired
Hello Gents, My name is James & this is my first post here. I built my own rig last year for the first time ever, and installed everything just fine. But now I have purchased a number of SSDs, and really just want to start all over again right from scratch. I'm talking about resetting...
Installation & Setup
Fresh Install (due to new MOBO) Error 0x80070570
Hey Sevenforums, About a year ago I decided to build my first computer. I did so and there was much rejoicing. That is until it started BSODing everywhere when I played video games or watched Netflix. Coming to your forums I was encouraged to do a memtest, got new RAM, for a while the problem...
Installation & Setup
BSOD after fresh install + on new MoBo/HDD/RAM
Hi everyone this is my first post on this Forum. I recently upgraded my HDD, Motherboard and RAM. My computer is a custom build and 4 days ago after upgrading i installed Win7 Ultimate 32bit + drivers and softwares. Everything went perfectly fine during installation and also i copied the data from...
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 05:34.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App