1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Blue Screens of Deaths! Please help?

Discussion in 'Windows Vista' started by LitomoSilver, Apr 18, 2008.

Thread Status:
Not open for further replies.
Advertisement
  1. LitomoSilver

    LitomoSilver Thread Starter

    Joined:
    Feb 20, 2005
    Messages:
    1,477
    So, I installed Windows Vista a couple days ago.

    It seems to have trouble now. :/ I'd like to solve this once and for all. This is an irritating problem. (It BSoD'ed in Windows XP too.)


    Could not read faulting driver name


    Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5e )

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

    0: 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: abfeb9f8, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: 906eafd8, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name



    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
    Unable to read MiSystemVaType memory at 81d117e0
    abfeb9f8

    FAULTING_IP:
    win32k!vSrcCopyS32D32Identity+5e
    906eafd8 ff4d08 dec dword ptr [ebp+8]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: voodoo.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: abbeb96c -- <link cmd=".trap 0xffffffffabbeb96c">(.trap 0xffffffffabbeb96c)</exec>
    ErrCode = 00000002
    eax=0cc91ee8 ebx=0cc91ee8 ecx=00000000 edx=00000000 esi=abbebb70 edi=fa1b8a98
    eip=906eafd8 esp=abbeb9e0 ebp=abfeb9f0 iopl=0 nv up ei ng nz ac po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
    win32k!vSrcCopyS32D32Identity+0x5e:
    906eafd8 ff4d08 dec dword ptr [ebp+8] ss:0010:abfeb9f8=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

    STACK_TEXT:
    abbeb954 81c8fbb4 00000001 abfeb9f8 00000000 nt!MmAccessFault+0x106
    abbeb954 906eafd8 00000001 abfeb9f8 00000000 nt!KiTrap0E+0xdc
    abbeb9f0 906e857f 0000008e ab2ec4d7 fdd8d7d8 win32k!vSrcCopyS32D32Identity+0x5e
    abbebc30 906ea266 fea0be70 fd7dee70 00000000 win32k!EngCopyBits+0x5b3
    abbebd10 81c8caaa fea0be60 ffa7c8c0 fe2604e0 win32k!NtGdiBitBlt+0x59c
    abbebd10 77610f34 fea0be60 ffa7c8c0 fe2604e0 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f3f8 00000000 00000000 00000000 00000000 0x77610f34


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!vSrcCopyS32D32Identity+5e
    906eafd8 ff4d08 dec dword ptr [ebp+8]

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+5e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: <link cmd="lmvm win32k">win32k</exec>

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

    FAILURE_BUCKET_ID: 0x50_W_win32k!vSrcCopyS32D32Identity+5e

    BUCKET_ID: 0x50_W_win32k!vSrcCopyS32D32Identity+5e

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


    Loading Dump File [C:\Windows\Minidump\Mini041808-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\websymbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16584.x86fre.vista_gdr.071023-1545
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Fri Apr 18 11:13:24.877 2008 (GMT-7)
    System Uptime: 0 days 17:36:03.599
    Loading Kernel Symbols
    ...........................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {abfeb9f8, 1, 906eafd8, 0}


    Could not read faulting driver name


    Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5e )

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

    0: 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: abfeb9f8, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: 906eafd8, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name



    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
    Unable to read MiSystemVaType memory at 81d117e0
    abfeb9f8

    FAULTING_IP:
    win32k!vSrcCopyS32D32Identity+5e
    906eafd8 ff4d08 dec dword ptr [ebp+8]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: voodoo.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: abbeb96c -- (.trap 0xffffffffabbeb96c)
    ErrCode = 00000002
    eax=0cc91ee8 ebx=0cc91ee8 ecx=00000000 edx=00000000 esi=abbebb70 edi=fa1b8a98
    eip=906eafd8 esp=abbeb9e0 ebp=abfeb9f0 iopl=0 nv up ei ng nz ac po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
    win32k!vSrcCopyS32D32Identity+0x5e:
    906eafd8 ff4d08 dec dword ptr [ebp+8] ss:0010:abfeb9f8=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

    STACK_TEXT:
    abbeb954 81c8fbb4 00000001 abfeb9f8 00000000 nt!MmAccessFault+0x106
    abbeb954 906eafd8 00000001 abfeb9f8 00000000 nt!KiTrap0E+0xdc
    abbeb9f0 906e857f 0000008e ab2ec4d7 fdd8d7d8 win32k!vSrcCopyS32D32Identity+0x5e
    abbebc30 906ea266 fea0be70 fd7dee70 00000000 win32k!EngCopyBits+0x5b3
    abbebd10 81c8caaa fea0be60 ffa7c8c0 fe2604e0 win32k!NtGdiBitBlt+0x59c
    abbebd10 77610f34 fea0be60 ffa7c8c0 fe2604e0 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f3f8 00000000 00000000 00000000 00000000 0x77610f34


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!vSrcCopyS32D32Identity+5e
    906eafd8 ff4d08 dec dword ptr [ebp+8]

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+5e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

    FAILURE_BUCKET_ID: 0x50_W_win32k!vSrcCopyS32D32Identity+5e

    BUCKET_ID: 0x50_W_win32k!vSrcCopyS32D32Identity+5e

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

    That's all I know, but I'll include the minidump for your convenience.

    Wait, I know this program... Voodoo.exe can be downloaded from Voodoo Chat But... why did this happen, I've no idea.

    There was a second BSoD, but I got nothing from it. It was just a BSoD but no error message was given.
     

    Attached Files:

  2. LitomoSilver

    LitomoSilver Thread Starter

    Joined:
    Feb 20, 2005
    Messages:
    1,477
    Ouch. New BSoD. Same process...


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


    Loading Dump File [C:\Windows\Minidump\Mini041808-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\websymbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16584.x86fre.vista_gdr.071023-1545
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Fri Apr 18 12:25:58.118 2008 (GMT-7)
    System Uptime: 0 days 0:44:40.957
    Loading Kernel Symbols
    .............................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck BE, {9fff39f8, 60, 9fbf396c, e}



    Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5e )

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

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

    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
    An attempt was made to write to readonly memory. The guilty driver is on the
    stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: 9fff39f8, Virtual address for the attempted write.
    Arg2: 00000060, PTE contents.
    Arg3: 9fbf396c, (reserved)
    Arg4: 0000000e, (reserved)

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




    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xBE

    PROCESS_NAME: taskmgr.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: 9fbf396c -- (.trap 0xffffffff9fbf396c)
    ErrCode = 00000002
    eax=02d1ca44 ebx=02d1ca44 ecx=00000000 edx=00000000 esi=9fbf3b70 edi=fd64c9c8
    eip=90aeafd8 esp=9fbf39e0 ebp=9fff39f0 iopl=0 nv up ei ng nz ac po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
    win32k!vSrcCopyS32D32Identity+0x5e:
    90aeafd8 ff4d08 dec dword ptr [ebp+8] ss:0010:9fff39f8=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

    STACK_TEXT:
    9fbf3954 81c8fbb4 00000001 9fff39f8 00000000 nt!MmAccessFault+0x106
    9fbf3954 90aeafd8 00000001 9fff39f8 00000000 nt!KiTrap0E+0xdc
    9fbf39f0 90ae857f 000000fe 9f2f84a3 fe396008 win32k!vSrcCopyS32D32Identity+0x5e
    9fbf3c30 90aea266 fe429330 fec7f138 00000000 win32k!EngCopyBits+0x5b3
    9fbf3d10 81c8caaa fe429320 ffa7c8c0 ffa02890 win32k!NtGdiBitBlt+0x59c
    9fbf3d10 773f0f34 fe429320 ffa7c8c0 ffa02890 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    000bec1c 00000000 00000000 00000000 00000000 0x773f0f34


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!vSrcCopyS32D32Identity+5e
    90aeafd8 ff4d08 dec dword ptr [ebp+8]

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+5e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

    FAILURE_BUCKET_ID: 0xBE_win32k!vSrcCopyS32D32Identity+5e

    BUCKET_ID: 0xBE_win32k!vSrcCopyS32D32Identity+5e

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

    Again, including the minidump.

    But during the BSoD, it said that something was attempting to write to read only memory or something similar.
     

    Attached Files:

  3. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    Win32k.sys faults are very non specific and require trial and error troubleshooting to isolate.

    Most often they are caused by firewall, antivirus or scanner utilities. Sometimes by hardware when the system is overheating.

    How often are they occuring?

    I would uninstall Comodo ( I think you have that), switch to the Windows firewall, and otherwise "clean boot" the system during a period of testing >> http://support.microsoft.com/kb/929135

    You may get a clue as to the culprit by opening the Control Panel > Performance Information and Tools > Advanced > Reliability Monitor and scroll back in time to see when these started occuring and what installs preceeded them.
     
  4. LitomoSilver

    LitomoSilver Thread Starter

    Joined:
    Feb 20, 2005
    Messages:
    1,477
    Yeah, I do have Comodo Firewall.

    Will do then.

    I don't see anything that even mentions what caused the failure in the Reliability Monitor.

    Other than a Raxco Perfect Disk install that I screwed up but was able to fix... and...

    VLC Media Player failing to install. Again, user mistake as well. Fixed as well.

    Explorer.exe froze and failed. A reboot fixed that.

    But nothing definitive as to what caused the BSoDs.

    Mainly applications that failed to install but were later corrected and installed successfully.

    Anywhere else I should look?
     
  5. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    The graphics driver is suspect in these as well.

    This part of the error I believe is a graphics driver operation and it seems pretty consistent:

    ( win32k!vSrcCopyS32D32Identity+5e

    and this:

    win32k!NtGdiBitBlt+0x59c

    The "gdi" in there is a conventiion for graphics device interface
     
  6. LitomoSilver

    LitomoSilver Thread Starter

    Joined:
    Feb 20, 2005
    Messages:
    1,477
    Another BSoD.

    Same process error. Win32k.sys

    What in hell is goin' on here? >_>

    Since I can't get the correct symbols, I'd like someone to check it out for me, and if possible, show me how I can get the correct symbols. -_-

    Edit: I'm thinking of purchasing another nVIDIA card and see what happens there.

    >_> This is really annoying.
     

    Attached Files:

  7. LitomoSilver

    LitomoSilver Thread Starter

    Joined:
    Feb 20, 2005
    Messages:
    1,477
    AHHHHH

    My Vista OS is borked!

    I cannot even get into it!

    Right now I'm running DSL off the CD.

    It gets to the logon screen... but before I could even log in, it goes, Please wait, as if the computer had just downloaded and installed updates. Maybe it has, but I have absolutely NO idea what happened.

    Then it blacks out and does not return.

    Also, I ran Memtest and found that one of my 1GB sticks of RAM was bad.

    So, I'm going to have to do something about that.

    Any suggestions, please?!

    And, could the bad RAM stick caused the Win32k.sys errors?

    Edit: Well, crap. I tried System Restore from the DVD. No go.

    All system checks out OK.

    I have absolutely NO idea why it's refusing to let me log in.

    I may very well have to do a system wipe and reinstall. -_-
     
  8. Rollin' Rog

    Rollin' Rog

    Joined:
    Dec 9, 2000
    Messages:
    45,855
    "And, could the bad RAM stick caused the Win32k.sys errors?"

    Yes, test each module of ram separately and remove the bad one. Usually you can get an idea of what module it is in by the memory location of the error from Memtest.

    Then see if you can boot in Safe Mode at least -- and if necessary, try a System Restore from there.

    I tried getting the correct Symbols for Vista SP1 too -- but kept getting that error.

    So I just use the online symbol path:

    SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
     
  9. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/704975

  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.
    Dismiss Notice