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

Bsod


  • Please log in to reply
2 replies to this topic

#1 4133

4133

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:42 PM

Posted 27 June 2008 - 06:23 PM

I did the whole thing the said to do to find the mini bumps so here they are. The guides never mentioned how to fix could somebody help me? I have 7 minidump data analysis things. from the 7 minidumps i had. please help :thumbsup: .
1.


I did everything on the http://forums.majorgeeks.com/showthread.php?t=35246 so did that like fix everything or do i have to do something else with the info it gave me?(info is down below)
It didnt go any further so i wasnt sure if that was it.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini010806-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun Jan 8 18:28:14.734 2006 (GMT-4)
System Uptime: 0 days 4:37:09.275
Loading Kernel Symbols
........................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image NOWMEMDF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NOWMEMDF.sys
*** ERROR: Module load completed but symbols could not be loaded for NOWMEMDF.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7dae704, eb8ddca0, 0}

Probably caused by : NOWMEMDF.sys ( NOWMEMDF+43a )

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: f7dae704, The address that the exception occurred at
Arg3: eb8ddca0, 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:
+fffffffff7dae704
f7dae704 8b42fc mov eax,dword ptr [edx-4]

TRAP_FRAME: eb8ddca0 -- (.trap 0xffffffffeb8ddca0)
ErrCode = 00000000
eax=f7daf6ac ebx=f7dae6f0 ecx=00000000 edx=00000ffc esi=f7daf6ac edi=eb8ddd44
eip=f7dae704 esp=eb8ddd14 ebp=eb8ddd20 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
f7dae704 8b42fc mov eax,dword ptr [edx-4] ds:0023:00000ff8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: clubbox.exe

LAST_CONTROL_TRANSFER: from eba8643a to f7dae704

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
eb8ddd20 eba8643a 00000594 7ffde008 00128918 0xf7dae704
eb8ddd48 804de7ec 00000594 7ffde008 00128918 NOWMEMDF+0x43a
eb8ddd48 7c90eb94 00000594 7ffde008 00128918 nt!KiFastCallEntry+0xf8
001285e0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
NOWMEMDF+43a
eba8643a ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NOWMEMDF+43a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NOWMEMDF

IMAGE_NAME: NOWMEMDF.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4368229b

FAILURE_BUCKET_ID: 0x8E_NOWMEMDF+43a

BUCKET_ID: 0x8E_NOWMEMDF+43a

Followup: MachineOwner
---------
2.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini011508-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Tue Jan 15 20:39:59.421 2008 (GMT-4)
System Uptime: 0 days 11:08:43.083
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {852c2020, 859b22b0, f7a3bcb4, 1}

Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
ERROR - could not read driver name for bugcheck parameter 3

Probably caused by : nv4_disp.dll ( nv4_disp+1ac75 )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: 852c2020, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 859b22b0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7a3bcb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

ERROR - could not read driver name for bugcheck parameter 3


FAULTING_THREAD: 852c2020

FAULTING_IP:
nv4_disp+1ac75
bf02cc75 ?? ???

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 421dfc18

MODULE_NAME: nv4_disp

FAULTING_MODULE: bf012000 nv4_disp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 804e39ce to 804db7f3

