Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Member graf's Avatar
    Join Date
    Mar 2006
    Posts
    134
    Points
    0

    Default Blue screen Error , Here's the Debugging report.

    Here, the report. but I don't know what to do with it, any help is apresheated.

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


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

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.060220-1746
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Sat Feb 24 02:53:24.237 2007 (GMT-6)
    System Uptime: 0 days 1:04:59.800
    Loading Kernel Symbols
    .....................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, f73f4cdb, f73f4c5c, 0}

    Probably caused by : win32k.sys ( win32k!NtGdiGetTextMetricsW+20 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: f73f4cdb, The address that the exception occurred at
    Arg3: f73f4c5c, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    +fffffffff73f4cdb
    f73f4cdb f73a idiv eax,dword ptr [edx]

    TRAP_FRAME: f73f4c5c -- (.trap fffffffff73f4c5c)
    ErrCode = 00000000
    eax=00000001 ebx=bf83aa1a ecx=01c51f00 edx=00000000 esi=00000000 edi=00000000
    eip=f73f4cdb esp=f73f4cd0 ebp=f73f4cd7 iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    f73f4cdb f73a idiv eax,dword ptr [edx] ds:0023:00000000=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: avant.exe

    LAST_CONTROL_TRANSFER: from 83aa3af7 to f73f4cdb

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: 17002000010004

    STACK_COMMAND: dds F73F4CE0-0x20 ; kb

    STACK_TEXT:
    f73f4cc0 00000000
    f73f4cc4 f73f4cdb
    f73f4cc8 00000008
    f73f4ccc 00010202
    f73f4cd0 f73f4d64
    f73f4cd4 e327dd08
    f73f4cd8 f73f4d50
    f73f4cdc bf83aa3a win32k!NtGdiGetTextMetricsW+0x20
    f73f4ce0 e14a6690
    f73f4ce4 f73f4cf4
    f73f4ce8 f73f4d64
    f73f4cec 0012cbd4
    f73f4cf0 bf83aa1a win32k!NtGdiGetTextMetricsW
    f73f4cf4 0000000e
    f73f4cf8 0000000c
    f73f4cfc 00000002
    f73f4d00 00000002
    f73f4d04 00000000
    f73f4d08 00000007
    f73f4d0c 00000015
    f73f4d10 000002bc
    f73f4d14 00000000
    f73f4d18 00000060
    f73f4d1c 00000060
    f73f4d20 fb020020
    f73f4d24 0020001f
    f73f4d28 27000000
    f73f4d2c 00000000
    f73f4d30 7ffdf000
    f73f4d34 201fff1e
    f73f4d38 f73f4ce8
    f73f4d3c f73f4754


    FOLLOWUP_IP:
    win32k!NtGdiGetTextMetricsW+20
    bf83aa3a 8bf0 mov esi,eax

    SYMBOL_NAME: win32k!NtGdiGetTextMetricsW+20

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

    FAILURE_BUCKET_ID: 0x8E_win32k!NtGdiGetTextMetricsW+20

    BUCKET_ID: 0x8E_win32k!NtGdiGetTextMetricsW+20

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

  2. #2
    Member Spyware Fighter zep516's Avatar
    Join Date
    Dec 2005
    Location
    Pittsburgh, Pa
    Posts
    7,175
    Points
    1308

    Default

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

    Was someone else helping you already?

    Graf,

    Does the machine run at all, if so download (memtest86) from here and run it:

    http://www.memtest86.com/

  3. #3
    Member Help2Go Moderator
    Join Date
    May 2003
    Location
    Boston, MA USA
    Posts
    2,994
    Points
    931

    Default

    avant.exe & win32k.sys is the issue.

    You can try uninstalling/reinstalling the avant browser. You may also want to try updating your video card drivers and do as zep/the tutorial suggests and run a memory diagnostics program such as memtest86 @ http://www.memtest86.com

    With this "win32k!NtGdiGetTextMetricsW" i'm going more with a RAM or Video Problem because that is a call to GDI (programming functions for Windows graphics output)

    Partieā„¢

  4. #4
    Member graf's Avatar
    Join Date
    Mar 2006
    Posts
    134
    Points
    0

    Default

    I'm going to run the program and see what it says , thanks guys

  5. #5
    Member graf's Avatar
    Join Date
    Mar 2006
    Posts
    134
    Points
    0

    Default

    I ran the memroy program and it said that nothing was wrong. so I still need some help. if anyone has an answer please feel free to shair.

  6. #6
    Member Spyware Fighter zep516's Avatar
    Join Date
    Dec 2005
    Location
    Pittsburgh, Pa
    Posts
    7,175
    Points
    1308

    Default

    If you have a video card try reseating it- reinstall the video driver for your viedo card, a lagre percentage of blue screen errors are ''hardware and device driver related'', make sure your not running hot and the computer is clean free of dust- if your not sure what is inside as far as hardware and the associated drivers go here and click download it will creat a profile of the computer :

    www.belarc.com

    Hardware & device drivers! if it is on board video still check for most current driver from the manfactures site and down load.

    Zep

  7. #7
    Member graf's Avatar
    Join Date
    Mar 2006
    Posts
    134
    Points
    0

    Default

    Heres another report. Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.060220-1746
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Tue Feb 27 00:07:06.667 2007 (GMT-6)
    System Uptime: 0 days 1:55:32.234
    Loading Kernel Symbols
    ........................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10000050, {d66c90e9, 1, f3c2a527, 0}


    Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!GreBatchTextOut+344 )

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

    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: d66c90e9, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: f3c2a527, 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: d66c90e9

    FAULTING_IP:
    +fffffffff3c2a527
    f3c2a527 0010 add byte ptr [eax],dl

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: BitComet.exe

    LAST_CONTROL_TRANSFER: from bf813c74 to f3c2a527

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    f3c2a558 bf813c74 f3c2a7f8 000002f8 00000115 0xf3c2a527
    f3c2a6c0 bf80dee2 f3c2a7f8 7ffdf1dc 0000005c win32k!GreBatchTextOut+0x344
    f3c2a814 804de7be 00000248 0012f03c 0012f054 win32k!NtGdiFlushUserBatch+0x11b
    f3c2a920 804e4acb 00001f80 804e2490 804e5760 nt!KiFastCallEntry+0xca
    f3c2a944 bf800b3b fed95b50 bf8c468d bbe46c18 nt!KeSetEventBoostPriority+0xaf
    f3c2a98c bf813e90 f3c2ad44 bf986924 bf98fde8 win32k!EnterCrit+0x21
    f3c2a9a4 bf8bd93f 00000000 000c04fe 00000000 win32k!SfnDWORD+0x100
    bf8c468d 90909090 909005eb 8b909090 4d83e865 win32k!xxxHkCallHook+0x274
    bf8c46a1 cf8bd9eb f402b1e8 89ff33ff b8e9fc5d 0x90909090
    bf8c46a5 f402b1e8 89ff33ff b8e9fc5d f6000000 0xcf8bd9eb
    bf8c46a9 89ff33ff b8e9fc5d f6000000 840f0406 0xf402b1e8
    bf8c46ad b8e9fc5d f6000000 840f0406 000000c7 0x89ff33ff
    bf8c46b1 f6000000 840f0406 000000c7 76ff016a 0xb8e9fc5d
    bf8c46b5 840f0406 000000c7 76ff016a d1e85704 0xf6000000
    bf8c46b9 00000000 76ff016a d1e85704 8bfff67e 0x840f0406


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!GreBatchTextOut+344
    bf813c74 8b03 mov eax,dword ptr [ebx]

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

    SYMBOL_NAME: win32k!GreBatchTextOut+344

    FAILURE_BUCKET_ID: 0x50_W_win32k!GreBatchTextOut+344

    BUCKET_ID: 0x50_W_win32k!GreBatchTextOut+344

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

  8. #8
    Member Help2Go Moderator
    Join Date
    May 2003
    Location
    Boston, MA USA
    Posts
    2,994
    Points
    931

    Default

    If you haven't yet, please update your video card drivers. Also, bitcomet.exe, hopefully you have the BitTorrent client called BitComet. If not bitcomet.exe is also associated with a virus. Please, make sure before posting again that you have updated your video card drivers. If you need help with that please respond and ask.

    Thank You,

    Partie

  9. #9
    Member graf's Avatar
    Join Date
    Mar 2006
    Posts
    134
    Points
    0

    Default

    I updated my video card drivers a while back so they should be current. I have a Nvida card. but if you can help me see if I did it right, that would be cool.

  10. #10
    Member Help2Go Moderator
    Join Date
    May 2003
    Location
    Boston, MA USA
    Posts
    2,994
    Points
    931

    Default

    Most definitely. Do you know what kind of card do you have? I know it's NVidia but what model?

    Partie

Page 1 of 2 12 LastLast