Crashing Mystery; Getting Desperate

Discussion in 'Windows 64bit' started by Rafael Rivera [Extended64.com], Jun 14, 2005.

  1. Ok usually I can fix problems on my own but this one is driving me up
    the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    Already tried the debugger approach but the dumps either point to
    unknown memory space or try to assign blame to win32k.sys. I have
    attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    every BSOD is something different - What's in the text file is likely
    false... I'm getting desperate here... Assume no floppy is present.

    * Already tried...

    memtest86 (passed)
    71.84 Forceware drivers
    70.80 Forceware drivers
    Increasing/Decreasing core voltage levels
    Repasting of core and GPU
    Format

    * Relevant Hardware Info:

    AMD Athlon(tm) 64 Processor 4000+
    (Family F, Ext. Family F, Model 7, Ext. Model 7
    Stepping A, Revision SH7-CG)
    Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    (dual channel kit, installed correctly)
    Asus AV8-SLI (although SLI not being used)
    NVIDIA Geforce 6800GT
    500W Ultra X-Connect PSU (eATX compatible)
    2 PATA HDDs, 2 PATA Optical drives

    * Relevant Software Info:

    NVIDIA Forceware drivers v70.80
    NVIDIA nForce4 platform drivers NOT installed
    (except NIC driver)
    AMD Cool(n)Quiet disabled

    * Other Info:

    Processor idle temperature: ~ 44C
    GPU idle temperature before repaste: ~ 68C
    GPU idle temperature after repaste: ~ 61C
    +12V: +11.9V
    +5V: +4.84V
    Core: +1.58V (increased for diag.)
    I/O: +3.30V

    Thanks in advance for any help provided!

    --
    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments:
    Arg1: 00000000c0000005
    Arg2: fffff97fff0ba49e
    Arg3: fffffadfe02531a0
    Arg4: 0000000000000000

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


    CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    r14=000000000012edf0 r15=0000000078b83980
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    fffff97f`ff0ba49e 488906 mov [rsi],rax ds:002b:0041=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e

    STACK_TEXT:
    fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041 fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 : win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340 00000000`00000001 00000000`00009001 00000000`00000000 : win32k!GreSetRectRgn+0x36
    fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327 00000000`0104003f 00000000`0104003f 00000000`0000000b : win32k!InternalInvalidate2+0x219
    fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340 00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 : win32k!xxxInternalInvalidate+0x451
    fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d 00000000`00010184 00000000`f6040ba9 00000000`00000000 : win32k!xxxRedrawWindow+0x1b8
    fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000 00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 : win32k!NtUserInvalidateRgn+0x87
    fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    00000000`0012ede8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9


    FOLLOWUP_IP:
    win32k!RGNOBJAPI::RGNOBJAPI+2e
    fffff97f`ff0ba49e 488906 mov [rsi],rax

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 42436088

    STACK_COMMAND: .cxr fffffadfe02531a0 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e

    BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e

    Followup: MachineOwner
    ---------
     
    Rafael Rivera [Extended64.com], Jun 14, 2005
    #1
    1. Advertising

  2. STOP 3B's are very rare actually. Do you have a kernel memory dump from
    this? Or maybe a mini-dump you can send to me?
     
    Joseph Conway [MSFT], Jun 14, 2005
    #2
    1. Advertising

  3. Ouch, no replies yet. Anyone?

    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    Rafael Rivera [Extended64.com] wrote:
    > Ok usually I can fix problems on my own but this one is driving me up
    > the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    > Already tried the debugger approach but the dumps either point to
    > unknown memory space or try to assign blame to win32k.sys. I have
    > attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    > every BSOD is something different - What's in the text file is likely
    > false... I'm getting desperate here... Assume no floppy is present.
    >
    > * Already tried...
    >
    > memtest86 (passed)
    > 71.84 Forceware drivers
    > 70.80 Forceware drivers
    > Increasing/Decreasing core voltage levels
    > Repasting of core and GPU
    > Format
    >
    > * Relevant Hardware Info:
    >
    > AMD Athlon(tm) 64 Processor 4000+
    > (Family F, Ext. Family F, Model 7, Ext. Model 7
    > Stepping A, Revision SH7-CG)
    > Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    > (dual channel kit, installed correctly)
    > Asus AV8-SLI (although SLI not being used)
    > NVIDIA Geforce 6800GT
    > 500W Ultra X-Connect PSU (eATX compatible)
    > 2 PATA HDDs, 2 PATA Optical drives
    >
    > * Relevant Software Info:
    >
    > NVIDIA Forceware drivers v70.80
    > NVIDIA nForce4 platform drivers NOT installed
    > (except NIC driver)
    > AMD Cool(n)Quiet disabled
    >
    > * Other Info:
    >
    > Processor idle temperature: ~ 44C
    > GPU idle temperature before repaste: ~ 68C
    > GPU idle temperature after repaste: ~ 61C
    > +12V: +11.9V
    > +5V: +4.84V
    > Core: +1.58V (increased for diag.)
    > I/O: +3.30V
    >
    > Thanks in advance for any help provided!
    >
     
    Rafael Rivera [Extended64.com], Jun 14, 2005
    #3
  4. -snip-
    > NVIDIA nForce4 platform drivers NOT installed
    > (except NIC driver)


    That is a problem in itself. You MUST install the motherboard drivers, all
    of them except for the sound drivers (unless you are using onboard sound)
    http://downloads.guru3d.com/download.php?det=1068



    Wayne
     
    Wayne Wastier, Jun 14, 2005
    #4
  5. Rafael Rivera [Extended64.com]

    John Barnes Guest

    I think your system is getting even for your comments about my task bar.
    FWIW I have a number of settings that randomly disappear, not just the
    height of the task bar.
    It seems totally random. 1-5 times the settings stay, 1-2 times the
    settings are gone. Stability isn't an x64 feature. Maybe SP2? :)


    "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    message news:...
    > Ok usually I can fix problems on my own but this one is driving me up
    > the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    > Already tried the debugger approach but the dumps either point to
    > unknown memory space or try to assign blame to win32k.sys. I have
    > attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    > every BSOD is something different - What's in the text file is likely
    > false... I'm getting desperate here... Assume no floppy is present.
    >
    > * Already tried...
    >
    > memtest86 (passed)
    > 71.84 Forceware drivers
    > 70.80 Forceware drivers
    > Increasing/Decreasing core voltage levels
    > Repasting of core and GPU
    > Format
    >
    > * Relevant Hardware Info:
    >
    > AMD Athlon(tm) 64 Processor 4000+
    > (Family F, Ext. Family F, Model 7, Ext. Model 7
    > Stepping A, Revision SH7-CG)
    > Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    > (dual channel kit, installed correctly)
    > Asus AV8-SLI (although SLI not being used)
    > NVIDIA Geforce 6800GT
    > 500W Ultra X-Connect PSU (eATX compatible)
    > 2 PATA HDDs, 2 PATA Optical drives
    >
    > * Relevant Software Info:
    >
    > NVIDIA Forceware drivers v70.80
    > NVIDIA nForce4 platform drivers NOT installed
    > (except NIC driver)
    > AMD Cool(n)Quiet disabled
    >
    > * Other Info:
    >
    > Processor idle temperature: ~ 44C
    > GPU idle temperature before repaste: ~ 68C
    > GPU idle temperature after repaste: ~ 61C
    > +12V: +11.9V
    > +5V: +4.84V
    > Core: +1.58V (increased for diag.)
    > I/O: +3.30V
    >
    > Thanks in advance for any help provided!
    >
    > --
    > Rafael Rivera
    > Extended64 | http://www.extended64.com
    > Blog | http://www.extended64.com/blogs/Rafael
    >



    --------------------------------------------------------------------------------


    > *******************************************************************************
    > *
    > *
    > * Bugcheck Analysis
    > *
    > *
    > *
    > *******************************************************************************
    >
    > SYSTEM_SERVICE_EXCEPTION (3b)
    > Arguments:
    > Arg1: 00000000c0000005
    > Arg2: fffff97fff0ba49e
    > Arg3: fffffadfe02531a0
    > Arg4: 0000000000000000
    >
    > Debugging Details:
    > ------------------
    >
    >
    > CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    > rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    > rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    > rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    > r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    > r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    > r14=000000000012edf0 r15=0000000078b83980
    > iopl=0 nv up ei ng nz na pe nc
    > cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b
    > efl=00010282
    > win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    > fffff97f`ff0ba49e 488906 mov [rsi],rax
    > ds:002b:0041=????????????????
    > Resetting default scope
    >
    > CUSTOMER_CRASH_COUNT: 3
    >
    > DEFAULT_BUCKET_ID: DRIVER_FAULT
    >
    > BUGCHECK_STR: 0x3B
    >
    > CURRENT_IRQL: 0
    >
    > LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >
    > STACK_TEXT:
    > fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041 fffff97f`ff085c8d
    > fffff97f`f78005e8 fffff97f`f7bd9340 : win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    > fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340 00000000`00000001
    > 00000000`00009001 00000000`00000000 : win32k!GreSetRectRgn+0x36
    > fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327 00000000`0104003f
    > 00000000`0104003f 00000000`0000000b : win32k!InternalInvalidate2+0x219
    > fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340 00000000`0104003f
    > 00000000`00000001 fffff97f`f7bd9340 : win32k!xxxInternalInvalidate+0x451
    > fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d 00000000`00010184
    > 00000000`f6040ba9 00000000`00000000 : win32k!xxxRedrawWindow+0x1b8
    > fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000 00000000`00000000
    > fffff97f`ff049550 00000000`7d8192e1 : win32k!NtUserInvalidateRgn+0x87
    > fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000 00000000`00000000
    > 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    > 00000000`0012ede8 00000000`00000000 : 00000000`00000000 00000000`00000000
    > 00000000`00000000 00000000`00000000 : 0x78b842d9
    >
    >
    > FOLLOWUP_IP:
    > win32k!RGNOBJAPI::RGNOBJAPI+2e
    > fffff97f`ff0ba49e 488906 mov [rsi],rax
    >
    > SYMBOL_STACK_INDEX: 0
    >
    > FOLLOWUP_NAME: MachineOwner
    >
    > SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > MODULE_NAME: win32k
    >
    > IMAGE_NAME: win32k.sys
    >
    > DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >
    > STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >
    > FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > Followup: MachineOwner
    > ---------
    >
     
    John Barnes, Jun 14, 2005
    #5
  6. Hmmmm, pretty sure I replied to you :)
     
    Joseph Conway [MSFT], Jun 14, 2005
    #6
  7. I doubt I "must" install them as Windows includes basic-enough support
    for my components. I did have them fully installed/configured in my last
    state before attempting a format to fix this problem so whether or not
    they're installed is irrelevant.

    Another note to throw out there - When left completely idle, crashing
    does not occur. Thanks for the replies so far!


    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    Wayne Wastier wrote:
    > -snip-
    >
    >>NVIDIA nForce4 platform drivers NOT installed
    >>(except NIC driver)

    >
    >
    > That is a problem in itself. You MUST install the motherboard drivers, all
    > of them except for the sound drivers (unless you are using onboard sound)
    > http://downloads.guru3d.com/download.php?det=1068
    >
    >
    >
    > Wayne
    >
    >
     
    Rafael Rivera [Extended64.com], Jun 15, 2005
    #7
  8. I must forewarn you these BSODs are very unlikely real ( something
    appears to be triggering these random BSODs ) ...

    I can send you the kernel memory dump (and the useless mini dump) - Can
    you mail me (remove obvious anti-spam tags) with a real email address
    that'll receive a 21.3MB RARed memory dump (expands to over 100MB)? Or
    maybe I'll just respond with a YouSendIt link...

    .... or I can relay information based on commands ...

    .... or I can allow some kind of remote interaction ...

    Let me know what you want to do.

    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    Joseph Conway [MSFT] wrote:
    > STOP 3B's are very rare actually. Do you have a kernel memory dump from
    > this? Or maybe a mini-dump you can send to me?
    >
     
    Rafael Rivera [Extended64.com], Jun 15, 2005
    #8
  9. Doubt all you want. I am telling you, you need the nForce drivers.



    "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    message news:...
    >I doubt I "must" install them as Windows includes basic-enough support for
    >my components. I did have them fully installed/configured in my last state
    >before attempting a format to fix this problem so whether or not they're
    >installed is irrelevant.
    >
    > Another note to throw out there - When left completely idle, crashing does
    > not occur. Thanks for the replies so far!
    >
    >
    > Rafael Rivera
    > Extended64 | http://www.extended64.com
    > Blog | http://www.extended64.com/blogs/Rafael
    >
    > Wayne Wastier wrote:
    >> -snip-
    >>
    >>>NVIDIA nForce4 platform drivers NOT installed
    >>>(except NIC driver)

    >>
    >>
    >> That is a problem in itself. You MUST install the motherboard drivers,
    >> all of them except for the sound drivers (unless you are using onboard
    >> sound)
    >> http://downloads.guru3d.com/download.php?det=1068
    >>
    >>
    >>
    >> Wayne
     
    Wayne Wastier, Jun 15, 2005
    #9
  10. Ok, note taken. This doesn't assist in resolving my current problem though.

    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    Wayne Wastier wrote:
    > Doubt all you want. I am telling you, you need the nForce drivers.
    >
    >
    >
    > "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    > message news:...
    >
    >>I doubt I "must" install them as Windows includes basic-enough support for
    >>my components. I did have them fully installed/configured in my last state
    >>before attempting a format to fix this problem so whether or not they're
    >>installed is irrelevant.
    >>
    >>Another note to throw out there - When left completely idle, crashing does
    >>not occur. Thanks for the replies so far!
    >>
    >>
    >>Rafael Rivera
    >>Extended64 | http://www.extended64.com
    >>Blog | http://www.extended64.com/blogs/Rafael
    >>
    >>Wayne Wastier wrote:
    >>
    >>>-snip-
    >>>
    >>>
    >>>>NVIDIA nForce4 platform drivers NOT installed
    >>>>(except NIC driver)
    >>>
    >>>
    >>>That is a problem in itself. You MUST install the motherboard drivers,
    >>>all of them except for the sound drivers (unless you are using onboard
    >>>sound)
    >>>http://downloads.guru3d.com/download.php?det=1068
    >>>
    >>>
    >>>
    >>>Wayne

    >
    >
    >
     
    Rafael Rivera [Extended64.com], Jun 15, 2005
    #10
  11. Rafael Rivera [Extended64.com]

    MHPNW STAFF Guest

    Just a Note ...
    Double check your bio's settings on your memory .... most boards you have
    better luck by manually entering in the timeing settings .These are the
    settings you should be using for your mem: w/ AMD processor ....

    AMD settings 2.5 -3-3-6 Intel Settings Are 2.0 3-3-6


    Hope that it helps


    Dennis


    "John Barnes" <> wrote in message
    news:%...
    >I think your system is getting even for your comments about my task bar.
    >FWIW I have a number of settings that randomly disappear, not just the
    >height of the task bar.
    > It seems totally random. 1-5 times the settings stay, 1-2 times the
    > settings are gone. Stability isn't an x64 feature. Maybe SP2? :)
    >
    >
    > "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    > message news:...
    >> Ok usually I can fix problems on my own but this one is driving me up
    >> the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    >> Already tried the debugger approach but the dumps either point to
    >> unknown memory space or try to assign blame to win32k.sys. I have
    >> attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    >> every BSOD is something different - What's in the text file is likely
    >> false... I'm getting desperate here... Assume no floppy is present.
    >>
    >> * Already tried...
    >>
    >> memtest86 (passed)
    >> 71.84 Forceware drivers
    >> 70.80 Forceware drivers
    >> Increasing/Decreasing core voltage levels
    >> Repasting of core and GPU
    >> Format
    >>
    >> * Relevant Hardware Info:
    >>
    >> AMD Athlon(tm) 64 Processor 4000+
    >> (Family F, Ext. Family F, Model 7, Ext. Model 7
    >> Stepping A, Revision SH7-CG)
    >> Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >> (dual channel kit, installed correctly)
    >> Asus AV8-SLI (although SLI not being used)
    >> NVIDIA Geforce 6800GT
    >> 500W Ultra X-Connect PSU (eATX compatible)
    >> 2 PATA HDDs, 2 PATA Optical drives
    >>
    >> * Relevant Software Info:
    >>
    >> NVIDIA Forceware drivers v70.80
    >> NVIDIA nForce4 platform drivers NOT installed
    >> (except NIC driver)
    >> AMD Cool(n)Quiet disabled
    >>
    >> * Other Info:
    >>
    >> Processor idle temperature: ~ 44C
    >> GPU idle temperature before repaste: ~ 68C
    >> GPU idle temperature after repaste: ~ 61C
    >> +12V: +11.9V
    >> +5V: +4.84V
    >> Core: +1.58V (increased for diag.)
    >> I/O: +3.30V
    >>
    >> Thanks in advance for any help provided!
    >>
    >> --
    >> Rafael Rivera
    >> Extended64 | http://www.extended64.com
    >> Blog | http://www.extended64.com/blogs/Rafael
    >>

    >
    >
    > --------------------------------------------------------------------------------
    >
    >
    >> *******************************************************************************
    >> * *
    >> * Bugcheck Analysis *
    >> * *
    >> *******************************************************************************
    >>
    >> SYSTEM_SERVICE_EXCEPTION (3b)
    >> Arguments:
    >> Arg1: 00000000c0000005
    >> Arg2: fffff97fff0ba49e
    >> Arg3: fffffadfe02531a0
    >> Arg4: 0000000000000000
    >>
    >> Debugging Details:
    >> ------------------
    >>
    >>
    >> CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >> rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >> rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >> rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >> r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >> r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >> r14=000000000012edf0 r15=0000000078b83980
    >> iopl=0 nv up ei ng nz na pe nc
    >> cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    >> win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >> ds:002b:0041=????????????????
    >> Resetting default scope
    >>
    >> CUSTOMER_CRASH_COUNT: 3
    >>
    >> DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>
    >> BUGCHECK_STR: 0x3B
    >>
    >> CURRENT_IRQL: 0
    >>
    >> LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>
    >> STACK_TEXT:
    >> fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041 fffff97f`ff085c8d
    >> fffff97f`f78005e8 fffff97f`f7bd9340 : win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >> fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340 00000000`00000001
    >> 00000000`00009001 00000000`00000000 : win32k!GreSetRectRgn+0x36
    >> fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327 00000000`0104003f
    >> 00000000`0104003f 00000000`0000000b : win32k!InternalInvalidate2+0x219
    >> fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340 00000000`0104003f
    >> 00000000`00000001 fffff97f`f7bd9340 : win32k!xxxInternalInvalidate+0x451
    >> fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d 00000000`00010184
    >> 00000000`f6040ba9 00000000`00000000 : win32k!xxxRedrawWindow+0x1b8
    >> fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000 00000000`00000000
    >> fffff97f`ff049550 00000000`7d8192e1 : win32k!NtUserInvalidateRgn+0x87
    >> fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000 00000000`00000000
    >> 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    >> 00000000`0012ede8 00000000`00000000 : 00000000`00000000 00000000`00000000
    >> 00000000`00000000 00000000`00000000 : 0x78b842d9
    >>
    >>
    >> FOLLOWUP_IP:
    >> win32k!RGNOBJAPI::RGNOBJAPI+2e
    >> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>
    >> SYMBOL_STACK_INDEX: 0
    >>
    >> FOLLOWUP_NAME: MachineOwner
    >>
    >> SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>
    >> MODULE_NAME: win32k
    >>
    >> IMAGE_NAME: win32k.sys
    >>
    >> DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>
    >> STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>
    >> FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>
    >> BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>
    >> Followup: MachineOwner
    >> ---------
    >>

    >
    >
     
    MHPNW STAFF, Jun 15, 2005
    #11
  12. Rafael Rivera [Extended64.com]

    John Barnes Guest

    My memory settings are per the memory mfg. 2-2-2-5. I have also run the
    Microsoft memory checker with no errors. However we are not talking about
    physical memory. We are talking about the system retaining settings during
    logoff, like task bar settings, in my case the height. Location of icons on
    the desktop, Usually just any newer ones. You know the 'Saving settings'
    part of logoff. Thanks anyway.


    "MHPNW STAFF" <> wrote in message
    news:...
    > Just a Note ...
    > Double check your bio's settings on your memory .... most boards you have
    > better luck by manually entering in the timeing settings .These are the
    > settings you should be using for your mem: w/ AMD processor ....
    >
    > AMD settings 2.5 -3-3-6 Intel Settings Are 2.0 3-3-6
    >
    >
    > Hope that it helps
    >
    >
    > Dennis
    >
    >
    > "John Barnes" <> wrote in message
    > news:%...
    >>I think your system is getting even for your comments about my task bar.
    >>FWIW I have a number of settings that randomly disappear, not just the
    >>height of the task bar.
    >> It seems totally random. 1-5 times the settings stay, 1-2 times the
    >> settings are gone. Stability isn't an x64 feature. Maybe SP2? :)
    >>
    >>
    >> "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    >> message news:...
    >>> Ok usually I can fix problems on my own but this one is driving me up
    >>> the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    >>> Already tried the debugger approach but the dumps either point to
    >>> unknown memory space or try to assign blame to win32k.sys. I have
    >>> attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    >>> every BSOD is something different - What's in the text file is likely
    >>> false... I'm getting desperate here... Assume no floppy is present.
    >>>
    >>> * Already tried...
    >>>
    >>> memtest86 (passed)
    >>> 71.84 Forceware drivers
    >>> 70.80 Forceware drivers
    >>> Increasing/Decreasing core voltage levels
    >>> Repasting of core and GPU
    >>> Format
    >>>
    >>> * Relevant Hardware Info:
    >>>
    >>> AMD Athlon(tm) 64 Processor 4000+
    >>> (Family F, Ext. Family F, Model 7, Ext. Model 7
    >>> Stepping A, Revision SH7-CG)
    >>> Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >>> (dual channel kit, installed correctly)
    >>> Asus AV8-SLI (although SLI not being used)
    >>> NVIDIA Geforce 6800GT
    >>> 500W Ultra X-Connect PSU (eATX compatible)
    >>> 2 PATA HDDs, 2 PATA Optical drives
    >>>
    >>> * Relevant Software Info:
    >>>
    >>> NVIDIA Forceware drivers v70.80
    >>> NVIDIA nForce4 platform drivers NOT installed
    >>> (except NIC driver)
    >>> AMD Cool(n)Quiet disabled
    >>>
    >>> * Other Info:
    >>>
    >>> Processor idle temperature: ~ 44C
    >>> GPU idle temperature before repaste: ~ 68C
    >>> GPU idle temperature after repaste: ~ 61C
    >>> +12V: +11.9V
    >>> +5V: +4.84V
    >>> Core: +1.58V (increased for diag.)
    >>> I/O: +3.30V
    >>>
    >>> Thanks in advance for any help provided!
    >>>
    >>> --
    >>> Rafael Rivera
    >>> Extended64 | http://www.extended64.com
    >>> Blog | http://www.extended64.com/blogs/Rafael
    >>>

    >>
    >>
    >> --------------------------------------------------------------------------------
    >>
    >>
    >>> *******************************************************************************
    >>> * *
    >>> * Bugcheck Analysis *
    >>> * *
    >>> *******************************************************************************
    >>>
    >>> SYSTEM_SERVICE_EXCEPTION (3b)
    >>> Arguments:
    >>> Arg1: 00000000c0000005
    >>> Arg2: fffff97fff0ba49e
    >>> Arg3: fffffadfe02531a0
    >>> Arg4: 0000000000000000
    >>>
    >>> Debugging Details:
    >>> ------------------
    >>>
    >>>
    >>> CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >>> rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >>> rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >>> rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >>> r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >>> r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >>> r14=000000000012edf0 r15=0000000078b83980
    >>> iopl=0 nv up ei ng nz na pe nc
    >>> cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    >>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>> ds:002b:0041=????????????????
    >>> Resetting default scope
    >>>
    >>> CUSTOMER_CRASH_COUNT: 3
    >>>
    >>> DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>>
    >>> BUGCHECK_STR: 0x3B
    >>>
    >>> CURRENT_IRQL: 0
    >>>
    >>> LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>>
    >>> STACK_TEXT:
    >>> fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041
    >>> fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 :
    >>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >>> fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340
    >>> 00000000`00000001 00000000`00009001 00000000`00000000 :
    >>> win32k!GreSetRectRgn+0x36
    >>> fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327
    >>> 00000000`0104003f 00000000`0104003f 00000000`0000000b :
    >>> win32k!InternalInvalidate2+0x219
    >>> fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340
    >>> 00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 :
    >>> win32k!xxxInternalInvalidate+0x451
    >>> fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d
    >>> 00000000`00010184 00000000`f6040ba9 00000000`00000000 :
    >>> win32k!xxxRedrawWindow+0x1b8
    >>> fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000
    >>> 00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 :
    >>> win32k!NtUserInvalidateRgn+0x87
    >>> fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000
    >>> 00000000`00000000 00000000`00000000 00000000`00000000 :
    >>> nt!KiSystemServiceCopyEnd+0x3
    >>> 00000000`0012ede8 00000000`00000000 : 00000000`00000000
    >>> 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9
    >>>
    >>>
    >>> FOLLOWUP_IP:
    >>> win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>
    >>> SYMBOL_STACK_INDEX: 0
    >>>
    >>> FOLLOWUP_NAME: MachineOwner
    >>>
    >>> SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>
    >>> MODULE_NAME: win32k
    >>>
    >>> IMAGE_NAME: win32k.sys
    >>>
    >>> DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>>
    >>> STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>>
    >>> FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>
    >>> BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>
    >>> Followup: MachineOwner
    >>> ---------
    >>>

    >>
    >>

    >
    >
     
    John Barnes, Jun 15, 2005
    #12
  13. Rafael Rivera [Extended64.com]

    MHPNW STAFF Guest

    I'm not saying that this is going to solve your problem, but with speeds
    getting up there ..timing issues are very relivent.
    Asus dosn't list very much on this with their boards , but if you look at
    any board at MSI that has a Nvidia chipset they very clearly tell you make
    sure you manully set your mem timing with the correct settings.....
    But then thats just my opinion...
    Dennis

    PS I ment CAS not xas ....little finger slipped


    "MHPNW STAFF" <> wrote in message
    news:...
    >I Checked your MFG with the memory that you listed, and thats what they
    >provided....
    > The agressive timing settings that you listed are primarly for intel based
    > chips.... they recommended to set the xas at 2.5 for amd thats what your
    > mem was tested at....per Corsair
    > attached is a copy
    >
    > Dennis
    > "John Barnes" <> wrote in message
    > news:...
    >> My memory settings are per the memory mfg. 2-2-2-5. I have also run the
    >> Microsoft memory checker with no errors. However we are not talking
    >> about
    >> physical memory. We are talking about the system retaining settings
    >> during
    >> logoff, like task bar settings, in my case the height. Location of icons
    >> on
    >> the desktop, Usually just any newer ones. You know the 'Saving
    >> settings'
    >> part of logoff. Thanks anyway.
    >>
    >>
    >> "MHPNW STAFF" <> wrote in message
    >> news:...
    >>> Just a Note ...
    >>> Double check your bio's settings on your memory .... most boards you
    >>> have
    >>> better luck by manually entering in the timeing settings .These are the
    >>> settings you should be using for your mem: w/ AMD processor ....
    >>>
    >>> AMD settings 2.5 -3-3-6 Intel Settings Are 2.0 3-3-6
    >>>
    >>>
    >>> Hope that it helps
    >>>
    >>>
    >>> Dennis
    >>>
    >>>
    >>> "John Barnes" <> wrote in message
    >>> news:%...
    >>>>I think your system is getting even for your comments about my task bar.
    >>>>FWIW I have a number of settings that randomly disappear, not just the
    >>>>height of the task bar.
    >>>> It seems totally random. 1-5 times the settings stay, 1-2 times the
    >>>> settings are gone. Stability isn't an x64 feature. Maybe SP2? :)
    >>>>
    >>>>
    >>>> "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote
    >>>> in
    >>>> message news:...
    >>>>> Ok usually I can fix problems on my own but this one is driving me up
    >>>>> the wall... I'm receiving seemingly-random BSODs pointing to
    >>>>> win32k.sys.
    >>>>> Already tried the debugger approach but the dumps either point to
    >>>>> unknown memory space or try to assign blame to win32k.sys. I have
    >>>>> attached one of many memory dump "!analyze -v" outputs... Keep in
    >>>>> mind,
    >>>>> every BSOD is something different - What's in the text file is likely
    >>>>> false... I'm getting desperate here... Assume no floppy is present.
    >>>>>
    >>>>> * Already tried...
    >>>>>
    >>>>> memtest86 (passed)
    >>>>> 71.84 Forceware drivers
    >>>>> 70.80 Forceware drivers
    >>>>> Increasing/Decreasing core voltage levels
    >>>>> Repasting of core and GPU
    >>>>> Format
    >>>>>
    >>>>> * Relevant Hardware Info:
    >>>>>
    >>>>> AMD Athlon(tm) 64 Processor 4000+
    >>>>> (Family F, Ext. Family F, Model 7, Ext. Model 7
    >>>>> Stepping A, Revision SH7-CG)
    >>>>> Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >>>>> (dual channel kit, installed correctly)
    >>>>> Asus AV8-SLI (although SLI not being used)
    >>>>> NVIDIA Geforce 6800GT
    >>>>> 500W Ultra X-Connect PSU (eATX compatible)
    >>>>> 2 PATA HDDs, 2 PATA Optical drives
    >>>>>
    >>>>> * Relevant Software Info:
    >>>>>
    >>>>> NVIDIA Forceware drivers v70.80
    >>>>> NVIDIA nForce4 platform drivers NOT installed
    >>>>> (except NIC driver)
    >>>>> AMD Cool(n)Quiet disabled
    >>>>>
    >>>>> * Other Info:
    >>>>>
    >>>>> Processor idle temperature: ~ 44C
    >>>>> GPU idle temperature before repaste: ~ 68C
    >>>>> GPU idle temperature after repaste: ~ 61C
    >>>>> +12V: +11.9V
    >>>>> +5V: +4.84V
    >>>>> Core: +1.58V (increased for diag.)
    >>>>> I/O: +3.30V
    >>>>>
    >>>>> Thanks in advance for any help provided!
    >>>>>
    >>>>> --
    >>>>> Rafael Rivera
    >>>>> Extended64 | http://www.extended64.com
    >>>>> Blog | http://www.extended64.com/blogs/Rafael
    >>>>>
    >>>>
    >>>>
    >>>> --------------------------------------------------------------------------------
    >>>>
    >>>>
    >>>>> *******************************************************************************
    >>>>> * *
    >>>>> * Bugcheck Analysis *
    >>>>> * *
    >>>>> *******************************************************************************
    >>>>>
    >>>>> SYSTEM_SERVICE_EXCEPTION (3b)
    >>>>> Arguments:
    >>>>> Arg1: 00000000c0000005
    >>>>> Arg2: fffff97fff0ba49e
    >>>>> Arg3: fffffadfe02531a0
    >>>>> Arg4: 0000000000000000
    >>>>>
    >>>>> Debugging Details:
    >>>>> ------------------
    >>>>>
    >>>>>
    >>>>> CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >>>>> rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >>>>> rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >>>>> rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >>>>> r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >>>>> r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >>>>> r14=000000000012edf0 r15=0000000078b83980
    >>>>> iopl=0 nv up ei ng nz na pe nc
    >>>>> cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    >>>>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >>>>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>> ds:002b:0041=????????????????
    >>>>> Resetting default scope
    >>>>>
    >>>>> CUSTOMER_CRASH_COUNT: 3
    >>>>>
    >>>>> DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>>>>
    >>>>> BUGCHECK_STR: 0x3B
    >>>>>
    >>>>> CURRENT_IRQL: 0
    >>>>>
    >>>>> LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>>>>
    >>>>> STACK_TEXT:
    >>>>> fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041
    >>>>> fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 :
    >>>>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >>>>> fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340
    >>>>> 00000000`00000001 00000000`00009001 00000000`00000000 :
    >>>>> win32k!GreSetRectRgn+0x36
    >>>>> fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327
    >>>>> 00000000`0104003f 00000000`0104003f 00000000`0000000b :
    >>>>> win32k!InternalInvalidate2+0x219
    >>>>> fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340
    >>>>> 00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 :
    >>>>> win32k!xxxInternalInvalidate+0x451
    >>>>> fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d
    >>>>> 00000000`00010184 00000000`f6040ba9 00000000`00000000 :
    >>>>> win32k!xxxRedrawWindow+0x1b8
    >>>>> fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000
    >>>>> 00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 :
    >>>>> win32k!NtUserInvalidateRgn+0x87
    >>>>> fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000
    >>>>> 00000000`00000000 00000000`00000000 00000000`00000000 :
    >>>>> nt!KiSystemServiceCopyEnd+0x3
    >>>>> 00000000`0012ede8 00000000`00000000 : 00000000`00000000
    >>>>> 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9
    >>>>>
    >>>>>
    >>>>> FOLLOWUP_IP:
    >>>>> win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>>
    >>>>> SYMBOL_STACK_INDEX: 0
    >>>>>
    >>>>> FOLLOWUP_NAME: MachineOwner
    >>>>>
    >>>>> SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>> MODULE_NAME: win32k
    >>>>>
    >>>>> IMAGE_NAME: win32k.sys
    >>>>>
    >>>>> DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>>>>
    >>>>> STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>>>>
    >>>>> FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>> BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>> Followup: MachineOwner
    >>>>> ---------
    >>>>>
    >>>>
    >>>>
    >>>
    >>>

    >>
    >>

    >
    >
    >
     
    MHPNW STAFF, Jun 15, 2005
    #13
  14. John is not having the issue, I am. Ignore his timings. I'll check my
    RAM timings upon next crash or reboot, whichever comes first. Thanks!

    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    MHPNW STAFF wrote:
    > I Checked your MFG with the memory that you listed, and thats what they
    > provided....
    > The agressive timing settings that you listed are primarly for intel based
    > chips.... they recommended to set the xas at 2.5 for amd thats what your mem
    > was tested at....per Corsair
    > attached is a copy
    >
    > Dennis
    > "John Barnes" <> wrote in message
    > news:...
    >
    >>My memory settings are per the memory mfg. 2-2-2-5. I have also run the
    >>Microsoft memory checker with no errors. However we are not talking
    >>about
    >>physical memory. We are talking about the system retaining settings
    >>during
    >>logoff, like task bar settings, in my case the height. Location of icons
    >>on
    >>the desktop, Usually just any newer ones. You know the 'Saving settings'
    >>part of logoff. Thanks anyway.
    >>
    >>
    >>"MHPNW STAFF" <> wrote in message
    >>news:...
    >>
    >>>Just a Note ...
    >>>Double check your bio's settings on your memory .... most boards you have
    >>>better luck by manually entering in the timeing settings .These are the
    >>>settings you should be using for your mem: w/ AMD processor ....
    >>>
    >>>AMD settings 2.5 -3-3-6 Intel Settings Are 2.0 3-3-6
    >>>
    >>>
    >>>Hope that it helps
    >>>
    >>>
    >>>Dennis
    >>>
    >>>
    >>>"John Barnes" <> wrote in message
    >>>news:%...
    >>>
    >>>>I think your system is getting even for your comments about my task bar.
    >>>>FWIW I have a number of settings that randomly disappear, not just the
    >>>>height of the task bar.
    >>>>It seems totally random. 1-5 times the settings stay, 1-2 times the
    >>>>settings are gone. Stability isn't an x64 feature. Maybe SP2? :)
    >>>>
    >>>>
    >>>>"Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    >>>>message news:...
    >>>>
    >>>>>Ok usually I can fix problems on my own but this one is driving me up
    >>>>>the wall... I'm receiving seemingly-random BSODs pointing to
    >>>>>win32k.sys.
    >>>>>Already tried the debugger approach but the dumps either point to
    >>>>>unknown memory space or try to assign blame to win32k.sys. I have
    >>>>>attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    >>>>>every BSOD is something different - What's in the text file is likely
    >>>>>false... I'm getting desperate here... Assume no floppy is present.
    >>>>>
    >>>>>* Already tried...
    >>>>>
    >>>>>memtest86 (passed)
    >>>>>71.84 Forceware drivers
    >>>>>70.80 Forceware drivers
    >>>>>Increasing/Decreasing core voltage levels
    >>>>>Repasting of core and GPU
    >>>>>Format
    >>>>>
    >>>>>* Relevant Hardware Info:
    >>>>>
    >>>>>AMD Athlon(tm) 64 Processor 4000+
    >>>>>(Family F, Ext. Family F, Model 7, Ext. Model 7
    >>>>>Stepping A, Revision SH7-CG)
    >>>>>Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >>>>>(dual channel kit, installed correctly)
    >>>>>Asus AV8-SLI (although SLI not being used)
    >>>>>NVIDIA Geforce 6800GT
    >>>>>500W Ultra X-Connect PSU (eATX compatible)
    >>>>>2 PATA HDDs, 2 PATA Optical drives
    >>>>>
    >>>>>* Relevant Software Info:
    >>>>>
    >>>>>NVIDIA Forceware drivers v70.80
    >>>>>NVIDIA nForce4 platform drivers NOT installed
    >>>>>(except NIC driver)
    >>>>>AMD Cool(n)Quiet disabled
    >>>>>
    >>>>>* Other Info:
    >>>>>
    >>>>>Processor idle temperature: ~ 44C
    >>>>>GPU idle temperature before repaste: ~ 68C
    >>>>>GPU idle temperature after repaste: ~ 61C
    >>>>>+12V: +11.9V
    >>>>>+5V: +4.84V
    >>>>>Core: +1.58V (increased for diag.)
    >>>>>I/O: +3.30V
    >>>>>
    >>>>>Thanks in advance for any help provided!
    >>>>>
    >>>>>--
    >>>>>Rafael Rivera
    >>>>>Extended64 | http://www.extended64.com
    >>>>>Blog | http://www.extended64.com/blogs/Rafael
    >>>>>
    >>>>
    >>>>
    >>>>--------------------------------------------------------------------------------
    >>>>
    >>>>
    >>>>
    >>>>>*******************************************************************************
    >>>>>* *
    >>>>>* Bugcheck Analysis *
    >>>>>* *
    >>>>>*******************************************************************************
    >>>>>
    >>>>>SYSTEM_SERVICE_EXCEPTION (3b)
    >>>>>Arguments:
    >>>>>Arg1: 00000000c0000005
    >>>>>Arg2: fffff97fff0ba49e
    >>>>>Arg3: fffffadfe02531a0
    >>>>>Arg4: 0000000000000000
    >>>>>
    >>>>>Debugging Details:
    >>>>>------------------
    >>>>>
    >>>>>
    >>>>>CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >>>>>rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >>>>>rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >>>>>rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >>>>>r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >>>>>r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >>>>>r14=000000000012edf0 r15=0000000078b83980
    >>>>>iopl=0 nv up ei ng nz na pe nc
    >>>>>cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    >>>>>win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >>>>>fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>>ds:002b:0041=????????????????
    >>>>>Resetting default scope
    >>>>>
    >>>>>CUSTOMER_CRASH_COUNT: 3
    >>>>>
    >>>>>DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>>>>
    >>>>>BUGCHECK_STR: 0x3B
    >>>>>
    >>>>>CURRENT_IRQL: 0
    >>>>>
    >>>>>LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>>>>
    >>>>>STACK_TEXT:
    >>>>>fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041
    >>>>>fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 :
    >>>>>win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >>>>>fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340
    >>>>>00000000`00000001 00000000`00009001 00000000`00000000 :
    >>>>>win32k!GreSetRectRgn+0x36
    >>>>>fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327
    >>>>>00000000`0104003f 00000000`0104003f 00000000`0000000b :
    >>>>>win32k!InternalInvalidate2+0x219
    >>>>>fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340
    >>>>>00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 :
    >>>>>win32k!xxxInternalInvalidate+0x451
    >>>>>fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d
    >>>>>00000000`00010184 00000000`f6040ba9 00000000`00000000 :
    >>>>>win32k!xxxRedrawWindow+0x1b8
    >>>>>fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000
    >>>>>00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 :
    >>>>>win32k!NtUserInvalidateRgn+0x87
    >>>>>fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000
    >>>>>00000000`00000000 00000000`00000000 00000000`00000000 :
    >>>>>nt!KiSystemServiceCopyEnd+0x3
    >>>>>00000000`0012ede8 00000000`00000000 : 00000000`00000000
    >>>>>00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9
    >>>>>
    >>>>>
    >>>>>FOLLOWUP_IP:
    >>>>>win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>>
    >>>>>SYMBOL_STACK_INDEX: 0
    >>>>>
    >>>>>FOLLOWUP_NAME: MachineOwner
    >>>>>
    >>>>>SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>>MODULE_NAME: win32k
    >>>>>
    >>>>>IMAGE_NAME: win32k.sys
    >>>>>
    >>>>>DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>>>>
    >>>>>STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>>>>
    >>>>>FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>>BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>>Followup: MachineOwner
    >>>>>---------
    >>>>>
    >>>>
    >>>>
    >>>

    >>

    >
    >
     
    Rafael Rivera [Extended64.com], Jun 15, 2005
    #14
  15. Rafael Rivera [Extended64.com]

    John Barnes Guest

    This is the memory I have. Four banks . 2 gig. I have checked the Mfg
    site and the same settings are for both AMD and Intel. Several other models
    have 2 for Intel and 2.5 for AMD but this is listed same for both.
    http://www.corsairmemory.com/corsair/products/specs/twinx1024-3200xl.pdf
    http://www.corsairmemory.com/corsair/xms.html Incidentally my x86 system is
    super stable. That is where I have most of my programs and work since so
    little still works on x64 for me.

    a.. CORSAIR XMS 1GB (2 x 512MB) 184-Pin DDR SDRAM DDR 400 (PC 3200)
    Unbuffered Dual Channel Kit System Memory Model TWINX1024-3200XLPT - Retail

    Cas Latency: 2
    Heat Spreader: Yes
    Manufacturer Warranty: Lifetime
    Timing: TCCD 2-2-2-5
    Voltage: 2.75V

    a.. Model #: TWINX1024-3200XLPT

    "MHPNW STAFF" <> wrote in message
    news:...
    >I Checked your MFG with the memory that you listed, and thats what they
    >provided....
    > The agressive timing settings that you listed are primarly for intel based
    > chips.... they recommended to set the xas at 2.5 for amd thats what your
    > mem was tested at....per Corsair
    > attached is a copy
    >
    > Dennis
    > "John Barnes" <> wrote in message
    > news:...
    >> My memory settings are per the memory mfg. 2-2-2-5. I have also run the
    >> Microsoft memory checker with no errors. However we are not talking
    >> about
    >> physical memory. We are talking about the system retaining settings
    >> during
    >> logoff, like task bar settings, in my case the height. Location of icons
    >> on
    >> the desktop, Usually just any newer ones. You know the 'Saving
    >> settings'
    >> part of logoff. Thanks anyway.
    >>
    >>
    >> "MHPNW STAFF" <> wrote in message
    >> news:...
    >>> Just a Note ...
    >>> Double check your bio's settings on your memory .... most boards you
    >>> have
    >>> better luck by manually entering in the timeing settings .These are the
    >>> settings you should be using for your mem: w/ AMD processor ....
    >>>
    >>> AMD settings 2.5 -3-3-6 Intel Settings Are 2.0 3-3-6
    >>>
    >>>
    >>> Hope that it helps
    >>>
    >>>
    >>> Dennis
    >>>
    >>>
    >>> "John Barnes" <> wrote in message
    >>> news:%...
    >>>>I think your system is getting even for your comments about my task bar.
    >>>>FWIW I have a number of settings that randomly disappear, not just the
    >>>>height of the task bar.
    >>>> It seems totally random. 1-5 times the settings stay, 1-2 times the
    >>>> settings are gone. Stability isn't an x64 feature. Maybe SP2? :)
    >>>>
    >>>>
    >>>> "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote
    >>>> in
    >>>> message news:...
    >>>>> Ok usually I can fix problems on my own but this one is driving me up
    >>>>> the wall... I'm receiving seemingly-random BSODs pointing to
    >>>>> win32k.sys.
    >>>>> Already tried the debugger approach but the dumps either point to
    >>>>> unknown memory space or try to assign blame to win32k.sys. I have
    >>>>> attached one of many memory dump "!analyze -v" outputs... Keep in
    >>>>> mind,
    >>>>> every BSOD is something different - What's in the text file is likely
    >>>>> false... I'm getting desperate here... Assume no floppy is present.
    >>>>>
    >>>>> * Already tried...
    >>>>>
    >>>>> memtest86 (passed)
    >>>>> 71.84 Forceware drivers
    >>>>> 70.80 Forceware drivers
    >>>>> Increasing/Decreasing core voltage levels
    >>>>> Repasting of core and GPU
    >>>>> Format
    >>>>>
    >>>>> * Relevant Hardware Info:
    >>>>>
    >>>>> AMD Athlon(tm) 64 Processor 4000+
    >>>>> (Family F, Ext. Family F, Model 7, Ext. Model 7
    >>>>> Stepping A, Revision SH7-CG)
    >>>>> Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >>>>> (dual channel kit, installed correctly)
    >>>>> Asus AV8-SLI (although SLI not being used)
    >>>>> NVIDIA Geforce 6800GT
    >>>>> 500W Ultra X-Connect PSU (eATX compatible)
    >>>>> 2 PATA HDDs, 2 PATA Optical drives
    >>>>>
    >>>>> * Relevant Software Info:
    >>>>>
    >>>>> NVIDIA Forceware drivers v70.80
    >>>>> NVIDIA nForce4 platform drivers NOT installed
    >>>>> (except NIC driver)
    >>>>> AMD Cool(n)Quiet disabled
    >>>>>
    >>>>> * Other Info:
    >>>>>
    >>>>> Processor idle temperature: ~ 44C
    >>>>> GPU idle temperature before repaste: ~ 68C
    >>>>> GPU idle temperature after repaste: ~ 61C
    >>>>> +12V: +11.9V
    >>>>> +5V: +4.84V
    >>>>> Core: +1.58V (increased for diag.)
    >>>>> I/O: +3.30V
    >>>>>
    >>>>> Thanks in advance for any help provided!
    >>>>>
    >>>>> --
    >>>>> Rafael Rivera
    >>>>> Extended64 | http://www.extended64.com
    >>>>> Blog | http://www.extended64.com/blogs/Rafael
    >>>>>
    >>>>
    >>>>
    >>>> --------------------------------------------------------------------------------
    >>>>
    >>>>
    >>>>> *******************************************************************************
    >>>>> * *
    >>>>> * Bugcheck Analysis *
    >>>>> * *
    >>>>> *******************************************************************************
    >>>>>
    >>>>> SYSTEM_SERVICE_EXCEPTION (3b)
    >>>>> Arguments:
    >>>>> Arg1: 00000000c0000005
    >>>>> Arg2: fffff97fff0ba49e
    >>>>> Arg3: fffffadfe02531a0
    >>>>> Arg4: 0000000000000000
    >>>>>
    >>>>> Debugging Details:
    >>>>> ------------------
    >>>>>
    >>>>>
    >>>>> CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >>>>> rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >>>>> rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >>>>> rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >>>>> r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >>>>> r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >>>>> r14=000000000012edf0 r15=0000000078b83980
    >>>>> iopl=0 nv up ei ng nz na pe nc
    >>>>> cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    >>>>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >>>>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>> ds:002b:0041=????????????????
    >>>>> Resetting default scope
    >>>>>
    >>>>> CUSTOMER_CRASH_COUNT: 3
    >>>>>
    >>>>> DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>>>>
    >>>>> BUGCHECK_STR: 0x3B
    >>>>>
    >>>>> CURRENT_IRQL: 0
    >>>>>
    >>>>> LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>>>>
    >>>>> STACK_TEXT:
    >>>>> fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041
    >>>>> fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 :
    >>>>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >>>>> fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340
    >>>>> 00000000`00000001 00000000`00009001 00000000`00000000 :
    >>>>> win32k!GreSetRectRgn+0x36
    >>>>> fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327
    >>>>> 00000000`0104003f 00000000`0104003f 00000000`0000000b :
    >>>>> win32k!InternalInvalidate2+0x219
    >>>>> fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340
    >>>>> 00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 :
    >>>>> win32k!xxxInternalInvalidate+0x451
    >>>>> fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d
    >>>>> 00000000`00010184 00000000`f6040ba9 00000000`00000000 :
    >>>>> win32k!xxxRedrawWindow+0x1b8
    >>>>> fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000
    >>>>> 00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 :
    >>>>> win32k!NtUserInvalidateRgn+0x87
    >>>>> fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000
    >>>>> 00000000`00000000 00000000`00000000 00000000`00000000 :
    >>>>> nt!KiSystemServiceCopyEnd+0x3
    >>>>> 00000000`0012ede8 00000000`00000000 : 00000000`00000000
    >>>>> 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9
    >>>>>
    >>>>>
    >>>>> FOLLOWUP_IP:
    >>>>> win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>>
    >>>>> SYMBOL_STACK_INDEX: 0
    >>>>>
    >>>>> FOLLOWUP_NAME: MachineOwner
    >>>>>
    >>>>> SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>> MODULE_NAME: win32k
    >>>>>
    >>>>> IMAGE_NAME: win32k.sys
    >>>>>
    >>>>> DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>>>>
    >>>>> STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>>>>
    >>>>> FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>> BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>
    >>>>> Followup: MachineOwner
    >>>>> ---------
    >>>>>
    >>>>
    >>>>
    >>>
    >>>

    >>
    >>

    >
    >
    >
     
    John Barnes, Jun 15, 2005
    #15
  16. Rafael Rivera [Extended64.com]

    MHPNW STAFF Guest

    Rafael said it all...

    The orig thread is named Crashing Mystery...
    I thought that was what we were all working on....
    Sorry

    Dennis


    "John Barnes" <> wrote in message
    news:...
    > This is the memory I have. Four banks . 2 gig. I have checked the Mfg
    > site and the same settings are for both AMD and Intel. Several other
    > models have 2 for Intel and 2.5 for AMD but this is listed same for both.
    > http://www.corsairmemory.com/corsair/products/specs/twinx1024-3200xl.pdf
    > http://www.corsairmemory.com/corsair/xms.html Incidentally my x86 system
    > is super stable. That is where I have most of my programs and work since
    > so little still works on x64 for me.
    >
    > a.. CORSAIR XMS 1GB (2 x 512MB) 184-Pin DDR SDRAM DDR 400 (PC 3200)
    > Unbuffered Dual Channel Kit System Memory Model TWINX1024-3200XLPT -
    > Retail
    >
    > Cas Latency: 2
    > Heat Spreader: Yes
    > Manufacturer Warranty: Lifetime
    > Timing: TCCD 2-2-2-5
    > Voltage: 2.75V
    >
    > a.. Model #: TWINX1024-3200XLPT
    >
    > "MHPNW STAFF" <> wrote in message
    > news:...
    >>I Checked your MFG with the memory that you listed, and thats what they
    >>provided....
    >> The agressive timing settings that you listed are primarly for intel
    >> based chips.... they recommended to set the xas at 2.5 for amd thats what
    >> your mem was tested at....per Corsair
    >> attached is a copy
    >>
    >> Dennis
    >> "John Barnes" <> wrote in message
    >> news:...
    >>> My memory settings are per the memory mfg. 2-2-2-5. I have also run
    >>> the
    >>> Microsoft memory checker with no errors. However we are not talking
    >>> about
    >>> physical memory. We are talking about the system retaining settings
    >>> during
    >>> logoff, like task bar settings, in my case the height. Location of
    >>> icons on
    >>> the desktop, Usually just any newer ones. You know the 'Saving
    >>> settings'
    >>> part of logoff. Thanks anyway.
    >>>
    >>>
    >>> "MHPNW STAFF" <> wrote in message
    >>> news:...
    >>>> Just a Note ...
    >>>> Double check your bio's settings on your memory .... most boards you
    >>>> have
    >>>> better luck by manually entering in the timeing settings .These are the
    >>>> settings you should be using for your mem: w/ AMD processor ....
    >>>>
    >>>> AMD settings 2.5 -3-3-6 Intel Settings Are 2.0 3-3-6
    >>>>
    >>>>
    >>>> Hope that it helps
    >>>>
    >>>>
    >>>> Dennis
    >>>>
    >>>>
    >>>> "John Barnes" <> wrote in message
    >>>> news:%...
    >>>>>I think your system is getting even for your comments about my task
    >>>>>bar.
    >>>>>FWIW I have a number of settings that randomly disappear, not just the
    >>>>>height of the task bar.
    >>>>> It seems totally random. 1-5 times the settings stay, 1-2 times the
    >>>>> settings are gone. Stability isn't an x64 feature. Maybe SP2? :)
    >>>>>
    >>>>>
    >>>>> "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote
    >>>>> in
    >>>>> message news:...
    >>>>>> Ok usually I can fix problems on my own but this one is driving me up
    >>>>>> the wall... I'm receiving seemingly-random BSODs pointing to
    >>>>>> win32k.sys.
    >>>>>> Already tried the debugger approach but the dumps either point to
    >>>>>> unknown memory space or try to assign blame to win32k.sys. I have
    >>>>>> attached one of many memory dump "!analyze -v" outputs... Keep in
    >>>>>> mind,
    >>>>>> every BSOD is something different - What's in the text file is likely
    >>>>>> false... I'm getting desperate here... Assume no floppy is present.
    >>>>>>
    >>>>>> * Already tried...
    >>>>>>
    >>>>>> memtest86 (passed)
    >>>>>> 71.84 Forceware drivers
    >>>>>> 70.80 Forceware drivers
    >>>>>> Increasing/Decreasing core voltage levels
    >>>>>> Repasting of core and GPU
    >>>>>> Format
    >>>>>>
    >>>>>> * Relevant Hardware Info:
    >>>>>>
    >>>>>> AMD Athlon(tm) 64 Processor 4000+
    >>>>>> (Family F, Ext. Family F, Model 7, Ext. Model 7
    >>>>>> Stepping A, Revision SH7-CG)
    >>>>>> Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >>>>>> (dual channel kit, installed correctly)
    >>>>>> Asus AV8-SLI (although SLI not being used)
    >>>>>> NVIDIA Geforce 6800GT
    >>>>>> 500W Ultra X-Connect PSU (eATX compatible)
    >>>>>> 2 PATA HDDs, 2 PATA Optical drives
    >>>>>>
    >>>>>> * Relevant Software Info:
    >>>>>>
    >>>>>> NVIDIA Forceware drivers v70.80
    >>>>>> NVIDIA nForce4 platform drivers NOT installed
    >>>>>> (except NIC driver)
    >>>>>> AMD Cool(n)Quiet disabled
    >>>>>>
    >>>>>> * Other Info:
    >>>>>>
    >>>>>> Processor idle temperature: ~ 44C
    >>>>>> GPU idle temperature before repaste: ~ 68C
    >>>>>> GPU idle temperature after repaste: ~ 61C
    >>>>>> +12V: +11.9V
    >>>>>> +5V: +4.84V
    >>>>>> Core: +1.58V (increased for diag.)
    >>>>>> I/O: +3.30V
    >>>>>>
    >>>>>> Thanks in advance for any help provided!
    >>>>>>
    >>>>>> --
    >>>>>> Rafael Rivera
    >>>>>> Extended64 | http://www.extended64.com
    >>>>>> Blog | http://www.extended64.com/blogs/Rafael
    >>>>>>
    >>>>>
    >>>>>
    >>>>> --------------------------------------------------------------------------------
    >>>>>
    >>>>>
    >>>>>> *******************************************************************************
    >>>>>> * *
    >>>>>> * Bugcheck Analysis *
    >>>>>> * *
    >>>>>> *******************************************************************************
    >>>>>>
    >>>>>> SYSTEM_SERVICE_EXCEPTION (3b)
    >>>>>> Arguments:
    >>>>>> Arg1: 00000000c0000005
    >>>>>> Arg2: fffff97fff0ba49e
    >>>>>> Arg3: fffffadfe02531a0
    >>>>>> Arg4: 0000000000000000
    >>>>>>
    >>>>>> Debugging Details:
    >>>>>> ------------------
    >>>>>>
    >>>>>>
    >>>>>> CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >>>>>> rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >>>>>> rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >>>>>> rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >>>>>> r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >>>>>> r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >>>>>> r14=000000000012edf0 r15=0000000078b83980
    >>>>>> iopl=0 nv up ei ng nz na pe nc
    >>>>>> cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    >>>>>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >>>>>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>>> ds:002b:0041=????????????????
    >>>>>> Resetting default scope
    >>>>>>
    >>>>>> CUSTOMER_CRASH_COUNT: 3
    >>>>>>
    >>>>>> DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>>>>>
    >>>>>> BUGCHECK_STR: 0x3B
    >>>>>>
    >>>>>> CURRENT_IRQL: 0
    >>>>>>
    >>>>>> LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>>>>>
    >>>>>> STACK_TEXT:
    >>>>>> fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041
    >>>>>> fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 :
    >>>>>> win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >>>>>> fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340
    >>>>>> 00000000`00000001 00000000`00009001 00000000`00000000 :
    >>>>>> win32k!GreSetRectRgn+0x36
    >>>>>> fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327
    >>>>>> 00000000`0104003f 00000000`0104003f 00000000`0000000b :
    >>>>>> win32k!InternalInvalidate2+0x219
    >>>>>> fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340
    >>>>>> 00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 :
    >>>>>> win32k!xxxInternalInvalidate+0x451
    >>>>>> fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d
    >>>>>> 00000000`00010184 00000000`f6040ba9 00000000`00000000 :
    >>>>>> win32k!xxxRedrawWindow+0x1b8
    >>>>>> fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000
    >>>>>> 00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 :
    >>>>>> win32k!NtUserInvalidateRgn+0x87
    >>>>>> fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000
    >>>>>> 00000000`00000000 00000000`00000000 00000000`00000000 :
    >>>>>> nt!KiSystemServiceCopyEnd+0x3
    >>>>>> 00000000`0012ede8 00000000`00000000 : 00000000`00000000
    >>>>>> 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9
    >>>>>>
    >>>>>>
    >>>>>> FOLLOWUP_IP:
    >>>>>> win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>> fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>>>>>
    >>>>>> SYMBOL_STACK_INDEX: 0
    >>>>>>
    >>>>>> FOLLOWUP_NAME: MachineOwner
    >>>>>>
    >>>>>> SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>>
    >>>>>> MODULE_NAME: win32k
    >>>>>>
    >>>>>> IMAGE_NAME: win32k.sys
    >>>>>>
    >>>>>> DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>>>>>
    >>>>>> STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>>>>>
    >>>>>> FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>>
    >>>>>> BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>>>>>
    >>>>>> Followup: MachineOwner
    >>>>>> ---------
    >>>>>>
    >>>>>
    >>>>>
    >>>>
    >>>>
    >>>
    >>>

    >>
    >>
    >>

    >
    >
     
    MHPNW STAFF, Jun 15, 2005
    #16
  17. =?Utf-8?B?Q2hyaXM=?=, Jun 15, 2005
    #17
  18. Have you tried reinstalls? If you can successfully reinstall, then you
    know that the error was just a hosed configuration. If you can't
    reinstall, because of more errors..... then most likely you've got a
    hardware problem. A real hand tool can be found here
    http://www.ultimatebootcd.com/ just download the iso, burn it then run
    some of the utilities like the HardDrive utility for your computer, try
    memtest86 and memtest86+ and it's always best to test your power supply.

    JB

    Rafael Rivera [Extended64.com] wrote:
    > Ok usually I can fix problems on my own but this one is driving me up
    > the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    > Already tried the debugger approach but the dumps either point to
    > unknown memory space or try to assign blame to win32k.sys. I have
    > attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    > every BSOD is something different - What's in the text file is likely
    > false... I'm getting desperate here... Assume no floppy is present.
    >
    > * Already tried...
    >
    > memtest86 (passed)
    > 71.84 Forceware drivers
    > 70.80 Forceware drivers
    > Increasing/Decreasing core voltage levels
    > Repasting of core and GPU
    > Format
    >
    > * Relevant Hardware Info:
    >
    > AMD Athlon(tm) 64 Processor 4000+
    > (Family F, Ext. Family F, Model 7, Ext. Model 7
    > Stepping A, Revision SH7-CG)
    > Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    > (dual channel kit, installed correctly)
    > Asus AV8-SLI (although SLI not being used)
    > NVIDIA Geforce 6800GT
    > 500W Ultra X-Connect PSU (eATX compatible)
    > 2 PATA HDDs, 2 PATA Optical drives
    >
    > * Relevant Software Info:
    >
    > NVIDIA Forceware drivers v70.80
    > NVIDIA nForce4 platform drivers NOT installed
    > (except NIC driver)
    > AMD Cool(n)Quiet disabled
    >
    > * Other Info:
    >
    > Processor idle temperature: ~ 44C
    > GPU idle temperature before repaste: ~ 68C
    > GPU idle temperature after repaste: ~ 61C
    > +12V: +11.9V
    > +5V: +4.84V
    > Core: +1.58V (increased for diag.)
    > I/O: +3.30V
    >
    > Thanks in advance for any help provided!
    >
    >
    > ------------------------------------------------------------------------
    >
    > *******************************************************************************
    > * *
    > * Bugcheck Analysis *
    > * *
    > *******************************************************************************
    >
    > SYSTEM_SERVICE_EXCEPTION (3b)
    > Arguments:
    > Arg1: 00000000c0000005
    > Arg2: fffff97fff0ba49e
    > Arg3: fffffadfe02531a0
    > Arg4: 0000000000000000
    >
    > Debugging Details:
    > ------------------
    >
    >
    > CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    > rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    > rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    > rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    > r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    > r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    > r14=000000000012edf0 r15=0000000078b83980
    > iopl=0 nv up ei ng nz na pe nc
    > cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    > win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    > fffff97f`ff0ba49e 488906 mov [rsi],rax ds:002b:0041=????????????????
    > Resetting default scope
    >
    > CUSTOMER_CRASH_COUNT: 3
    >
    > DEFAULT_BUCKET_ID: DRIVER_FAULT
    >
    > BUGCHECK_STR: 0x3B
    >
    > CURRENT_IRQL: 0
    >
    > LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >
    > STACK_TEXT:
    > fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041 fffff97f`ff085c8d fffff97f`f78005e8 fffff97f`f7bd9340 : win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    > fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340 00000000`00000001 00000000`00009001 00000000`00000000 : win32k!GreSetRectRgn+0x36
    > fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327 00000000`0104003f 00000000`0104003f 00000000`0000000b : win32k!InternalInvalidate2+0x219
    > fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340 00000000`0104003f 00000000`00000001 fffff97f`f7bd9340 : win32k!xxxInternalInvalidate+0x451
    > fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d 00000000`00010184 00000000`f6040ba9 00000000`00000000 : win32k!xxxRedrawWindow+0x1b8
    > fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000 00000000`00000000 fffff97f`ff049550 00000000`7d8192e1 : win32k!NtUserInvalidateRgn+0x87
    > fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    > 00000000`0012ede8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9
    >
    >
    > FOLLOWUP_IP:
    > win32k!RGNOBJAPI::RGNOBJAPI+2e
    > fffff97f`ff0ba49e 488906 mov [rsi],rax
    >
    > SYMBOL_STACK_INDEX: 0
    >
    > FOLLOWUP_NAME: MachineOwner
    >
    > SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > MODULE_NAME: win32k
    >
    > IMAGE_NAME: win32k.sys
    >
    > DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >
    > STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >
    > FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > Followup: MachineOwner
    > ---------
     
    Jerry Bradford, Jun 16, 2005
    #18
  19. Rafael Rivera [Extended64.com]

    John Barnes Guest

    Haven't heard your results for a couple of days. Problem fixed, and how?


    "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    message news:...
    > Ok usually I can fix problems on my own but this one is driving me up
    > the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    > Already tried the debugger approach but the dumps either point to
    > unknown memory space or try to assign blame to win32k.sys. I have
    > attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    > every BSOD is something different - What's in the text file is likely
    > false... I'm getting desperate here... Assume no floppy is present.
    >
    > * Already tried...
    >
    > memtest86 (passed)
    > 71.84 Forceware drivers
    > 70.80 Forceware drivers
    > Increasing/Decreasing core voltage levels
    > Repasting of core and GPU
    > Format
    >
    > * Relevant Hardware Info:
    >
    > AMD Athlon(tm) 64 Processor 4000+
    > (Family F, Ext. Family F, Model 7, Ext. Model 7
    > Stepping A, Revision SH7-CG)
    > Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    > (dual channel kit, installed correctly)
    > Asus AV8-SLI (although SLI not being used)
    > NVIDIA Geforce 6800GT
    > 500W Ultra X-Connect PSU (eATX compatible)
    > 2 PATA HDDs, 2 PATA Optical drives
    >
    > * Relevant Software Info:
    >
    > NVIDIA Forceware drivers v70.80
    > NVIDIA nForce4 platform drivers NOT installed
    > (except NIC driver)
    > AMD Cool(n)Quiet disabled
    >
    > * Other Info:
    >
    > Processor idle temperature: ~ 44C
    > GPU idle temperature before repaste: ~ 68C
    > GPU idle temperature after repaste: ~ 61C
    > +12V: +11.9V
    > +5V: +4.84V
    > Core: +1.58V (increased for diag.)
    > I/O: +3.30V
    >
    > Thanks in advance for any help provided!
    >
    > --
    > Rafael Rivera
    > Extended64 | http://www.extended64.com
    > Blog | http://www.extended64.com/blogs/Rafael
    >



    --------------------------------------------------------------------------------


    > *******************************************************************************
    > *
    > *
    > * Bugcheck Analysis
    > *
    > *
    > *
    > *******************************************************************************
    >
    > SYSTEM_SERVICE_EXCEPTION (3b)
    > Arguments:
    > Arg1: 00000000c0000005
    > Arg2: fffff97fff0ba49e
    > Arg3: fffffadfe02531a0
    > Arg4: 0000000000000000
    >
    > Debugging Details:
    > ------------------
    >
    >
    > CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    > rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    > rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    > rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    > r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    > r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    > r14=000000000012edf0 r15=0000000078b83980
    > iopl=0 nv up ei ng nz na pe nc
    > cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b
    > efl=00010282
    > win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    > fffff97f`ff0ba49e 488906 mov [rsi],rax
    > ds:002b:0041=????????????????
    > Resetting default scope
    >
    > CUSTOMER_CRASH_COUNT: 3
    >
    > DEFAULT_BUCKET_ID: DRIVER_FAULT
    >
    > BUGCHECK_STR: 0x3B
    >
    > CURRENT_IRQL: 0
    >
    > LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >
    > STACK_TEXT:
    > fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041 fffff97f`ff085c8d
    > fffff97f`f78005e8 fffff97f`f7bd9340 : win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    > fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340 00000000`00000001
    > 00000000`00009001 00000000`00000000 : win32k!GreSetRectRgn+0x36
    > fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327 00000000`0104003f
    > 00000000`0104003f 00000000`0000000b : win32k!InternalInvalidate2+0x219
    > fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340 00000000`0104003f
    > 00000000`00000001 fffff97f`f7bd9340 : win32k!xxxInternalInvalidate+0x451
    > fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d 00000000`00010184
    > 00000000`f6040ba9 00000000`00000000 : win32k!xxxRedrawWindow+0x1b8
    > fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000 00000000`00000000
    > fffff97f`ff049550 00000000`7d8192e1 : win32k!NtUserInvalidateRgn+0x87
    > fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000 00000000`00000000
    > 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    > 00000000`0012ede8 00000000`00000000 : 00000000`00000000 00000000`00000000
    > 00000000`00000000 00000000`00000000 : 0x78b842d9
    >
    >
    > FOLLOWUP_IP:
    > win32k!RGNOBJAPI::RGNOBJAPI+2e
    > fffff97f`ff0ba49e 488906 mov [rsi],rax
    >
    > SYMBOL_STACK_INDEX: 0
    >
    > FOLLOWUP_NAME: MachineOwner
    >
    > SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > MODULE_NAME: win32k
    >
    > IMAGE_NAME: win32k.sys
    >
    > DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >
    > STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >
    > FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >
    > Followup: MachineOwner
    > ---------
    >
     
    John Barnes, Jun 16, 2005
    #19
  20. Hi John,

    I'm currently testing another beta driver configuration...

    (NEW!) Leaked 76.80 Nvidia Forceware drivers
    WinXP IDE driver version 5.24
    SMBus driver version 4.48 (WHQL)
    Ethernet NRM driver version 4.75 (WHQL)
    Network management tools version 4.80

    Aside from the Windows GUI to be somewhat sluggish in terms of feedback
    (eg. moving windows around), I've been stable for an entire day. I also
    sent a kernel dump to Joseph for analysis.

    Will keep all updated.

    Rafael Rivera
    Extended64 | http://www.extended64.com
    Blog | http://www.extended64.com/blogs/Rafael

    John Barnes wrote:
    > Haven't heard your results for a couple of days. Problem fixed, and how?
    >
    >
    > "Rafael Rivera [Extended64.com]" <rafael*at*extended64*dot*com> wrote in
    > message news:...
    >
    >>Ok usually I can fix problems on my own but this one is driving me up
    >>the wall... I'm receiving seemingly-random BSODs pointing to win32k.sys.
    >>Already tried the debugger approach but the dumps either point to
    >>unknown memory space or try to assign blame to win32k.sys. I have
    >>attached one of many memory dump "!analyze -v" outputs... Keep in mind,
    >>every BSOD is something different - What's in the text file is likely
    >>false... I'm getting desperate here... Assume no floppy is present.
    >>
    >>* Already tried...
    >>
    >>memtest86 (passed)
    >>71.84 Forceware drivers
    >>70.80 Forceware drivers
    >>Increasing/Decreasing core voltage levels
    >>Repasting of core and GPU
    >>Format
    >>
    >>* Relevant Hardware Info:
    >>
    >>AMD Athlon(tm) 64 Processor 4000+
    >>(Family F, Ext. Family F, Model 7, Ext. Model 7
    >>Stepping A, Revision SH7-CG)
    >>Corsair CMX512-3200C2 PC3200 DDR 400mhz memory
    >>(dual channel kit, installed correctly)
    >>Asus AV8-SLI (although SLI not being used)
    >>NVIDIA Geforce 6800GT
    >>500W Ultra X-Connect PSU (eATX compatible)
    >>2 PATA HDDs, 2 PATA Optical drives
    >>
    >>* Relevant Software Info:
    >>
    >>NVIDIA Forceware drivers v70.80
    >>NVIDIA nForce4 platform drivers NOT installed
    >>(except NIC driver)
    >>AMD Cool(n)Quiet disabled
    >>
    >>* Other Info:
    >>
    >>Processor idle temperature: ~ 44C
    >>GPU idle temperature before repaste: ~ 68C
    >>GPU idle temperature after repaste: ~ 61C
    >>+12V: +11.9V
    >>+5V: +4.84V
    >>Core: +1.58V (increased for diag.)
    >>I/O: +3.30V
    >>
    >>Thanks in advance for any help provided!
    >>
    >>--
    >>Rafael Rivera
    >>Extended64 | http://www.extended64.com
    >>Blog | http://www.extended64.com/blogs/Rafael
    >>

    >
    >
    >
    > --------------------------------------------------------------------------------
    >
    >
    >
    >>*******************************************************************************
    >>*
    >>*
    >>* Bugcheck Analysis
    >>*
    >>*
    >>*
    >>*******************************************************************************
    >>
    >>SYSTEM_SERVICE_EXCEPTION (3b)
    >>Arguments:
    >>Arg1: 00000000c0000005
    >>Arg2: fffff97fff0ba49e
    >>Arg3: fffffadfe02531a0
    >>Arg4: 0000000000000000
    >>
    >>Debugging Details:
    >>------------------
    >>
    >>
    >>CONTEXT: fffffadfe02531a0 -- (.cxr fffffadfe02531a0)
    >>rax=fffffa80025d6600 rbx=0000000001040041 rcx=fffffadfff103990
    >>rdx=0000000000000000 rsi=0000000001040041 rdi=0000000000000000
    >>rip=fffff97fff0ba49e rsp=fffffadfe02539b0 rbp=0000000000000327
    >>r8=0000000000000000 r9=fffffa80025d6600 r10=00000000000001c5
    >>r11=fffffadfe02539a8 r12=00000000000001c5 r13=0000000000000000
    >>r14=000000000012edf0 r15=0000000078b83980
    >>iopl=0 nv up ei ng nz na pe nc
    >>cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b
    >>efl=00010282
    >>win32k!RGNOBJAPI::RGNOBJAPI+0x2e:
    >>fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>ds:002b:0041=????????????????
    >>Resetting default scope
    >>
    >>CUSTOMER_CRASH_COUNT: 3
    >>
    >>DEFAULT_BUCKET_ID: DRIVER_FAULT
    >>
    >>BUGCHECK_STR: 0x3B
    >>
    >>CURRENT_IRQL: 0
    >>
    >>LAST_CONTROL_TRANSFER: from fffff97fff0a5046 to fffff97fff0ba49e
    >>
    >>STACK_TEXT:
    >>fffffadf`e02539b0 fffff97f`ff0a5046 : 00000000`01040041 fffff97f`ff085c8d
    >>fffff97f`f78005e8 fffff97f`f7bd9340 : win32k!RGNOBJAPI::RGNOBJAPI+0x2e
    >>fffffadf`e0253a00 fffff97f`ff07acb3 : fffff97f`f7bd9340 00000000`00000001
    >>00000000`00009001 00000000`00000000 : win32k!GreSetRectRgn+0x36
    >>fffffadf`e0253a80 fffff97f`ff0a5497 : 00000000`00000327 00000000`0104003f
    >>00000000`0104003f 00000000`0000000b : win32k!InternalInvalidate2+0x219
    >>fffffadf`e0253b00 fffff97f`ff0a73e6 : fffff97f`f7bd9340 00000000`0104003f
    >>00000000`00000001 fffff97f`f7bd9340 : win32k!xxxInternalInvalidate+0x451
    >>fffffadf`e0253bc0 fffff97f`ff0495d4 : 00000000`1a20cc0d 00000000`00010184
    >>00000000`f6040ba9 00000000`00000000 : win32k!xxxRedrawWindow+0x1b8
    >>fffffadf`e0253c20 fffff800`01041422 : 00000000`00000000 00000000`00000000
    >>fffff97f`ff049550 00000000`7d8192e1 : win32k!NtUserInvalidateRgn+0x87
    >>fffffadf`e0253c70 00000000`78b842d9 : 00000000`00000000 00000000`00000000
    >>00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    >>00000000`0012ede8 00000000`00000000 : 00000000`00000000 00000000`00000000
    >>00000000`00000000 00000000`00000000 : 0x78b842d9
    >>
    >>
    >>FOLLOWUP_IP:
    >>win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>fffff97f`ff0ba49e 488906 mov [rsi],rax
    >>
    >>SYMBOL_STACK_INDEX: 0
    >>
    >>FOLLOWUP_NAME: MachineOwner
    >>
    >>SYMBOL_NAME: win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>
    >>MODULE_NAME: win32k
    >>
    >>IMAGE_NAME: win32k.sys
    >>
    >>DEBUG_FLR_IMAGE_TIMESTAMP: 42436088
    >>
    >>STACK_COMMAND: .cxr fffffadfe02531a0 ; kb
    >>
    >>FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>
    >>BUCKET_ID: X64_0x3B_win32k!RGNOBJAPI::RGNOBJAPI+2e
    >>
    >>Followup: MachineOwner
    >>---------
    >>

    >
    >
    >
     
    Rafael Rivera [Extended64.com], Jun 16, 2005
    #20
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Richard G Carruthers

    Help I am getting Desperate!!

    Richard G Carruthers, Aug 8, 2005, in forum: Windows 64bit
    Replies:
    10
    Views:
    543
    jackfrost64
    Aug 10, 2005
  2. Miles Bader

    Re: P&S sellers getting desperate

    Miles Bader, Aug 14, 2009, in forum: Digital Photography
    Replies:
    14
    Views:
    563
    Bob Larter
    Aug 17, 2009
  3. Rich

    Re: P&S sellers getting desperate

    Rich, Aug 15, 2009, in forum: Digital Photography
    Replies:
    22
    Views:
    718
    John Turco
    Aug 23, 2009
  4. RichA

    Magazines, websites getting desperate

    RichA, Jul 1, 2010, in forum: Digital Photography
    Replies:
    131
    Views:
    2,086
    John A.
    Jul 5, 2010
  5. Valorie McLaughlin
    Replies:
    8
    Views:
    1,063
    Jeff Gaines
    Sep 13, 2010
Loading...

Share This Page