STACK_TEXT:
f292f3ec 804e39ce f7a3bb40 f7a3bb70 00000000 nt!KiUnlockDispatcherDatabase+0x77
f292f400 f79d8a67 f7a3bb94 00000000 00000000 nt!KeSetEvent+0x74
f292f6f4 804eee9a f7a3bb40 f292f740 f292f734 watchdog!WatchdogKernelApc+0x13b
f292f744 804eeed9 00000000 00000000 00000000 nt!KiDeliverApc+0xb3
f292f75c 804dc143 00000000 e1b8a010 00009ca1 nt!KiSwapThread+0x64
f292f784 bf85a31f 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x1c2
f292f7a0 bf02cc75 85adfce8 f292f7c0 000645d0 win32k!EngWaitForSingleObject+0x23
WARNING: Stack unwind information not available. Following frames may be wrong.
f292f7ac 000645d0 bc721008 f292f8b4 e1b8a010 nv4_disp+0x1ac75
f292f7c0 ffffffff bf034b6a e1b8a010 f7b960ee 0x645d0
f292f7c4 bf034b6a e1b8a010 f7b960ee 00000000 0xffffffff
f292f7c8 e1b8a010 f7b960ee 00000000 00000003 nv4_disp+0x22b6a
f292f7cc f7b960ee 00000000 00000003 bf035318 0xe1b8a010
f292f8cc bf805a4a e18a5cf8 e1b8a178 000002cc 0xf7b960ee
f292f8f8 bf805d0a e18a5cf8 e1b89350 00000000 win32k!REGION::vDeleteREGION+0x14
f292f918 bf9a55c0 e1b89350 e1b57cf0 00000001 win32k!WatchdogDrvCopyBits+0x53
f292f944 bf839f31 e18a5cf8 e1b89350 00000000 win32k!xloIdent
f292fb6c bf80a4ef e18a5cf8 00000000 00000000 win32k!EngCopyBits+0xcb
f292fc00 bf8cee9a e18a5ce8 bf9a55c0 e1b2da40 win32k!NtGdiBitBlt+0x51c
f292fc54 bf8cf1cc 000002c8 000e0274 bbea3b78 win32k!SaveVisualBits+0x123
f292fcc4 bf8ce53b e12aa9b8 00000000 00000000 win32k!xxxCreateGhostWindow+0x1e8
f292fce4 bf8cec24 bf801077 00000022 019dfff8 win32k!xxxScanGhosts+0x6d
f292fd30 bf87263c 856af878 00000003 f292fd54 win32k!GhostThread+0xa4
f292fd40 bf80109a 856af878 f292fd64 019dfff8 win32k!xxxCreateSystemThreads+0x6a
f292fd54 804de7ec 00000001 00000022 00000000 win32k!NtUserCallOneParam+0x23
f292fd54 7c90eb94 00000001 00000022 00000000 nt!KiFastCallEntry+0xf8
00000000 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .thread 0xffffffff852c2020 ; kb

FOLLOWUP_IP:
nv4_disp+1ac75
bf02cc75 ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nv4_disp+1ac75

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2005_02_24

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2005_02_24

Followup: MachineOwner
---------
3.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini090707-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Sep 7 14:13:37.453 2007 (GMT-4)
System Uptime: 0 days 2:27:31.999
Loading Kernel Symbols
.......................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7b08e2a, ef2c5c2c, 0}

Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )

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: f7b08e2a, The address that the exception occurred at
Arg3: ef2c5c2c, 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:
+fffffffff7b08e2a
f7b08e2a 8b42fc mov eax,dword ptr [edx-4]

TRAP_FRAME: ef2c5c2c -- (.trap 0xffffffffef2c5c2c)
ErrCode = 00000000
eax=f7b0b5c4 ebx=00000001 ecx=00000000 edx=00000290 esi=0012c69c edi=f7b0b5c4
eip=f7b08e2a esp=ef2c5ca0 ebp=ef2c5cb8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
f7b08e2a 8b42fc mov eax,dword ptr [edx-4] ds:0023:0000028c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: KnightOnLine.ex

LAST_CONTROL_TRANSFER: from f7b08ed9 to f7b08e2a

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ef2c5cb8 f7b08ed9 85000020 00000004 00000004 0xf7b08e2a
ef2c5d34 804de7ec 00000290 00000000 00000000 0xf7b08ed9
ef2c5d34 7c90eb94 00000290 00000000 00000000 nt!KiFastCallEntry+0xf8
0012c668 7c90d8ef 7c801671 00000290 00000000 0x7c90eb94
0012c6cc 458b91d7 00000290 85000020 0012c774 0x7c90d8ef
0012c704 458a8c72 458b4df0 458b4cb0 00008100 0x458b91d7
0012c73c 014b4381 00000290 85000020 0012c774 0x458a8c72
00000000 00000000 00000000 00000000 00000000 0x14b4381


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiFastCallEntry+f8
804de7ec 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiFastCallEntry+f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

FAILURE_BUCKET_ID: 0x8E_nt!KiFastCallEntry+f8

BUCKET_ID: 0x8E_nt!KiFastCallEntry+f8

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

4.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini112405-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Thu Nov 24 14:25:15.437 2005 (GMT-4)
System Uptime: 0 days 2:20:27.971
Loading Kernel Symbols
.......................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image NOWMEMDF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NOWMEMDF.sys
*** ERROR: Module load completed but symbols could not be loaded for NOWMEMDF.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7d56960, ebc55ca0, 0}

