Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Again bsod x(

22 Dec 2010   #1

Windows 7 Enterprise x64
Again bsod x(

Look i took again after i done what you said.When I play games i take this bsod after fow hours of playing.
Pls help me. Tomorrow i will change my rams, they are the problem?

Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+ef849
From Address : fffff800`02c1d000
To Address : fffff800`031f9000
Size : 0x005dc000
Time Stamp : 0x4c1c44a9
Time String : 6/19/2010 6:16:41 AM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\ntoskrnl.exe

Filename : win32k.sys
Address In Stack : win32k.sys+89849
From Address : fffff960`00000000
To Address : fffff960`00310000
Size : 0x00310000
Time Stamp : 0x4cbe5d3e
Time String : 10/20/2010 5:08:46 AM
Product Name :
File Description :
File Version :
Company :
Full Path :

My System SpecsSystem Spec
22 Dec 2010   #2

Windows 7 Enterprise x64

Anyone help me?
My System SpecsSystem Spec
22 Dec 2010   #3

Windows 7 Ultimate 32 bit

I'm sorry to hear that you are still having trouble. Your dump does not give a specific cause; but it does indicate memory corruption. Memory corruption can be caused by several thing including, but not necessarily, bad RAM.

Your version of Eset is no known to cause BSOD's; but I did run into a case last week where it is the apparent cause. I suggest you uninstall Eset using this tool: Tool. Download and install Microsoft Security Essentials in its place while you are troubleshooting. Once you get your system stable, you can try Eset again.

I also suggest that you test your RAM with Memtest 86. Follow the instructions in this tutorial. Read the tutorial carefully. Run Memtest from a cold boot after your computer has been off for a couple of hours. Let it run for at least seven passes. This will take 6-8 hours. Post back with your results.
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Wed Dec 22 17:59:26.572 2010 (GMT-5)
System Uptime: 0 days 6:38:15.601
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd96000084678, 8, ffffd96000084678, 7}

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!FreeObject+40 )

Followup: MachineOwner

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

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.
Arg1: ffffd96000084678, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: ffffd96000084678, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000007, (reserved)

Debugging Details:

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec50e0

ffffd960`00084678 ??              ???





PROCESS_NAME:  Garena.exe


TRAP_FRAME:  fffff8800391a970 -- (.trap 0xfffff8800391a970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffff900c1db5920
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=ffffd96000084678 rsp=fffff8800391ab08 rbp=00000000320115bf
 r8=fffff900c22a9d30  r9=000000000000001f r10=fffffa8004610160
r11=fffff900c1f2b010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ffffd960`00084678 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d0c849 to fffff80002c8d740

fffff880`0391a808 fffff800`02d0c849 : 00000000`00000050 ffffd960`00084678 00000000`00000008 fffff880`0391a970 : nt!KeBugCheckEx
fffff880`0391a810 fffff800`02c8b82e : 00000000`00000008 fffffa80`04610160 00000000`00000a00 fffff900`c0000410 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`0391a970 ffffd960`00084678 : fffff960`000c4da0 fffff900`c1f2b010 00000000`00000000 0000001f`00000000 : nt!KiPageFault+0x16e
fffff880`0391ab08 fffff960`000c4da0 : fffff900`c1f2b010 00000000`00000000 0000001f`00000000 00000000`00000000 : 0xffffd960`00084678
fffff880`0391ab10 fffff960`001fbddc : 00000000`00000004 fffff880`0391abc0 00000000`00000000 00000000`00000000 : win32k!FreeObject+0x40
fffff880`0391ab40 fffff960`000c7642 : fffff880`0391abc0 00000000`00000000 00000000`00000000 ffffffff`e4051412 : win32k!bDeleteDCInternalWorker+0x198
fffff880`0391aba0 fffff960`00086558 : 00000000`320115bf fffff880`0391aca0 00000000`00000000 00000000`7efdb000 : win32k!bDeleteDCInternal+0x56
fffff880`0391abf0 fffff800`02c8c993 : fffffa80`023b7b60 fffff880`0391aca0 00000000`04260340 fffffa80`03237de0 : win32k!NtGdiDeleteObjectApp+0x120
fffff880`0391ac20 00000000`74292dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74292dd9


fffff960`000c4da0 eb16            jmp     win32k!FreeObject+0x58 (fffff960`000c4db8)


SYMBOL_NAME:  win32k!FreeObject+40

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  win32k.sys


FAILURE_BUCKET_ID:  X64_0x50_win32k!FreeObject+40

BUCKET_ID:  X64_0x50_win32k!FreeObject+40

Followup: MachineOwner
My System SpecsSystem Spec

23 Dec 2010   #4

Windows 7 Enterprise x64

Today i changed my RAMs and NO BSOD !!!!! FIRST DAY WITH NO BSOD!!! I bought Corsair 3x2gb and after 12 hours of playing games and let my pc on , I HAVE GOT NO BSOD . I hope i will got no bsods starting now .
My System SpecsSystem Spec
23 Dec 2010   #5

Windows 7 Ultimate 32 bit

That is great news!! Thank you for the update. I hope the new RAM solved your problem. Post back in two or three days and update us.
My System SpecsSystem Spec

 Again bsod x(

Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:29.
Twitter Facebook Google+