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: Various BSOD

04 Feb 2011   #1
Dogster

Windows 7 Ultimate x64
 
 
Various BSOD

Hello guys, and thx in advance. Ive been having teathing problems since i built myself a new computer, ive even brought a new motherboard and im getting more blue screens then ever. memory was replaced, tested and no errors, so im kinda out of ideas


My System SpecsSystem Spec
.
04 Feb 2011   #2
wish

Windows 7 Ultimate x64 SP1
 
 

Hi,
Update or uninstall LogMeIn/RemotelyAnywhere Kernel driver: RemotelyAnywhere - Remote Access Solutions
lmimirr.sys Tue Apr 10 15:32:45 2007
RaInfo.sys Fri Jan 04 10:57:14 2008
LMIRfsDriver.sys Mon Jul 14 09:26:56 2008

Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02858000 PsLoadedModuleList = 0xfffff800`02a95e50
Debug session time: Thu Feb  3 00:16:23.375 2011 (GMT-8)
System Uptime: 0 days 0:00:55.185
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffea818a499546, 1, fffff960007720cf, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b000e0
 ffffea818a499546 

FAULTING_IP: 
cdd!CDDMULTISURFLOCK::vInit+137
fffff960`007720cf c0744c6683      sal     byte ptr [rsp+rcx*2+66h],83h

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006a51320 -- (.trap 0xfffff88006a51320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c1d24018 rbx=0000000000000000 rcx=fffff900c1d24018
rdx=fffff88006a51770 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960007720cf rsp=fffff88006a514b0 rbp=fffff900c2699bf8
 r8=fffff88006a51a98  r9=fffff88006a51aa0 r10=fffff900c00bd8b0
r11=fffff88006a51a88 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cdd!CDDMULTISURFLOCK::vInit+0x137:
fffff960`007720cf c0744c6683      sal     byte ptr [rsp+rcx*2+66h],83h ss:0018:ffffea81`8a499546=??
Resetting default scope

MISALIGNED_IP: 
cdd!CDDMULTISURFLOCK::vInit+137
fffff960`007720cf c0744c6683      sal     byte ptr [rsp+rcx*2+66h],83h

LAST_CONTROL_TRANSFER:  from fffff80002947b19 to fffff800028c9f00

STACK_TEXT:  
fffff880`06a511b8 fffff800`02947b19 : 00000000`00000050 ffffea81`8a499546 00000000`00000001 fffff880`06a51320 : nt!KeBugCheckEx
fffff880`06a511c0 fffff800`028c7fee : 00000000`00000001 00000000`00000001 fffff900`c00bf000 00000000`00000101 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`06a51320 fffff960`007720cf : fffffa80`05e5a4f0 fffff900`c00bffa0 fffff880`06a51970 fffff960`00771f2a : nt!KiPageFault+0x16e
fffff880`06a514b0 fffff960`00778de1 : 00000000`00000000 fffff900`c00bf020 fffff880`06a51a98 fffff880`06a51d50 : cdd!CDDMULTISURFLOCK::vInit+0x137
fffff880`06a51500 fffff960`0077a12b : 00000000`00000000 fffff900`c2699bf8 fffff900`c1d24018 00000000`00000000 : cdd!BitBltBitmap+0x1c9
fffff880`06a51a90 fffff960`0077b138 : 00000000`00000000 fffff960`000a63b3 00000000`00000000 00000000`00000000 : cdd!DrvBitBlt+0x17b
fffff880`06a51cb0 fffff960`002ec07b : 00000000`00000000 00000000`00000000 fffff900`c1ced9d0 00000000`00000001 : cdd!DrvCopyBits+0x44
fffff880`06a51d20 fffff960`00231544 : 00000000`00000000 00000000`00000000 00000000`0000cccc 00000000`00000000 : win32k!OffCopyBits+0xc7
fffff880`06a51d80 fffff960`002319d8 : fffff900`c2699bf8 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SpBitBlt+0x418
fffff880`06a52170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SpCopyBits+0x44


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !cdd
    fffff96000772012 - cdd!CDDMULTISURFLOCK::vInit+7a
    [ b7:a7 ]
1 error : !cdd (fffff96000772012)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
My System SpecsSystem Spec
04 Feb 2011   #3
Dogster

Windows 7 Ultimate x64
 
 

ok thx, ive removed logmein and installed teamviewer instead i honestly thought it was my motherboard, but obviously not
My System SpecsSystem Spec
.

Reply

 Various BSOD




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