Probably caused by : NOWMEMDF.sys ( NOWMEMDF+43a )

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: f7d56960, The address that the exception occurred at
Arg3: ebc55ca0, 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:
+fffffffff7d56960
f7d56960 8b42fc mov eax,dword ptr [edx-4]

TRAP_FRAME: ebc55ca0 -- (.trap 0xffffffffebc55ca0)
ErrCode = 00000000
eax=f7d576ac ebx=f7d5694c ecx=00000000 edx=00000ffc esi=f7d576ac edi=ebc55d44
eip=f7d56960 esp=ebc55d14 ebp=ebc55d20 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
f7d56960 8b42fc mov eax,dword ptr [edx-4] ds:0023:00000ff8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: ClubBox.exe

LAST_CONTROL_TRANSFER: from ebca243a to f7d56960

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ebc55d20 ebca243a 000005b4 7ffdf008 00128918 0xf7d56960
ebc55d48 804de7ec 000005b4 7ffdf008 00128918 NOWMEMDF+0x43a
ebc55d48 7c90eb94 000005b4 7ffdf008 00128918 nt!KiFastCallEntry+0xf8
001285e0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
NOWMEMDF+43a
ebca243a ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NOWMEMDF+43a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NOWMEMDF

IMAGE_NAME: NOWMEMDF.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4368229b

FAILURE_BUCKET_ID: 0x8E_NOWMEMDF+43a

BUCKET_ID: 0x8E_NOWMEMDF+43a

Followup: MachineOwner
---------
5.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini112505-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Nov 25 12:32:36.265 2005 (GMT-4)
System Uptime: 0 days 0:47:13.804
Loading Kernel Symbols
........................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image NOWMEMDF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NOWMEMDF.sys
*** ERROR: Module load completed but symbols could not be loaded for NOWMEMDF.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7daa960, ec18eca0, 0}

Probably caused by : NOWMEMDF.sys ( NOWMEMDF+43a )

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: f7daa960, The address that the exception occurred at
Arg3: ec18eca0, 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:
+fffffffff7daa960
f7daa960 8b42fc mov eax,dword ptr [edx-4]

TRAP_FRAME: ec18eca0 -- (.trap 0xffffffffec18eca0)
ErrCode = 00000000
eax=f7dab6ac ebx=f7daa94c ecx=00000000 edx=00000ffc esi=f7dab6ac edi=ec18ed44
eip=f7daa960 esp=ec18ed14 ebp=ec18ed20 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
f7daa960 8b42fc mov eax,dword ptr [edx-4] ds:0023:00000ff8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: GameMon.des

LAST_CONTROL_TRANSFER: from ebcd643a to f7daa960

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ec18ed20 ebcd643a 00000190 7ffdf000 012dfc18 0xf7daa960
ec18ed48 804de7ec 00000190 7ffdf000 012dfc18 NOWMEMDF+0x43a
ec18ed48 7c90eb94 00000190 7ffdf000 012dfc18 nt!KiFastCallEntry+0xf8
012dfbf4 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
NOWMEMDF+43a
ebcd643a ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NOWMEMDF+43a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NOWMEMDF

IMAGE_NAME: NOWMEMDF.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4368229b

FAILURE_BUCKET_ID: 0x8E_NOWMEMDF+43a

BUCKET_ID: 0x8E_NOWMEMDF+43a

Followup: MachineOwner
---------
6.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini112505-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Nov 25 12:46:50.921 2005 (GMT-4)
System Uptime: 0 days 0:13:57.453
Loading Kernel Symbols
.......................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image NOWMEMDF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NOWMEMDF.sys
*** ERROR: Module load completed but symbols could not be loaded for NOWMEMDF.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7d9e960, ebcfeca0, 0}

Probably caused by : NOWMEMDF.sys ( NOWMEMDF+43a )

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: f7d9e960, The address that the exception occurred at
Arg3: ebcfeca0, 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:
+fffffffff7d9e960
f7d9e960 8b42fc mov eax,dword ptr [edx-4]

