Windows 7: 1 BSOD and many random freeze(30 sec to 1 Min)

Kemeros · 03 Aug 2010

Hello,

I've been experiencing many random freeze of my computer. Usually when i use Firefox 3.6.8 but it can happen other places too. The only place i seem to have no problem is when i play games. Which is cool but strange.

I've included as asked the bsod dump and perfmon report zip file. Sorry if the perfmon report is partly in french... i didn't find any ways to make the report in english since the windows is in french. Will reinstall in english eventually.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64
- the original installed OS on the system? win 7 pro
- an OEM or full retail version? used a friend's cd to test win 7 pro
currently in the 30 activation period time.

- What is the age of system (hardware)? 2 weeks
- What is the age of OS installation (have you re-installed the OS?) same

Code:

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


Loading Dump File [C:\Users\Kemeros\Desktop\080210-13478-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Mon Aug  2 15:23:17.180 2010 (UTC - 4:00)
System Uptime: 0 days 3:07:31.162
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff90000812000, fd2, fffff900c2c33009}

Probably caused by : win32k.sys ( win32k!memset+b0 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff90000812000
Arg3: 0000000000000fd2
Arg4: fffff900c2c33009

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800376f020 -- (.trap 0xfffff8800376f020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c2a00000 rbx=0000000000000000 rcx=fffff900c2f45000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000143c10 rsp=fffff8800376f1b8 rbp=0000000000000001
 r8=0000000000000004  r9=0000000000000432 r10=000000000000007f
r11=0000000000000034 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k!memset+0xb0:
fffff960`00143c10 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c2f45000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f3ad98 to fffff80002ecb600

STACK_TEXT:  
fffff880`0376ecb8 fffff800`02f3ad98 : 00000000`0000001a 00000000`00005003 fffff900`00812000 00000000`00000fd2 : nt!KeBugCheckEx
fffff880`0376ecc0 fffff800`02ee7b82 : 00000000`00000001 fffff900`c2f45000 fffff880`0376f020 fffff6fc`80617a28 : nt! ?? ::FNODOBFM::`string'+0x29f97
fffff880`0376edb0 fffff800`02ee5bd1 : 00000000`00090570 fffff900`c2af3000 00000000`00000000 00000000`00000004 : nt!MiDispatchFault+0x8c2
fffff880`0376eec0 fffff800`02ec96ee : 00000000`00000001 fffff900`c2a00000 00000000`35316800 00000000`00555c84 : nt!MmAccessFault+0x8f1
fffff880`0376f020 fffff960`00143c10 : fffff960`00132a12 fffff900`c01e6cf0 00000000`00000000 fffff960`00276ffc : nt!KiPageFault+0x16e
fffff880`0376f1b8 fffff960`00132a12 : fffff900`c01e6cf0 00000000`00000000 fffff960`00276ffc fffff960`00144215 : win32k!memset+0xb0
fffff880`0376f1c0 fffff960`00133f2b : 00000000`00000000 fffff880`0376f360 00000000`00000001 fffff960`001315e6 : win32k!AllocateObject+0xf2
fffff880`0376f200 fffff960`0010b4a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`0376f2f0 fffff960`0010b01e : 00000381`00000617 00000000`00000381 00000000`010809c7 00000000`00000617 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`0376f3c0 fffff800`02eca853 : fffffa80`03b9a060 fffff880`0376f520 00000000`00000000 fffff900`c00d2280 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0376f4a0 00000000`75232dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0016d2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75232dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`00143c10 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

FAILURE_BUCKET_ID:  X64_0x1a_5003_win32k!memset+b0

BUCKET_ID:  X64_0x1a_5003_win32k!memset+b0

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

I'm disapointed since i made sure the memory is in the quality list of the board. Still having issues with asus boards i guess.

I did all the windows update... i updated to the latest bios... still no success. I made sure the voltage and cl speed were right for the board and the ram.

Hope you guys can help.

Kemeros

**Capt.Jack Sparrow** · 03 Aug 2010

Hello ! Welcome to SF !

The Dump wasn't very helpful since it's pointing to Core Windows File. Lets run Hardware Diagnostic to make sure everything is fine. Hardware Diagnostic !! « Captain Debugger

Turn on Driver Verifier Using Driver Verifier to identify issues with Drivers

- Captain

The Logs weren't very helpful since it's not English

Kemeros · 03 Aug 2010

Thank you for the quick reply,

Did Memtest86+ already. No errors. No S.M.A.R.T. errors on my drive. Temperatures are ok.

The driver test your talking about sounds like a one way down problems road. Sure it's safe for my stuff?

Kemeros

**Capt.Jack Sparrow** · 03 Aug 2010

Driver Verifier will try to find if a Software is causing the System to crash i.e. if there is any rouge driver. So when you enable the System will run slow and it will cause BSOD. We use Driver Verifier when the Dump files or Logs doesn't give us any clues. So the decision is upto you. We used to recommend this most of the time. And the Memtest86+ has to be ran atleast 6 passes.

Hope this helps,
Captain

Kemeros · 03 Aug 2010

Will redo the memtest right now since i'm going out. Will try to reinstall in english soon and get a proper report. If those 2 steps are still not good enough. Will try the driver thingy.

Thank you for your time and speak to you again soon.

Kemeros