BSOD after restarting for Windows update

[oxnume]

My OS is Windows 7 Ultimate x64 Full Retail
I bought the laptop a year and half ago.
The HDD broke down about 2 months ago and I ended up replacing it over the break. After replacing the HDD, I installed Windows 7 a first time and while doing all the Windows updates, I encountered a BSOD after which Windows would not start properly. Fearing defects in the new HDD I installed linux, ran the SMART tool and saw nothing wrong. So I install Windows 7 again a week ago Sunday, and did not do all the updates because I was on slow internet. I just did the Windows update a few hours ago and after restarting this BSOD occurred.

Please help me figure out if there is something seriously wrong with my laptop, thanks.

 

[writhziden]

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


Loading Dump File [J:\BSODDmpFiles\oxnume\Windows_NT6_BSOD_jcgriff2\012412-25927-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02855000 PsLoadedModuleList = 0xfffff800`02a9a670
Debug session time: Tue Jan 24 06:21:35.208 2012 (UTC - 7:00)
System Uptime: 0 days 2:28:49.332
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff96100310ff0, 0, fffff960001d65ae, 5}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+1965ae )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff96100310ff0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960001d65ae, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b04100
 fffff96100310ff0 

FAULTING_IP: 
win32k+1965ae
fffff960`001d65ae 450fb61438      movzx   r10d,byte ptr [r8+rdi]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800739f3d0 -- (.trap 0xfffff8800739f3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000003500 rbx=0000000000000000 rcx=0000000000000010
rdx=0000000000000041 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001d65ae rsp=fffff8800739f560 rbp=fffff8800739f5d0
 r8=00000000fffffff0  r9=0000000000000000 r10=0000000000003000
r11=000000006f013570 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32k+0x1965ae:
fffff960`001d65ae 450fb61438      movzx   r10d,byte ptr [r8+rdi] ds:0004:00000000`fffffff0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000287c3bf to fffff800028d1c40

STACK_TEXT:  
fffff880`0739f268 fffff800`0287c3bf : 00000000`00000050 fffff961`00310ff0 00000000`00000000 fffff880`0739f3d0 : nt!KeBugCheckEx
fffff880`0739f270 fffff800`028cfd6e : 00000000`00000000 fffff961`00310ff0 00000000`00000000 fffff960`00310f00 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0739f3d0 fffff960`001d65ae : fffff900`c32e9998 fffff960`0009a689 fffffa80`05c7c990 fffff880`073a0000 : nt!KiPageFault+0x16e
fffff880`0739f560 fffff900`c32e9998 : fffff960`0009a689 fffffa80`05c7c990 fffff880`073a0000 00000000`050102a6 : win32k+0x1965ae
fffff880`0739f568 fffff960`0009a689 : fffffa80`05c7c990 fffff880`073a0000 00000000`050102a6 fffff900`c32e99f4 : 0xfffff900`c32e9998
fffff880`0739f570 fffffa80`05c7c990 : fffff880`073a0000 00000000`050102a6 fffff900`c32e99f4 fffff880`0739f5d0 : win32k+0x5a689
fffff880`0739f578 fffff880`073a0000 : 00000000`050102a6 fffff900`c32e99f4 fffff880`0739f5d0 00000000`00000001 : 0xfffffa80`05c7c990
fffff880`0739f580 00000000`050102a6 : fffff900`c32e99f4 fffff880`0739f5d0 00000000`00000001 fffff960`00317f00 : 0xfffff880`073a0000
fffff880`0739f588 fffff900`c32e99f4 : fffff880`0739f5d0 00000000`00000001 fffff960`00317f00 00000000`050102bd : 0x50102a6
fffff880`0739f590 fffff880`0739f5d0 : 00000000`00000001 fffff960`00317f00 00000000`050102bd fffff900`c32e9a50 : 0xfffff900`c32e99f4
fffff880`0739f598 00000000`00000001 : fffff960`00317f00 00000000`050102bd fffff900`c32e9a50 fffffa80`05c7c990 : 0xfffff880`0739f5d0
fffff880`0739f5a0 fffff960`00317f00 : 00000000`050102bd fffff900`c32e9a50 fffffa80`05c7c990 fffff900`c32e99f4 : 0x1
fffff880`0739f5a8 00000000`050102bd : fffff900`c32e9a50 fffffa80`05c7c990 fffff900`c32e99f4 fffffa80`069dad78 : win32k+0x2d7f00
fffff880`0739f5b0 fffff900`c32e9a50 : fffffa80`05c7c990 fffff900`c32e99f4 fffffa80`069dad78 00000010`00000000 : 0x50102bd
fffff880`0739f5b8 fffffa80`05c7c990 : fffff900`c32e99f4 fffffa80`069dad78 00000010`00000000 00000008`00000000 : 0xfffff900`c32e9a50
fffff880`0739f5c0 fffff900`c32e99f4 : fffffa80`069dad78 00000010`00000000 00000008`00000000 00000000`00000000 : 0xfffffa80`05c7c990
fffff880`0739f5c8 fffffa80`069dad78 : 00000010`00000000 00000008`00000000 00000000`00000000 0000ff00`00ff0000 : 0xfffff900`c32e99f4
fffff880`0739f5d0 00000010`00000000 : 00000008`00000000 00000000`00000000 0000ff00`00ff0000 000000ff`000000ff : 0xfffffa80`069dad78
fffff880`0739f5d8 00000008`00000000 : 00000000`00000000 0000ff00`00ff0000 000000ff`000000ff 000000ff`000000ff : 0x10`00000000
fffff880`0739f5e0 00000000`00000000 : 0000ff00`00ff0000 000000ff`000000ff 000000ff`000000ff fffff960`00310f00 : 0x8`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+1965ae
fffff960`001d65ae 450fb61438      movzx   r10d,byte ptr [r8+rdi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k+1965ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5b

FAILURE_BUCKET_ID:  X64_0x50_win32k+1965ae

BUCKET_ID:  X64_0x50_win32k+1965ae

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

The crash was fairly inconclusive. Possible causes are Memory problems... Graphics card memory problems... CMOS... Hard disk errors... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.

Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking anything, 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).
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net and |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card.
  
  
  
• Download and install HWiNFO64 Download to check hardware temperatures.
  
  
  
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems.
  
  
  
• Update your chipset drivers through your laptop's manufacturer.
  
  
  
• Reset your BIOS to defaults through the BIOS settings to clear the CMOS. See How To Clear CMOS (Reset BIOS)
  
  
  
• Update your BIOS through your laptop's manufacturer.
  
  
  
• Check for viruses.
  
  Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
  Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
  Download the Fakerean removal tool but do not run it yet.
  Start your computer in http://www.sevenforums.com/tutorials/69585-safe-mode.html
  Unzip VIPRE Rescue and let it run.
  Run a full scan with Malwarebytes.
  Run the fakerean removal tool.​
  
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations. I know your installation is new, but there still may corrupted Windows files, especially if an update failed to completely install.
  
  
  
• Install all Windows Updates.
  
  
  
• 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. Run Driver Verifier
  
  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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.​

 

[oxnume]

Since I am dualbooting with ubuntu and that comes with memtest86+, I just ran it from the grub bootloader and started testing last night. After waking up my computer has already restarted and was just waiting for me at the windows login screen. Does that just mean no errors were found?

 

[writhziden]

Since I am dualbooting with ubuntu and that comes with memtest86+, I just ran it from the grub bootloader and started testing last night. After waking up my computer has already restarted and was just waiting for me at the windows login screen. Does that just mean no errors were found?

Is Windows the default setting through grub? It may have failed and the computer restarted. You may have to run and monitor it, or you can download the bootable version and run that to see if it behaves differently.


Any luck running memtest86+?

 

[oxnume]

I had no way of getting a bootable media with memtest86+ (don't have a blank disc or usb). I decided I would borrow one from a friend if I ever get another BSOD and that hasn't happened yet, so yea... Thanks for all your help so far though and I hope I don't get another BSOD.

 

[writhziden]

Alright, keep us updated. Best wishes the system remains stable.\


Were you able to run memtest86+ eventually?