TRAP_FRAME: ebcfeca0 -- (.trap 0xffffffffebcfeca0)
ErrCode = 00000000
eax=f7d9f6ac ebx=f7d9e94c ecx=00000000 edx=00000ffc esi=f7d9f6ac edi=ebcfed44
eip=f7d9e960 esp=ebcfed14 ebp=ebcfed20 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
f7d9e960 8b42fc mov eax,dword ptr [edx-4] ds:0023:00000ff8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: ClubBox.exe

LAST_CONTROL_TRANSFER: from ec08343a to f7d9e960

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ebcfed20 ec08343a 000004e0 7ffd3008 00128918 0xf7d9e960
ebcfed48 804de7ec 000004e0 7ffd3008 00128918 NOWMEMDF+0x43a
ebcfed48 7c90eb94 000004e0 7ffd3008 00128918 nt!KiFastCallEntry+0xf8
001285e0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
NOWMEMDF+43a
ec08343a ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NOWMEMDF+43a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NOWMEMDF

IMAGE_NAME: NOWMEMDF.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4368229b

FAILURE_BUCKET_ID: 0x8E_NOWMEMDF+43a

BUCKET_ID: 0x8E_NOWMEMDF+43a

Followup: MachineOwner
---------
7.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini121205-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Mon Dec 12 18:18:42.250 2005 (GMT-4)
System Uptime: 0 days 1:50:26.787
Loading Kernel Symbols
............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image NOWMEMDF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NOWMEMDF.sys
*** ERROR: Module load completed but symbols could not be loaded for NOWMEMDF.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7db2960, ebca5ca0, 0}

Probably caused by : splitter.sys ( splitter+960 )

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: f7db2960, The address that the exception occurred at
Arg3: ebca5ca0, 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:
splitter+960
f7db2960 8b42fc mov eax,dword ptr [edx-4]

TRAP_FRAME: ebca5ca0 -- (.trap 0xffffffffebca5ca0)
ErrCode = 00000000
eax=f7db36ac ebx=f7db294c ecx=00000000 edx=00000ffc esi=f7db36ac edi=ebca5d44
eip=f7db2960 esp=ebca5d14 ebp=ebca5d20 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
<Unloaded_splitter.sys>+0x960:
f7db2960 8b42fc mov eax,dword ptr [edx-4] ds:0023:00000ff8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: clubbox.exe

IP_MODULE_UNLOADED:
splitter+960
f7db2960 8b42fc mov eax,dword ptr [edx-4]

LAST_CONTROL_TRANSFER: from eba7943a to f7db2960

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ebca5d20 eba7943a 00000570 7ffde008 00128918 <Unloaded_splitter.sys>+0x960
ebca5d48 804de7ec 00000570 7ffde008 00128918 NOWMEMDF+0x43a
ebca5d48 7c90eb94 00000570 7ffde008 00128918 nt!KiFastCallEntry+0xf8
001285e0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
splitter+960
f7db2960 8b42fc mov eax,dword ptr [edx-4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: splitter+960

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: splitter

IMAGE_NAME: splitter.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x8E_splitter+960

BUCKET_ID: 0x8E_splitter+960

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

If somebody could help me that would be great. I keep getting these blue screens.

Edited by 4133, 27 June 2008 - 06:29 PM.


BC AdBot (Login to Remove)

 


m

#2 nigglesnush85

nigglesnush85

  • Members
  • 4,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:UK
  • Local time:05:42 PM

Posted 27 June 2008 - 08:48 PM

Hello 4133,

The information provided is just information it has not fixed anything. The files indicate your computer crashed numerous times due to the following applications called...

clubbox,
Nowcom Memory Defender,
Graphics,
GameMon.

There can be many reasons for this, I would update these programs or remove the ones you don't need. I would also advise you download https://psi.secunia.com/ this tool and update the system.
Regards,

Alan.

#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,074 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:42 PM

Posted 28 June 2008 - 07:39 AM

Most of the errors have occurred in your memory (the c0000005 stuff).

I'd uninstall the Nowcom stuff - both the clubbox and the Memory Defender seem to be from there
I'd uninstall your GameMon for Knight Online (KnightOnLine.ex)
If that doesn't fix it, then I'd uninstall and reinstall a fresh copy of the latest nVidia video drivers for your system: http://www.nvidia.com/Download/index.aspx?lang=en-us

If that still doesn't fix it, then I'd suggest running this free, bootable memory tester: http://www.memtest86.com/

Edited by usasma, 28 June 2008 - 07:40 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users