1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista Windows Vista BSOD - Minidump included

Discussion in 'Legacy Windows' started by andyalien, 2009/08/25.

  1. 2009/08/25
    andyalien

    andyalien Inactive Thread Starter

    Joined:
    2009/08/25
    Messages:
    3
    Likes Received:
    0
    I just switched my motherboards from Asus P6T to EVGA A1 and sudeenly I'm getting some BSOD's no idea what's causing it.
    I ran MemTest for several hours and came up clean.

    If anyone can help, please.

    Here is debuglog txt

    Opened log file 'c:\debuglog.txt'
    1: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    1: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960006d3bee, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffffa6010cd1560, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

    FAULTING_IP:
    cdd!CddCheckCreateShadowBitmap+16
    fffff960`006d3bee 48395830 cmp qword ptr [rax+30h],rbx

    CONTEXT: fffffa6010cd1560 -- (.cxr 0xfffffa6010cd1560)
    .cxr 0xfffffa6010cd1560
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff900c0086030
    rdx=fffff900c0089668 rsi=000000000000cccc rdi=fffff900c0086030
    rip=fffff960006d3bee rsp=fffffa6010cd1dc0 rbp=fffffa6010cd1fe0
    r8=0000000000000000 r9=0000000000000000 r10=fffff960006d95e4
    r11=fffffa6010cd1f08 r12=0000000000000000 r13=fffff900c22d8018
    r14=fffff900c0089668 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    cdd!CddCheckCreateShadowBitmap+0x16:
    fffff960`006d3bee 48395830 cmp qword ptr [rax+30h],rbx ds:002b:00000000`00000030=????????????????
    .cxr
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: winvnc4.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff960006d8ea0 to fffff960006d3bee

    STACK_TEXT:
    fffffa60`10cd1dc0 fffff960`006d8ea0 : fffff900`c0086030 fffff800`020b8e74 00000000`00000000 00000000`00000001 : cdd!CddCheckCreateShadowBitmap+0x16
    fffffa60`10cd1df0 fffff960`006d9628 : fffff900`c0066960 00000000`00000000 00000000`00000000 00000000`000000dc : cdd!DrvBitBlt+0x64
    fffffa60`10cd1ea0 fffff960`000a7b33 : 00000000`00000000 fffffa60`00000001 00000000`00000000 fffff900`c2c00000 : cdd!DrvCopyBits+0x44
    fffffa60`10cd1f10 fffff960`0020bb6b : fffff900`c0066960 00000000`00000000 fffff900`cb661d68 fffffa60`00000020 : win32k!WatchdogDrvCopyBits+0x83
    fffffa60`10cd1f80 fffff960`0028279f : 0000048a`00000000 00000000`00000000 fffff900`c0089668 fffff900`c20f8890 : win32k!OffCopyBits+0xc7
    fffffa60`10cd1fe0 fffff960`00282a79 : fffff900`c22d8018 fffff900`c01b6288 00000000`00000000 0000048a`00000000 : win32k!bBitBltFromScreen+0x36b
    fffffa60`10cd21e0 fffff960`0028319c : fffff900`c20f8890 fffff900`c01b6288 00000000`00000000 00000000`00000000 : win32k!MulBitBlt+0x129
    fffffa60`10cd2430 fffff960`0020bb6b : 00000000`00000000 00000000`00000000 fffff900`00000000 00000000`00002000 : win32k!MulCopyBits+0x44
    fffffa60`10cd24a0 fffff960`0020ce48 : 0000048a`00000000 fffff900`c20f8890 fffff900`c0085010 fffff900`c01b6270 : win32k!OffCopyBits+0xc7
    fffffa60`10cd2500 fffff960`0020e59f : fffff900`c20f8890 fffff900`cb77bfb0 00000000`00000000 fffff960`00215fcb : win32k!vSpReadFromScreen+0x20c
    fffffa60`10cd2660 fffff960`002125af : 00000000`000004b0 fffff900`c2892598 fffff900`cb77bf10 00000000`00000000 : win32k!vSpSmallUnderlayCopy+0x143
    fffffa60`10cd2730 fffff960`00212def : fffffa60`0000003c 00000000`00000026 00000000`00000000 fffff800`01e711b2 : win32k!bSpUpdatePosition+0x497
    fffffa60`10cd28a0 fffff960`00212db9 : fffff900`c2892540 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!vSpHideSprites+0x83
    fffffa60`10cd28e0 fffff960`0009cd65 : fffff900`c0085010 00000000`00000000 fffff900`c262b2a0 fffff900`c250e910 : win32k!vSpHideSprites+0x4d
    fffffa60`10cd2920 fffff960`0017fdcd : fffff900`00000000 00000000`00000000 00000000`03dafdb0 00000000`00000000 : win32k!DrvChangeDisplaySettings+0xc5a
    fffffa60`10cd2b40 fffff960`0017388d : 00000000`00000000 00000000`045629f0 00000000`03dafdb0 00000000`045629f0 : win32k!xxxUserChangeDisplaySettings+0x3bd
    fffffa60`10cd2be0 fffff800`01e65ef3 : fffffa80`08eb7bb0 fffffa60`10cd2ca0 00000000`03dafdb0 00000000`00000020 : win32k!NtUserChangeDisplaySettings+0x89
    fffffa60`10cd2c20 00000000`76dd524a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03dafd88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dd524a


    FOLLOWUP_IP:
    cdd!CddCheckCreateShadowBitmap+16
    fffff960`006d3bee 48395830 cmp qword ptr [rax+30h],rbx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: cdd!CddCheckCreateShadowBitmap+16

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: cdd

    IMAGE_NAME: cdd.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 49e040d5

    STACK_COMMAND: .cxr 0xfffffa6010cd1560 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_cdd!CddCheckCreateShadowBitmap+16

    BUCKET_ID: X64_0x3B_cdd!CddCheckCreateShadowBitmap+16

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

    rax=fffffa6010cd0cb0 rbx=fffffa6010cd2c20 rcx=000000000000003b
    rdx=00000000c0000005 rsi=fffff80001e65ef3 rdi=fffff8000200f49c
    rip=fffff80001e66450 rsp=fffffa6010cd0ba8 rbp=fffffa6010cd1b88
    r8=fffff960006d3bee r9=fffffa6010cd1560 r10=0000000000000000
    r11=0000000000000001 r12=fffffa6010ccc000 r13=fffffa6010cd3000
    r14=fffff80001e0c000 r15=fffff80001f59fc4
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282
    nt!KeBugCheckEx:
    fffff800`01e66450 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa60`10cd0bb0=000000000000003b
    Child-SP RetAddr : Args to Child : Call Site
    fffffa60`10cd0ba8 fffff800`01e661ee : 00000000`0000003b 00000000`c0000005 fffff960`006d3bee fffffa60`10cd1560 : nt!KeBugCheckEx
    fffffa60`10cd0bb0 fffff800`01e65bbc : 00000000`00000000 fffff800`01e91b6e 00000000`00000010 00000000`00010213 : nt!KiBugCheckDispatch+0x6e
    fffffa60`10cd0cf0 fffff800`01e91dcd : 00000000`00000000 fffff960`00090000 fffffa60`10cd3000 fffff800`0200f49c : nt!KiSystemServiceHandler+0x7c
    fffffa60`10cd0d30 fffff800`01e9208f : fffffa60`00000001 00000000`00000001 ff99b5d1`00000000 fffffa60`10cd2c20 : nt!RtlpExecuteHandlerForException+0xd
    fffffa60`10cd0d60 fffff800`01e9f706 : fffffa60`10cd1b88 fffffa60`10cd1560 fffffa60`00000000 fffff800`01f3ff75 : nt!RtlDispatchException+0x22f
    fffffa60`10cd1450 fffff800`01e662a9 : fffffa60`10cd1b88 00000000`00000000 fffffa60`10cd1c30 00000000`0000cccc : nt!KiDispatchException+0xc2
    fffffa60`10cd1a50 fffff800`01e650a5 : 00000000`00000000 fffff800`020d005e 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xa9
    fffffa60`10cd1c30 fffff960`006d3bee : 00000000`00000000 00000000`00000086 00000000`40000000 fffff880`0ab1f720 : nt!KiPageFault+0x1e5 (TrapFrame @ fffffa60`10cd1c30)
    fffffa60`10cd1dc0 fffff960`006d8ea0 : fffff900`c0086030 fffff800`020b8e74 00000000`00000000 00000000`00000001 : cdd!CddCheckCreateShadowBitmap+0x16
    fffffa60`10cd1df0 fffff960`006d9628 : fffff900`c0066960 00000000`00000000 00000000`00000000 00000000`000000dc : cdd!DrvBitBlt+0x64
    fffffa60`10cd1ea0 fffff960`000a7b33 : 00000000`00000000 fffffa60`00000001 00000000`00000000 fffff900`c2c00000 : cdd!DrvCopyBits+0x44
    fffffa60`10cd1f10 fffff960`0020bb6b : fffff900`c0066960 00000000`00000000 fffff900`cb661d68 fffffa60`00000020 : win32k!WatchdogDrvCopyBits+0x83
    fffffa60`10cd1f80 fffff960`0028279f : 0000048a`00000000 00000000`00000000 fffff900`c0089668 fffff900`c20f8890 : win32k!OffCopyBits+0xc7
    fffffa60`10cd1fe0 fffff960`00282a79 : fffff900`c22d8018 fffff900`c01b6288 00000000`00000000 0000048a`00000000 : win32k!bBitBltFromScreen+0x36b
    fffffa60`10cd21e0 fffff960`0028319c : fffff900`c20f8890 fffff900`c01b6288 00000000`00000000 00000000`00000000 : win32k!MulBitBlt+0x129
    fffffa60`10cd2430 fffff960`0020bb6b : 00000000`00000000 00000000`00000000 fffff900`00000000 00000000`00002000 : win32k!MulCopyBits+0x44
    fffffa60`10cd24a0 fffff960`0020ce48 : 0000048a`00000000 fffff900`c20f8890 fffff900`c0085010 fffff900`c01b6270 : win32k!OffCopyBits+0xc7
    fffffa60`10cd2500 fffff960`0020e59f : fffff900`c20f8890 fffff900`cb77bfb0 00000000`00000000 fffff960`00215fcb : win32k!vSpReadFromScreen+0x20c
    fffffa60`10cd2660 fffff960`002125af : 00000000`000004b0 fffff900`c2892598 fffff900`cb77bf10 00000000`00000000 : win32k!vSpSmallUnderlayCopy+0x143
    fffffa60`10cd2730 fffff960`00212def : fffffa60`0000003c 00000000`00000026 00000000`00000000 fffff800`01e711b2 : win32k!bSpUpdatePosition+0x497
    start end module name
    fffff800`01e0c000 fffff800`02324000 nt ntkrnlmp.exe Sat Apr 11 00:58:39 2009 (49E0237F)
    fffff800`02324000 fffff800`0236a000 hal hal.dll Sat Apr 11 03:04:56 2009 (49E04118)
    fffff960`00090000 fffff960`00341000 win32k win32k.sys Tue Apr 21 08:03:41 2009 (49EDB61D)
    fffff960`00470000 fffff960`0047a000 TSDDD TSDDD.dll unavailable (00000000)
    fffff960`006d0000 fffff960`006e1000 cdd cdd.dll Sat Apr 11 03:03:49 2009 (49E040D5)
    fffff960`00810000 fffff960`0081c000 vncmirror_fffff96000810000 vncmirror.dll Fri Mar 14 13:43:17 2008 (47DAB935)
    fffffa60`00600000 fffffa60`0060a000 kdcom kdcom.dll Sat Apr 11 03:07:57 2009 (49E041CD)
    fffffa60`0060a000 fffffa60`00645000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Apr 11 03:05:41 2009 (49E04145)
    fffffa60`00645000 fffffa60`00659000 PSHED PSHED.dll Sat Apr 11 03:08:17 2009 (49E041E1)
    fffffa60`00659000 fffffa60`006b6000 CLFS CLFS.SYS Sat Apr 11 00:54:21 2009 (49E0227D)
    fffffa60`006b6000 fffffa60`00768000 CI CI.dll Sat Apr 11 03:08:09 2009 (49E041D9)
    fffffa60`00768000 fffffa60`007af000 fltmgr fltmgr.sys Sat Apr 11 00:54:38 2009 (49E0228E)
    fffffa60`007af000 fffffa60`007c2000 intelppm intelppm.sys Sat Jan 19 00:52:45 2008 (4791902D)
    fffffa60`007c2000 fffffa60`007f3000 ctoss2k ctoss2k.sys Mon Jul 13 13:30:53 2009 (4A5B6F4D)
    fffffa60`0080a000 fffffa60`008e4000 Wdf01000 Wdf01000.sys Sat Jan 19 01:33:27 2008 (479199B7)
    fffffa60`008e4000 fffffa60`008f2000 WDFLDR WDFLDR.SYS Sat Jan 19 01:32:33 2008 (47919981)
    fffffa60`008f2000 fffffa60`00922000 pci pci.sys Sat Apr 11 01:03:33 2009 (49E024A5)
    fffffa60`00922000 fffffa60`00988000 volmgrx volmgrx.sys Sat Apr 11 01:35:14 2009 (49E02C12)
     
    andyalien,
    #1
  2. 2009/08/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Welcome to WindowsBBS :)

    We encourage all members to complete their System Specifications which help us to help you :)
    You might get a little more info running the dump data through our Dump Data Collection tool, but I doubt it. Also note that it does not run properly on x64.
    Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.

    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.

    According to this thread you may have a memory problem .....

    System_service_exception

    Is your memory compatible with the new mobo? Have you loaded the chipset drivers?

    The EVGA A1 appears to take DDR2 RAM - the P6T runs DDR3 - I don't know off hand if that is backwards compatible - but see below.....

    Checking out the memory compatability at Crucial.com for the A1 suggests DDR2.

    Is DDR3 memory backward compatible with DDR2 and DDR? According to that - NO

    So check the specs of your memory ....
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2009/08/25
    andyalien

    andyalien Inactive Thread Starter

    Joined:
    2009/08/25
    Messages:
    3
    Likes Received:
    0
    EVGA E758-A1 takes DDR3 1600/1333
    but I will try different set of memory, and see if that fixed the problem
     
    andyalien,
    #3
  5. 2009/08/26
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Problem seems to have occurred when running the RealVNC Server...

    That DLL is part of the display driver system...

    Just some thoughts.
     
    Arie,
    #4
  6. 2009/08/26
    andyalien

    andyalien Inactive Thread Starter

    Joined:
    2009/08/25
    Messages:
    3
    Likes Received:
    0
    That's what I tought.
    But now my PC crashes all the time or hangs.
    I got anotehr BSOD with DRIVER_POWER_STATE_FAILURE STOP 0x0000009F

    and when I try to restore Windows to earlier time it keeps telling me that drive C: has errors and cannot proceed.
    Maybe my HDD is failing?
     
    andyalien,
    #5
  7. 2009/08/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    PeteC,
    #6

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...