Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Mini011109-01 amd sysdata error


  • Please log in to reply
6 replies to this topic

#1 lzr84

lzr84

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:55 PM

Posted 17 January 2009 - 08:18 PM

LOCALS~1\Temp\WER4138.dir00\Mini011109-01.dmp
LOCALS~1\Temp\WER4138.dir00\sysdata.xml

Above two are the errors that i got when i switch on the computer and i don't know what caused it. What should i do??

Thank in advance~

BC AdBot (Login to Remove)

 


#2 garmanma

garmanma

    Computer Masochist


  • Staff Emeritus
  • 27,809 posts
  • OFFLINE
  •  
  • Location:Cleveland, Ohio
  • Local time:05:55 PM

Posted 18 January 2009 - 10:13 AM

It's a dump file. Information can be found in this tutorial:
http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
Mark
Posted Image
why won't my laptop work?

Having grandkids is God's way of giving you a 2nd chance because you were too busy working your butt off the 1st time around
Do not send me PMs with problems that should be posted in the forums. Keep it in the forums, so everyone benefits
Become a BleepingComputer fan: Facebook and Twitter

#3 lzr84

lzr84
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:55 PM

Posted 23 January 2009 - 10:10 PM

Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Jan 18 19:42:04.968 2009 (GMT+8)
System Uptime: 0 days 10:34:54.539
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image s3gnb.dll, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for s3gnb.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {8122ada8, ffbd4448, 812431b0, 1}

Probably caused by : s3gnb.dll ( s3gnb+386 )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8122ada8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: ffbd4448, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 812431b0, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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


FAULTING_THREAD: 8122ada8

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from bf9dc499 to bf9d5386

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f97f1588 bf9dc499 e19c1010 f97f15c8 00000040 s3gnb+0x386
00000000 00000000 00000000 00000000 00000000 s3gnb+0x7499


STACK_COMMAND: .thread 0xffffffff8122ada8 ; kb

FOLLOWUP_IP:
s3gnb+386
bf9d5386 81e2ffffff05 and edx,5FFFFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: s3gnb+386

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: s3gnb

IMAGE_NAME: s3gnb.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3ea38782

FAILURE_BUCKET_ID: 0xEA_IMAGE_s3gnb.dll_DATE_2003_04_21

BUCKET_ID: 0xEA_IMAGE_s3gnb.dll_DATE_2003_04_21

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

#4 lzr84

lzr84
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:55 PM

Posted 23 January 2009 - 10:13 PM

BTW i got 33 files.. do i need to do for all??


Microsoft Windows Debugger Version 6.10.0003.233 X86
Copyright Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jan 17 12:41:28.843 2009 (GMT+8)
System Uptime: 0 days 4:59:50.410
Loading Kernel Symbols
...............................................................
..............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image s3gnb.dll, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for s3gnb.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {8122dda8, 8115d978, 8122a1d8, 1}

Probably caused by : s3gnb.dll ( s3gnb+386 )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8122dda8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 8115d978, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8122a1d8, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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


FAULTING_THREAD: 8122dda8

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 2

BUGCHECK_STR: 0xEA

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from bf9dc499 to bf9d5386

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f97d7588 bf9dc499 e19dc010 f97d75c8 00000030 s3gnb+0x386
f97d75bc bf805b06 f4ce27e4 e2644a2e 00000000 s3gnb+0x7499
f97d7608 bf8a629f e2644590 e19e3e90 00000000 win32k!WatchdogDrvCopyBits+0x53
f97d7650 bf850b8f bf805aba e14873f8 e2644590 win32k!OffCopyBits+0x7d
f97d7710 bf8c5f92 00000000 e14873f8 e2644590 win32k!vSpReadFromScreen+0x147
f97d77a8 bf827ba1 e1487390 e14873f8 e2644590 win32k!vSpSmallUnderlayCopy+0xd0
f97d7890 bf938c99 e19db048 0000000e 00000018 win32k!bSpUpdatePosition+0x28d
f97d78c0 bf879c2a e19e3e90 000003f4 000000ae win32k!EngMovePointer+0x140
f97d78e4 bf879fc6 e19db008 000003f4 000000ae win32k!vMovePointer+0x72
f97d7908 bf87a765 e19db008 000003f4 000000ae win32k!GreMovePointer+0xd9
f97d7944 bf87ab28 000003f4 000000ae 00000000 win32k!xxxMoveEventAbsolute+0x13c
f97d797c bf879a8d 01105d96 8122dda8 f97d79d4 win32k!ProcessMouseInput+0x16e
f97d798c 804f1718 e1a0e4a8 e1a0e4d0 00000000 win32k!InputApc+0x4e
f97d79d4 804ecae9 00000000 00000000 00000000 nt!KiDeliverApc+0x124
f97d79ec 804e3b7d 804e3a0d e1a30c48 00000000 nt!KiSwapThread+0x64
f97d7a24 bf807a6c 00000003 81200838 00000001 nt!KeWaitForMultipleObjects+0x284
f97d7a5c bf88fbf6 00000002 81200838 bf892b44 win32k!xxxMsgWaitForMultipleObjects+0xb0
f97d7d30 bf878ba3 bf9ab100 00000001 f97d7d54 win32k!xxxDesktopThread+0x339
f97d7d40 bf80108a bf9ab100 f97d7d64 0073fff4 win32k!xxxCreateSystemThreads+0x6a
f97d7d54 804de7ec 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f97d7d54 7c90e4f4 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
00000000 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: .thread 0xffffffff8122dda8 ; kb

FOLLOWUP_IP:
s3gnb+386
bf9d5386 81e2ffffff05 and edx,5FFFFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: s3gnb+386

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: s3gnb

IMAGE_NAME: s3gnb.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3ea38782

FAILURE_BUCKET_ID: 0xEA_IMAGE_s3gnb.dll_DATE_2003_04_21

BUCKET_ID: 0xEA_IMAGE_s3gnb.dll_DATE_2003_04_21

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

Edited by lzr84, 23 January 2009 - 10:16 PM.


#5 hamluis

hamluis

    Moderator


  • Moderator
  • 55,263 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:55 PM

Posted 24 January 2009 - 09:22 AM

http://www.bleepingcomputer.com/filedb/s3gnb.dll-7636.html

I'd uninstall the current video drivers...and reinstall either a fresh version of the current drivers or...an updated version.

Louis

#6 lzr84

lzr84
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:55 PM

Posted 24 January 2009 - 10:10 AM

http://www.bleepingcomputer.com/filedb/s3gnb.dll-7636.html

I'd uninstall the current video drivers...and reinstall either a fresh version of the current drivers or...an updated version.

Louis



there are files inside the mini dump file, should i delete away those?? i surf the net.. some said delete the files..

#7 hamluis

hamluis

    Moderator


  • Moderator
  • 55,263 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:55 PM

Posted 24 January 2009 - 11:25 AM

I guess that I don't know what you are saying...the .dmp file is just a file for reference, reading, etc...similar to a text or document file.

I don't even bother to read my minidump files, I just delete them. But if I thought that there was some data contained therein that would be useful to me in solving a situation, I would read them...and subsequently delete them because they have outlived their usefulness (once I overcame the situation), not because I believed they could do any harm to the system.

The one thing about the Web to always remember...anyone can say/suggest just about anything. The fact that such is done does not make the assertion any more valid than any other unintentional misstatement of fact/premise.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users