BSOD While playing a game...

The big question I'm having is why overclocking in Windows 7 is such an issue. Personally I've lowered my speeds after upgrading from Vista, but still get an occasional BSOD which is quite annoying.

Why does Vista and XP handle overclocking at higher speeds with no issues? What makes Windows 7 different?

HughShaw said:

The big question I'm having is why overclocking in Windows 7 is such an issue. Personally I've lowered my speeds after upgrading from Vista, but still get an occasional BSOD which is quite annoying.

Why does Vista and XP handle overclocking at higher speeds with no issues? What makes Windows 7 different?

I can't answer that question. I'm not a software engineer. There are also too many variables. I'm not saying this is your case, but in general, perhaps you were running x86 with Vista/XP - perhaps different chipset drivers driving to a higher degree...who knows?

Best thing you can do for your machine is to test with no overclock. If a bsod happens, we will be more than happy to offer further suggestions.

torrentg said:

Please see this link.

The error is due to a read operation involving csrss.exe and win32k.sys.

Considering the overclock, it would be my first and only recommendation at this point to run default as a test. Overclock after if test is successful, to a lesser degree.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\Files\111009-25724-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`0323fe50
Debug session time: Tue Nov 10 19:07:21.367 2009 (GMT-5)
System Uptime: 0 days 0:45:42.131
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {3, 2, 0, fffff80003077ffb}

Probably caused by : win32k.sys ( win32k!WakeRIT+37 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003077ffb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032aa0e0
 0000000000000003 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+16b
fffff800`03077ffb 488b1b          mov     rbx,qword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  fffff88005499400 -- (.trap 0xfffff88005499400)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=1e2ccc9de1880000
rdx=fffffffffffffffd rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003077ffb rsp=fffff88005499590 rbp=0000000000000000
 r8=ffffffffffffff63  r9=fffffa8005cedc10 r10=fffff80003002000
r11=fffff88005499560 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeSetEvent+0x16b:
fffff800`03077ffb 488b1b          mov     rbx,qword ptr [rbx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003073469 to fffff80003073f00

STACK_TEXT:  
fffff880`054992b8 fffff800`03073469 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`054992c0 fffff800`030720e0 : fffffa80`05fda760 00000000`00000003 fffffa80`05f1a000 fffff880`05499478 : nt!KiBugCheckDispatch+0x69
fffff880`05499400 fffff800`03077ffb : fffffa80`05c36d50 00000000`00000003 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`05499590 fffff960`000b93c3 : 00000000`00000000 fffff880`00000001 00000000`00000000 fffffa80`05d05850 : nt!KeSetEvent+0x16b
fffff880`05499600 fffff960`0016739e : fffff880`05499c20 fffffa80`05bb4b30 00000000`00000000 00000000`00000000 : win32k!WakeRIT+0x37
fffff880`05499630 fffff960`00167b19 : fffff900`c01ecdcc 00000000`0029d76b fffff900`c01ecd40 00000259`000003be : win32k!QueueMouseEvent+0x192
fffff880`05499660 fffff960`00167930 : fffff900`c01ecd40 00000259`000003be 00000000`00000000 00000000`00000286 : win32k!ProcessMouseInput+0x1d5
fffff880`054996d0 fffff800`03050969 : 00000000`00000100 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!InputApc+0x7c
fffff880`05499700 fffff800`0307b25d : fffffa80`05cf7b60 00000000`00000000 fffff960`001678b4 00000000`00000000 : nt!KiDeliverApc+0x211
fffff880`05499780 fffff800`0307754b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
fffff880`05499810 fffff960`001086e8 : fffff900`00000002 fffffa80`050d3e00 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x271
fffff880`05499ac0 fffff960`00109604 : 00000000`00000000 fffff900`c013e010 fffff960`0034f340 fffff900`c013eea0 : win32k!xxxMsgWaitForMultipleObjects+0x108
fffff880`05499b40 fffff960`000c4720 : fffffa80`00000001 fffffa80`0000000c fffffa80`05cf7b60 fffff6fc`4002a398 : win32k!xxxDesktopThread+0x254
fffff880`05499bc0 fffff960`00143ea6 : fffffa80`00000001 fffff960`0034f340 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64
fffff880`05499bf0 fffff800`03073153 : fffffa80`05cf7b60 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`05499c20 000007fe`fd683d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0214f9b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd683d3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!WakeRIT+37
fffff960`000b93c3 4883c428        add     rsp,28h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!WakeRIT+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

FAILURE_BUCKET_ID:  X64_0xA_win32k!WakeRIT+37

BUCKET_ID:  X64_0xA_win32k!WakeRIT+37

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

I thought the csrss.exe showed up because it was something that closed along with the restart, or basically something that got in the way with the restart.

Do you think it could be my video drivers or would that produce a different error?

I know you kind of answered this above but, knowing my OC is stable, under temperatures etc, what in 7 could cause it or what would you guess is causing it? With this BSOD being the first one I've had, and how random it is I'm having trouble guessing what it is.

My first guess would be drivers but, I can't reproduce the BSOD so I'm not sure.

Perhaps the current Nvidia drivers are not yet fully compatible with Windows 7. At least that's what I'm hoping for.

HughShaw said:

Perhaps the current Nvidia drivers are not yet fully compatible with Windows 7. At least that's what I'm hoping for.

I've read some other posts on here and other forums about Nvidia drivers causing BSOD after installs etc. Not sure it's the same but, could be an issue.

If it means anything, I've been beta testing since last year with both NVIDA and ATI machines. Never have I run into a driver problem with either and I tried all...betas, normal, always latest, my own edits...etc...

Do you think Ati Tray tools could cause it?

I ran it in vista 64, but in windows 7 it requires driving signing, and you have to bypass it to use them. Which means running driver signature enforcement override in "test mode".

Not sure that could be it, but it's one thing I haven't changed. I updated it etc when I upgraded.

I don't think so but anything is possible. I don't run x64 machines so I wouldn't know.

I said already what I think is the cause of the bsod.

No I know.

I installed two driver updates since the BSOD which were my NIC and Sound driver.

I also deleted daemon tools, which wasn't running but was causing a different error. (may or may not be related to the BSOD)

And finally, trying the regular CCC drivers over ATI Tray tools.

If I get another BSOD while playing the game I will reset the overclock to default and go from there.

Let us know how it goes! I'm currently testing for BSOD using lower overclocked settings. Everything seems good so far.

I think we need to get the word out that Windows 7 will not handle as high of an overclock as Vista/XP did. So everyone that is using the same exact settings which worked for them 100% in Vista/XP can not expect to get the same speeds w/o getting an occasional BSOD.