Solved BSOD after Windows Anytime Upgrade to Windows 7 Professional (64 bit)

[dharrold]

Hi, I upgraded from Windows 7 Home Premium to Windows 7 Professional yesterday using Windows Anytime Upgrade. Very shortly thereafter, my system started crashing with BSOD:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFF98035378E60
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800462B0E9
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

The first two times it happened I was copying files from another computer on my network to a shared folder on the computer that is crashing. The third time was very early this morning while I was not using the computer, though I had kicked off a format of an external USB hard drive the night before that did not complete successfully.

Note that you will see some minidump files from 2/6/14 - 3/12/14 -- I was getting BSOD crashes last year after I first built the system that were resolved by replacing the memory. Then I had one random crash on 4/11/14 and another random one on 4/18/15. The last three (6/24/15 and 6/25/15) started after the Windows 7 Professional upgrade.

Thanks very much for your assistance.

 

[Arc]

Hi dharrold.

Download and install Atheros LAN driver from GIGABYTE - Motherboard - Socket 1155 - GA-Z77-DS3H (rev. 1.0) ... see how it goes. Let us know.
_____________________________________________

BugCheck D1, {fffff98035378e60, 2, 0, fffff8800462b0e9}

*** WARNING: Unable to verify timestamp for L1C62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
Probably caused by : L1C62x64.sys ( L1C62x64+70e9 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff98035378e60, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800462b0e9, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bd100
GetUlongFromAddress: unable to read from fffff800032bd1c0
 fffff98035378e60 

CURRENT_IRQL:  2

FAULTING_IP: 
L1C62x64+70e9
fffff880`0462b0e9 4d8b36          mov     r14,qword ptr [r14]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff88007983570 -- (.trap 0xfffff88007983570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000286
rdx=fffffa8009746c11 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800462b0e9 rsp=fffff88007983700 rbp=fffff9800356efb0
 r8=0000000000000000  r9=0000000000000000 r10=fffff8000353f4c0
r11=fffffa800972af00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
L1C62x64+0x70e9:
fffff880`0462b0e9 4d8b36          mov     r14,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000307fe69 to fffff800030808c0

STACK_TEXT:  
fffff880`07983428 fffff800`0307fe69 : 00000000`0000000a fffff980`35378e60 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07983430 fffff800`0307eae0 : fffffa80`0668e7d0 fffffa80`09722830 00000000`00000000 fffffa80`096d5a20 : nt!KiBugCheckDispatch+0x69
fffff880`07983570 fffff880`0462b0e9 : fffffa80`0908c1a0 fffffa80`096d5a20 fffff980`0356efb0 fffff980`0356efb0 : nt!KiPageFault+0x260
fffff880`07983700 fffffa80`0908c1a0 : fffffa80`096d5a20 fffff980`0356efb0 fffff980`0356efb0 fffffa80`097eccc0 : L1C62x64+0x70e9
fffff880`07983708 fffffa80`096d5a20 : fffff980`0356efb0 fffff980`0356efb0 fffffa80`097eccc0 fffff880`000001c0 : 0xfffffa80`0908c1a0
fffff880`07983710 fffff980`0356efb0 : fffff980`0356efb0 fffffa80`097eccc0 fffff880`000001c0 00000000`00000000 : 0xfffffa80`096d5a20
fffff880`07983718 fffff980`0356efb0 : fffffa80`097eccc0 fffff880`000001c0 00000000`00000000 00000000`00000000 : 0xfffff980`0356efb0
fffff880`07983720 fffffa80`097eccc0 : fffff880`000001c0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff980`0356efb0
fffff880`07983728 fffff880`000001c0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff980`35378e60 : 0xfffffa80`097eccc0
fffff880`07983730 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff980`35378e60 fffff980`35378d30 : 0xfffff880`000001c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
L1C62x64+70e9
fffff880`0462b0e9 4d8b36          mov     r14,qword ptr [r14]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  L1C62x64+70e9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: L1C62x64

IMAGE_NAME:  L1C62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51e4eeac

FAILURE_BUCKET_ID:  X64_0xD1_VRF_L1C62x64+70e9

BUCKET_ID:  X64_0xD1_VRF_L1C62x64+70e9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_vrf_l1c62x64+70e9

FAILURE_ID_HASH:  {fdad5eb7-4877-9e66-73a7-2d24e7bca3fc}

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

0: kd> lmvm L1C62x64
start             end                 module name
fffff880`04624000 fffff880`04646000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Tue Jul 16 12:26:44 2013 (51E4EEAC)
    CheckSum:         0002912C
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[dharrold]

It must have been the Atheros LAN driver because I haven't had any crashes since updating it. Thank you!