Page 1 of 1
BSOD Errors - Dump File analysis
#1
Posted 18 June 2010 - 11:03 PM
Hi all,
I've been having a lot of BSOD errors lately and don't understand why. I went through the tutorial on how to get my dump file info and will post it here. I see something about Chrome in it... I did have a lot of tabs open in Chrome the last time I got the BSOD error. Could that have caused it??
Thanks ahead of time for your help!
Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini061810-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
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Fri Jun 18 19:05:10.750 2010 (UTC - 5:00)
System Uptime: 4 days 12:00:38.312
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bf953715, b66eec00, 0}
Probably caused by : win32k.sys ( win32k!GreGetGlyphIndicesW+af )
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: bf953715, The address that the exception occurred at
Arg3: b66eec00, 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:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
TRAP_FRAME: b66eec00 -- (.trap 0xffffffffb66eec00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=00000000 edx=e4a76c14 esi=e23af000 edi=e4a76818
eip=bf953715 esp=b66eec74 ebp=b66eec8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!GreGetGlyphIndicesW+0xaf:
bf953715 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from bf94ada2 to bf953715
STACK_TEXT:
b66eec8c bf94ada2 e4e7e008 e23af200 e46675b0 win32k!GreGetGlyphIndicesW+0xaf
b66eed28 bf94ae1e c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesWInternal+0xf2
b66eed48 8053d658 c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesW+0x1b
b66eed48 7c90e514 c7010e62 0013edb0 00000100 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013eb40 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!GreGetGlyphIndicesW+af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bdd0c20
FAILURE_BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
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: bf953715, The address that the exception occurred at
Arg3: b66eec00, 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:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
TRAP_FRAME: b66eec00 -- (.trap 0xffffffffb66eec00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=00000000 edx=e4a76c14 esi=e23af000 edi=e4a76818
eip=bf953715 esp=b66eec74 ebp=b66eec8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!GreGetGlyphIndicesW+0xaf:
bf953715 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from bf94ada2 to bf953715
STACK_TEXT:
b66eec8c bf94ada2 e4e7e008 e23af200 e46675b0 win32k!GreGetGlyphIndicesW+0xaf
b66eed28 bf94ae1e c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesWInternal+0xf2
b66eed48 8053d658 c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesW+0x1b
b66eed48 7c90e514 c7010e62 0013edb0 00000100 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013eb40 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!GreGetGlyphIndicesW+af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bdd0c20
FAILURE_BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
Followup: MachineOwner
---------
I've been having a lot of BSOD errors lately and don't understand why. I went through the tutorial on how to get my dump file info and will post it here. I see something about Chrome in it... I did have a lot of tabs open in Chrome the last time I got the BSOD error. Could that have caused it??
Thanks ahead of time for your help!
Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini061810-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
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Fri Jun 18 19:05:10.750 2010 (UTC - 5:00)
System Uptime: 4 days 12:00:38.312
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bf953715, b66eec00, 0}
Probably caused by : win32k.sys ( win32k!GreGetGlyphIndicesW+af )
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: bf953715, The address that the exception occurred at
Arg3: b66eec00, 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:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
TRAP_FRAME: b66eec00 -- (.trap 0xffffffffb66eec00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=00000000 edx=e4a76c14 esi=e23af000 edi=e4a76818
eip=bf953715 esp=b66eec74 ebp=b66eec8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!GreGetGlyphIndicesW+0xaf:
bf953715 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from bf94ada2 to bf953715
STACK_TEXT:
b66eec8c bf94ada2 e4e7e008 e23af200 e46675b0 win32k!GreGetGlyphIndicesW+0xaf
b66eed28 bf94ae1e c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesWInternal+0xf2
b66eed48 8053d658 c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesW+0x1b
b66eed48 7c90e514 c7010e62 0013edb0 00000100 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013eb40 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!GreGetGlyphIndicesW+af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bdd0c20
FAILURE_BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
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: bf953715, The address that the exception occurred at
Arg3: b66eec00, 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:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
TRAP_FRAME: b66eec00 -- (.trap 0xffffffffb66eec00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=00000000 edx=e4a76c14 esi=e23af000 edi=e4a76818
eip=bf953715 esp=b66eec74 ebp=b66eec8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!GreGetGlyphIndicesW+0xaf:
bf953715 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from bf94ada2 to bf953715
STACK_TEXT:
b66eec8c bf94ada2 e4e7e008 e23af200 e46675b0 win32k!GreGetGlyphIndicesW+0xaf
b66eed28 bf94ae1e c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesWInternal+0xf2
b66eed48 8053d658 c7010e62 0013edb0 00000100 win32k!NtGdiGetGlyphIndicesW+0x1b
b66eed48 7c90e514 c7010e62 0013edb0 00000100 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013eb40 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreGetGlyphIndicesW+af
bf953715 8b4004 mov eax,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!GreGetGlyphIndicesW+af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bdd0c20
FAILURE_BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af
Followup: MachineOwner
---------
#2
Posted 19 June 2010 - 07:30 AM
Try using less tabs in Chrome, and see if the issue still exists. If it stops, then your computer doesn't have the resources available to handle that many tabs.
My work schedule is as follows: Mon and Tues 1800 to 0600, Friday - Sunday 1800EST to 0600, and Wednesday to Thursday 1800est to 0600. So if I do not respond right away I am at work.
----------------
If I am helping you, then Please Send Me a Message!with your thread link in it. This is only if I haven't replied back to you within 24 to 48 hours.
----------------
My Main Site || My Backup Site || steam://friends/add/cryptodan Add me to your Steam Friends.
#3
Posted 19 June 2010 - 07:48 AM
Let's try a different look.
Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.
Double-click BlueScreenView.exe file.
When scanning is done, Edit/Select All.
Then File/Save Selected Items.
Save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content and paste it into your next reply.
Louis
Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.
Double-click BlueScreenView.exe file.
When scanning is done, Edit/Select All.
Then File/Save Selected Items.
Save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content and paste it into your next reply.
Louis
#4
Posted 19 June 2010 - 10:12 AM
I definitely tend to get a lot of tabs open in Chrome. However, there have been times I've had way more tabs than I did last night and I've had no problems.
Here is the text from the file, Louis.
==================================================
Dump File : Mini061810-01.dmp
Crash Time : 6/18/2010 7:06:14 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953715
Parameter 3 : 0xb66eec00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153715
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini061010-02.dmp
Crash Time : 6/10/2010 7:45:23 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe14f501c
Parameter 2 : 0x00000000
Parameter 3 : 0xbf8374d3
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+374d3
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061010-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini061010-01.dmp
Crash Time : 6/10/2010 7:02:33 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xa1ce1b57
Parameter 2 : 0x00000000
Parameter 3 : 0xbf83722e
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+3722e
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061010-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini050410-02.dmp
Crash Time : 5/4/2010 10:34:11 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953492
Parameter 3 : 0xee3eb7d0
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153492
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini050410-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini050410-01.dmp
Crash Time : 5/4/2010 9:37:16 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8124e9
Parameter 3 : 0xb93c9878
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+124e9
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini050410-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini033110-01.dmp
Crash Time : 3/31/2010 9:18:41 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe109801c
Parameter 2 : 0x00000000
Parameter 3 : 0xbf8b9425
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+b9425
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini033110-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini030810-01.dmp
Crash Time : 3/8/2010 12:06:51 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953492
Parameter 3 : 0xb75b2c00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153492
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini030810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini081908-01.dmp
Crash Time : 8/19/2008 6:49:46 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000002
Parameter 2 : 0x8295a240
Parameter 3 : 0x82adbc88
Parameter 4 : 0x81e213c0
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+63b5
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini081908-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini062008-01.dmp
Crash Time : 6/20/2008 7:19:00 AM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 0x00000000
Parameter 2 : 0x805463f0
Parameter 3 : 0xb2104000
Parameter 4 : 0x00000175
Caused By Driver : hal.dll
Caused By Address : hal.dll+58d7
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062008-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
Here is the text from the file, Louis.
==================================================
Dump File : Mini061810-01.dmp
Crash Time : 6/18/2010 7:06:14 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953715
Parameter 3 : 0xb66eec00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153715
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini061010-02.dmp
Crash Time : 6/10/2010 7:45:23 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe14f501c
Parameter 2 : 0x00000000
Parameter 3 : 0xbf8374d3
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+374d3
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061010-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini061010-01.dmp
Crash Time : 6/10/2010 7:02:33 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xa1ce1b57
Parameter 2 : 0x00000000
Parameter 3 : 0xbf83722e
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+3722e
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061010-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini050410-02.dmp
Crash Time : 5/4/2010 10:34:11 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953492
Parameter 3 : 0xee3eb7d0
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153492
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini050410-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini050410-01.dmp
Crash Time : 5/4/2010 9:37:16 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8124e9
Parameter 3 : 0xb93c9878
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+124e9
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini050410-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini033110-01.dmp
Crash Time : 3/31/2010 9:18:41 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe109801c
Parameter 2 : 0x00000000
Parameter 3 : 0xbf8b9425
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+b9425
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini033110-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini030810-01.dmp
Crash Time : 3/8/2010 12:06:51 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953492
Parameter 3 : 0xb75b2c00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153492
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini030810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini081908-01.dmp
Crash Time : 8/19/2008 6:49:46 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000002
Parameter 2 : 0x8295a240
Parameter 3 : 0x82adbc88
Parameter 4 : 0x81e213c0
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+63b5
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini081908-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
==================================================
Dump File : Mini062008-01.dmp
Crash Time : 6/20/2008 7:19:00 AM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 0x00000000
Parameter 2 : 0x805463f0
Parameter 3 : 0xb2104000
Parameter 4 : 0x00000175
Caused By Driver : hal.dll
Caused By Address : hal.dll+58d7
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062008-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================
#5
Posted 19 June 2010 - 10:28 AM
Are your USB Drivers/Chipset drivers updated?
Can you perform the following: Publish a Snapshot using Speccy
Can you perform the following: Publish a Snapshot using Speccy
My work schedule is as follows: Mon and Tues 1800 to 0600, Friday - Sunday 1800EST to 0600, and Wednesday to Thursday 1800est to 0600. So if I do not respond right away I am at work.
----------------
If I am helping you, then Please Send Me a Message!with your thread link in it. This is only if I haven't replied back to you within 24 to 48 hours.
----------------
My Main Site || My Backup Site || steam://friends/add/cryptodan Add me to your Steam Friends.
#6
Posted 19 June 2010 - 02:28 PM
I have no idea if they're updated. Here is the site created with Piriform: http://speccy.piriform.com/results/8qrknMl4Obgo7OmnhGY31yt.
#7
Posted 19 June 2010 - 02:33 PM
Here try this: Xpress 200M Drivers
My work schedule is as follows: Mon and Tues 1800 to 0600, Friday - Sunday 1800EST to 0600, and Wednesday to Thursday 1800est to 0600. So if I do not respond right away I am at work.
----------------
If I am helping you, then Please Send Me a Message!with your thread link in it. This is only if I haven't replied back to you within 24 to 48 hours.
----------------
My Main Site || My Backup Site || steam://friends/add/cryptodan Add me to your Steam Friends.
#8
Posted 20 June 2010 - 09:51 PM
I installed it. So far, so good. So now I just wait to see if I get the blue screen error again?
#9
Posted 21 June 2010 - 07:34 AM
katiedid, on Jun 21 2010, 02:51 AM, said:
I installed it. So far, so good. So now I just wait to see if I get the blue screen error again?
You got it.
My work schedule is as follows: Mon and Tues 1800 to 0600, Friday - Sunday 1800EST to 0600, and Wednesday to Thursday 1800est to 0600. So if I do not respond right away I am at work.
----------------
If I am helping you, then Please Send Me a Message!with your thread link in it. This is only if I haven't replied back to you within 24 to 48 hours.
----------------
My Main Site || My Backup Site || steam://friends/add/cryptodan Add me to your Steam Friends.
#11
Posted 22 June 2010 - 06:16 AM
Happy computing. Please be sure to keep it updated.
My work schedule is as follows: Mon and Tues 1800 to 0600, Friday - Sunday 1800EST to 0600, and Wednesday to Thursday 1800est to 0600. So if I do not respond right away I am at work.
----------------
If I am helping you, then Please Send Me a Message!with your thread link in it. This is only if I haven't replied back to you within 24 to 48 hours.
----------------
My Main Site || My Backup Site || steam://friends/add/cryptodan Add me to your Steam Friends.
Share this topic:
Page 1 of 1

Help

Back to top








