BSOD when trying to run windows update (or occasionally with IE)

dabman · 25 Dec 2012

Hi,

I purchased a new PC today (spec below) and after booting it up for the first time and attempting to perform some windows updates, I found that some updates were failing to install, with no clear reasoning as to why. After this, I quite often get BSOD when loading windows update (seems to centre round .NET installations), trying to update drivers (primarily graphics) and occasionally just randomly with no discernable pattern.

I have attempted various fixes posted on the net for this type of error, including some tools from the microsoft website which also failed to complete.

I attach a zipped copy of the dmp files in line with your posting policy in the hope that someone can point me in the right direction. This was a Christmas gift and it would be heartening to be able to resolve this issue without having to send the entire machine back.

Should you require any more info, just ask and I will post.

Thanks!

B

SPEC:

Intel Core I7 3770 @ 3.40GHz
8GB RAM
MSI MS-7808 Mainboard
NVIDIA GTX650
Win7 Home Premium

koolkat77 · 25 Dec 2012

Welcome to SevenForums.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000c8ed70, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000c8ed70
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  drvinst.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d49b50 to fffff80002cddfc0

STACK_TEXT:  
fffff880`0b971818 fffff800`02d49b50 : 00000000`0000001a 00000000`00041790 fffffa80`00c8ed70 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0b971820 fffff800`02cca81f : fffffa80`00000000 00000000`0138ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0b9719e0 fffff800`02cdd253 : ffffffff`ffffffff 00000000`00a3f7a8 00000000`00a3f7a0 000007fe`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0b971ae0 00000000`776d14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00a3f728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776d14fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35054
fffff800`02d49b50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35054

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

Followup: MachineOwner
---------

Perform Memtest.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

Let us know the results.