Windows 7: New Mobo, Fresh Win 7 BSODs

Britton30 · 08 Dec 2011

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

panais · 08 Dec 2011

Hi and welcome to sevenforums!

Remove mse beta from your system.

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

Code:

*******************************************************************************
*                                                                             *
*                        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                                    *
*                                                                             *
*******************************************************************************

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: 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:
------------------


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e8b5c0

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: fffff8800317d600

STACK_COMMAND:  dds FFFFF8800317D600-0x20 ; kb

STACK_TEXT:  
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

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

Britton30 · 08 Dec 2011

Quote: Originally Posted by panais

Hi and welcome to sevenforums!

Indeed

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

JMH · 09 Dec 2011

> You might also run...
Driver verifier

Quote:

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/Windows 7 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.

Britton30 · 09 Dec 2011

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.

panais · 10 Dec 2011

Before RMA the motherboard we can try 2-3 steps if you like.

Windows 7: New Mobo, Fresh Win 7 BSODs

New Mobo, Fresh Win 7 BSODs problems?