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: help, please.

27 May 2010   #31

Windows 7 Professional x64

Sure, that sounds good.

My System SpecsSystem Spec
27 May 2010   #32


I did it, whilst installing, my screen got entirely black multiple times but with no effect on system, after installation no problem-so its probably because of lack of driver...

Ill post if I have any further problems until next time rep+ for ya thx very much
My System SpecsSystem Spec
27 May 2010   #33

Windows 7 Professional x64

You're very welcome. I hope the problem is solved now.

Let us know if you need anything else.
My System SpecsSystem Spec

27 May 2010   #34


oops, another one.
what could it be?
My System SpecsSystem Spec
27 May 2010   #35

Windows 7 Ultimate 32 bit

Mikios, what were you doing when you got this last BSOD? What program(s) were you running?
My System SpecsSystem Spec
27 May 2010   #36

Windows 7 Professional x64

I can't believe I didn't recommend a memory test yet.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

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

Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\\052810-21450-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a63000 PsLoadedModuleList = 0xfffff800`02ca0e50
Debug session time: Thu May 27 19:35:30.116 2010 (GMT-4)
System Uptime: 0 days 1:14:55.066
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff67f9a02af99, 0, fffff80002b04b43, 7}

Could not read faulting driver name
Probably caused by : hardware ( win32k!SURFACE::bDeleteSurface+3a2 )

Followup: MachineOwner

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

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0b0e0

fffff800`02b04b43 0000            add     byte ptr [rax],al





PROCESS_NAME:  chrome.exe


TRAP_FRAME:  fffff88006c12160 -- (.trap 0xfffff88006c12160)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff68000031d10 rbx=0000000000000000 rcx=fffff68000031600
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b04b43 rsp=fffff88006c122f0 rbp=0000000000000000
 r8=fffffa8006be3b30  r9=fffff88003163111 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff800`02b04b43 0000            add     byte ptr [rax],al ds:fffff680`00031d10=??
Resetting default scope

fffff800`02b04b43 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff80002b52789 to fffff80002ad3600

fffff880`06c11ff8 fffff800`02b52789 : 00000000`00000050 fffff67f`9a02af99 00000000`00000000 fffff880`06c12160 : nt!KeBugCheckEx
fffff880`06c12000 fffff800`02ad16ee : 00000000`00000000 fffffa80`06be3b30 00000000`00256000 fffffa80`05d1e000 : nt! ?? ::FNODOBFM::`string'+0x40e4b
fffff880`06c12160 fffff800`02b04b43 : 00000000`000030c1 00000000`00000200 00000000`63416d4d 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`06c122f0 fffff800`02b04251 : 00000000`00000011 fffff680`00031d10 f7d00000`5c99cc66 f7d00000`5c99c867 : nt!MiDeletePteRun+0x53
fffff880`06c124a0 fffff800`02b06cc9 : 00000000`00000000 00000000`063a2fff 00000000`00000000 00000001`00000001 : nt!MiDeleteVirtualAddresses+0x408
fffff880`06c12660 fffff800`02ded170 : fffffa80`06eb74a0 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`06c12780 fffff800`02ded57b : fffffa80`00000000 00000000`062c0000 fffffa80`00000001 00000000`7efdf100 : nt!MiUnmapViewOfSection+0x1b0
fffff880`06c12840 fffff800`02ad2853 : 00000000`00ffffff fffff960`0015a5f5 fffffa80`06be3b30 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
fffff880`06c12890 fffff800`02acedf0 : fffff960`001950ca 00000000`00000001 fffff900`c00d4280 fffff900`c25d0cd0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06c12a28 fffff960`001950ca : 00000000`00000001 fffff900`c00d4280 fffff900`c25d0cd0 00000000`00000000 : nt!KiServiceLinkage
fffff880`06c12a30 fffff960`0019544c : 00000000`00000000 fffff880`00000000 fffff900`c25d0cd0 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x3a2
fffff880`06c12b80 fffff960`0015661d : 00000000`05051162 fffff900`c25d0cd0 00000000`00001162 fffff960`0014721c : win32k!bDeleteSurface+0x34
fffff880`06c12bb0 fffff800`02ad2853 : fffffa80`04fbda90 fffff900`c00d4280 00000000`03df7ea8 00000000`001fef18 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`06c12be0 00000000`73402dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ae778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73402dd9


fffff960`001950ca e9d6010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`001952a5)


SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3a2

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware


MODULE_NAME: hardware



Followup: MachineOwner
My System SpecsSystem Spec
28 May 2010   #37


@ carl well, only google chrome I think
@ Jonathan_King Ill try that
My System SpecsSystem Spec
28 May 2010   #38

Windows 7 Ultimate 32 bit

Quote   Quote: Originally Posted by mikios1 View Post
@ carl well, only google chrome I think
@ Jonathan_King Ill try that
Thanks for the reply. Let's see how your mem test comes out.
My System SpecsSystem Spec
06 Jun 2010   #39


sorry for not responding so long, I had lots of exams,
now back to....
I did what you said, i ran test 5 times and it said in the almost-right from left column that it counts 16 errors....what now?
I eagerly await response...
My System SpecsSystem Spec
06 Jun 2010   #40

Windows 7 Professional x64

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
My System SpecsSystem Spec

 help, please.

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 16:11.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App