Multiple BSODs

Pink401k · Aug 9, 2010

I just bought a brand new HP Dv7tse with Windows 7 x64, and ever since day one have been getting BSOD. It says that there's a problem with my graphic's driver, which I've tried to upgrade, but that didn't help. Then, it started blaming the BSODs on a new driver I got from Motion Joy for my PS3 controller to be used on my Computer. However, since the BSODs were happening before I installed the software, I'm dubious. Any help would be greatly appreciated.

Windows 7 came pre-installed, I'm using the initial installation, and both the OS installation and computer are less than a month old.

Thanks for the help.

CarlTR6 · Aug 9, 2010

I looked at your three latest dumps. All three have the same error code of 7E - BSOD Index

This error code points to hardware or hardware related problems. All three dumps blame xusb21.sys. Since this is a Microsoft driver, it is probably not the cause. And, indeed, your Motion Joy driver is blamed, also. Here is a thread you might want to read about MijXfilt.sys - MotionJoy • Bluescreen caused by MijXfilt.sys

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSOD(2).zip\Windows7_BSOD_jcgriff2\080910-35739-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Mon Aug  9 22:46:55.972 2010 (GMT-4)
System Uptime: 1 days 11:01:10.158
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.........................
Unable to load image \SystemRoot\system32\DRIVERS\xusb21.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xusb21.sys
*** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88006463a03, fffff88003585518, fffff88003584d80}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : xusb21.sys ( xusb21+2a03 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006463a03, The address that the exception occurred at
Arg3: fffff88003585518, Exception Record Address
Arg4: fffff88003584d80, Context Record Address

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


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

FAULTING_IP: 
xusb21+2a03
fffff880`06463a03 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  fffff88003585518 -- (.exr 0xfffff88003585518)
ExceptionAddress: fffff88006463a03 (xusb21+0x0000000000002a03)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003584d80 -- (.cxr 0xfffff88003584d80)
rax=fffffa800715cde0 rbx=fffffa8004786120 rcx=0041005c0065006c
rdx=fffffa800715cde0 rsi=fffffa800715cde0 rdi=fffffa8004786120
rip=fffff88006463a03 rsp=fffff88003585750 rbp=0000000000000020
 r8=0000000000000020  r9=000000000000100a r10=0000057ff902ce78
r11=fffff88003585738 r12=0000000000000000 r13=fffffa8007ea5330
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202
xusb21+0x2a03:
fffff880`06463a03 488b01          mov     rax,qword ptr [rcx] ds:002b:0041005c`0065006c=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
 ffffffffffffffff 

FOLLOWUP_IP: 
xusb21+2a03
fffff880`06463a03 488b01          mov     rax,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa8003c5f000 to fffff88006463a03

STACK_TEXT:  
fffff880`03585750 fffffa80`03c5f000 : fffffa80`03c5f000 fffff800`02c40000 fffff800`02df087c fffffa80`04786120 : xusb21+0x2a03
fffff880`03585758 fffffa80`03c5f000 : fffff800`02c40000 fffff800`02df087c fffffa80`04786120 fffff880`06463c79 : 0xfffffa80`03c5f000
fffff880`03585760 fffff800`02c40000 : fffff800`02df087c fffffa80`04786120 fffff880`06463c79 00000000`00000020 : 0xfffffa80`03c5f000
fffff880`03585768 fffff800`02df087c : fffffa80`04786120 fffff880`06463c79 00000000`00000020 fffff880`00f3d130 : hal!$$VProc_ImageExportDirectory
fffff880`03585770 fffffa80`04057600 : fffffa80`06fd3180 fffff880`00eee22b fffffa80`0443f800 00000000`00000000 : nt!ExFreePoolWithTag+0x7cc
fffff880`03585820 fffffa80`06fd3180 : fffff880`00eee22b fffffa80`0443f800 00000000`00000000 00000008`00000018 : 0xfffffa80`04057600
fffff880`03585828 fffff880`00eee22b : fffffa80`0443f800 00000000`00000000 00000008`00000018 00000000`00000000 : 0xfffffa80`06fd3180
fffff880`03585830 fffff880`00ec4c9b : fffffa80`06fd3180 fffffa80`06fd3180 fffffa80`06fd3190 fffffa80`070ac601 : Wdf01000!FxRequestBase::CompleteSubmitted+0x177
fffff880`035858b0 fffff880`00ec4dc4 : fffffa80`04906200 00000000`00000001 00000000`00000000 00000000`00000001 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`03585920 fffff800`02ca5fd5 : 00000000`00000001 fffff880`03585a70 fffff880`01069860 fffff880`01004c03 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`03585950 fffff800`02cbdc26 : fffffa80`06f27fb3 00000000`00000000 00000000`00000000 fffffa80`06f27c10 : nt!IopUnloadSafeCompletion+0x55
fffff880`03585980 fffff880`00ee7a52 : 00000000`00000000 fffffa80`0a3b5c00 00000000`00000001 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`03585a60 fffff880`00ed813e : fffffa80`06f27c10 00000000`00000001 fffffa80`044f9100 fffffa80`06f27c10 : Wdf01000!FxRequest::CompleteInternal+0x646
fffff880`03585b10 fffff880`0645144e : fffffa80`04906290 fffffa80`04906290 fffffa80`0976e390 0000057f`f6891fd8 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa
fffff880`03585b80 fffffa80`04906290 : fffffa80`04906290 fffffa80`0976e390 0000057f`f6891fd8 fffffa80`06c70008 : MijXfilt+0x544e
fffff880`03585b88 fffffa80`04906290 : fffffa80`0976e390 0000057f`f6891fd8 fffffa80`06c70008 0000057f`fb6f9d68 : 0xfffffa80`04906290
fffff880`03585b90 fffffa80`0976e390 : 0000057f`f6891fd8 fffffa80`06c70008 0000057f`fb6f9d68 fffffa80`06c7c8d0 : 0xfffffa80`04906290
fffff880`03585b98 0000057f`f6891fd8 : fffffa80`06c70008 0000057f`fb6f9d68 fffffa80`06c7c8d0 00000000`00000000 : 0xfffffa80`0976e390
fffff880`03585ba0 fffffa80`06c70008 : 0000057f`fb6f9d68 fffffa80`06c7c8d0 00000000`00000000 00000000`00000001 : 0x57f`f6891fd8
fffff880`03585ba8 0000057f`fb6f9d68 : fffffa80`06c7c8d0 00000000`00000000 00000000`00000001 fffffa80`03ce9148 : 0xfffffa80`06c70008
fffff880`03585bb0 fffffa80`06c7c8d0 : 00000000`00000000 00000000`00000001 fffffa80`03ce9148 ffff0000`05098b9b : 0x57f`fb6f9d68
fffff880`03585bb8 00000000`00000000 : 00000000`00000001 fffffa80`03ce9148 ffff0000`05098b9b fffffa80`03ce9040 : 0xfffffa80`06c7c8d0


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  xusb21+2a03

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: xusb21

IMAGE_NAME:  xusb21.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49dcb49c

STACK_COMMAND:  .cxr 0xfffff88003584d80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_xusb21+2a03

BUCKET_ID:  X64_0x7E_xusb21+2a03

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

Your earlier dumps are also hardware or hardware related problems.

BugCheck A - BSOD Index

BugCheck 116 - BSOD Index This one is the most telling. It is a video error. We will start trouble shooting here. Read through the thread below for information on this stop error -

http://www.sevenforums.com/graphic-...ing-display-driver-ati-hd5870.html#post821652

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp2_BSOD(2).zip\Windows7_BSOD_jcgriff2\071310-20592-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[url=http://msdl.microsoft.com/download/symbols]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Tue Jul 13 13:31:59.735 2010 (GMT-4)
System Uptime: 1 days 12:47:41.906
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008530010, fffff880041abc98, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+5c98 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008530010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880041abc98, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+5c98
fffff880`041abc98 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`08525308 fffff880`050e7ef8 : 00000000`00000116 fffffa80`08530010 fffff880`041abc98 00000000`00000000 : nt!KeBugCheckEx
fffff880`08525310 fffff880`050e7c02 : fffff880`041abc98 fffffa80`08530010 fffffa80`070c3010 fffffa80`07690410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08525350 fffff880`0518ef07 : fffffa80`08530010 00000000`00000000 fffffa80`070c3010 fffffa80`07690410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`08525380 fffff880`051bcd7e : fffffa80`ffffffff 00000000`00818fc2 fffff880`085254d0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`08525460 fffff880`051a2bb1 : fffffa80`076f1000 ffffffff`feced300 00000000`00000002 fffff880`085257d8 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`085254a0 fffff880`051a5aaf : 00000000`00008328 00000000`00000000 fffffa80`074ffa40 fffff8a0`090a1010 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`085255a0 fffff880`051a41a0 : fffff8a0`090a1010 00000000`00000000 fffffa80`076f1000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`085255e0 fffff880`051a40f6 : 00000000`00000000 00000000`00000001 fffffa80`076f1000 fffff880`051a2a1e : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`08525770 fffff880`051ad642 : fffffa80`07510a80 00000000`00000001 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`085257e0 fffff880`051ad3eb : fffff8a0`090a1010 00000000`00001000 fffffa80`07510a80 fffff8a0`090a1010 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`08525830 fffff880`051acd8f : fffff8a0`090a1010 fffffa80`076f1c80 00000000`00000000 fffffa80`076f1c80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`08525890 fffff880`051a076c : fffffa80`076f1000 fffffa80`076f1000 fffffa80`076f1c80 fffffa80`076f1000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`085258d0 fffff880`0519d133 : 00000000`c0000001 00000000`00000000 00000000`00000006 fffffa80`076f1000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`08525910 fffff880`051b765d : 00000000`00000000 fffff8a0`024effd0 fffffa80`00000002 fffffa80`086046d0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`08525ae0 fffff880`051b7398 : fffff880`009ef040 fffff880`051b6d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`08525cd0 fffff880`051b6e96 : 00000000`00000000 fffffa80`076c3580 00000000`00000080 fffffa80`07690410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`08525d00 fffff800`02f62a86 : 00000000`fffffc32 fffffa80`0769b510 fffffa80`03cd2b30 fffffa80`0769b510 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`08525d40 fffff800`02c9bb06 : fffff880`009ea180 fffffa80`0769b510 fffff880`009f50c0 fffff880`01458bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`08525d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+5c98
fffff880`041abc98 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+5c98

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b59a32a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp2_BSOD(2).zip\Windows7_BSOD_jcgriff2\062610-18283-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[url=http://msdl.microsoft.com/download/symbols]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50
Debug session time: Sat Jun 26 16:19:00.407 2010 (GMT-4)
System Uptime: 0 days 4:37:03.578
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {88, 2, 1, fffff80002c9f812}

Unable to load image \SystemRoot\system32\DRIVERS\gt72ubus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gt72ubus.sys
*** ERROR: Module load completed but symbols could not be loaded for gt72ubus.sys
Probably caused by : gt72ubus.sys ( gt72ubus+ab60 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000088, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c9f812, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef60e0
 0000000000000088 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeInsertQueueApc+42
fffff800`02c9f812 f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff800042746f0 -- (.trap 0xfffff800042746f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80040c08a8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c9f812 rsp=fffff80004274880 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002c4e000
r11=fffff800042749b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeInsertQueueApc+0x42:
fffff800`02c9f812 f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0 ds:dbb8:00000000`00000088=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cbf469 to fffff80002cbff00

STACK_TEXT:  
fffff800`042745a8 fffff800`02cbf469 : 00000000`0000000a 00000000`00000088 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`042745b0 fffff800`02cbe0e0 : fffffa80`04806010 00000000`00000000 fffff800`04274888 fffffa80`040c0830 : nt!KiBugCheckDispatch+0x69
fffff800`042746f0 fffff800`02c9f812 : fffffa80`0496c301 00000000`00000000 fffffa80`0496c010 fffffa80`0721f6a0 : nt!KiPageFault+0x260
fffff800`04274880 fffff800`02cc2d4b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000002 : nt!KeInsertQueueApc+0x42
fffff800`042748e0 fffff880`07422b60 : fffffa80`04358760 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff800`042749c0 fffffa80`04358760 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0721ea02 : gt72ubus+0xab60
fffff800`042749c8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0721ea02 00000000`00000000 : 0xfffffa80`04358760


STACK_COMMAND:  kb

FOLLOWUP_IP: 
gt72ubus+ab60
fffff880`07422b60 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  gt72ubus+ab60

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: gt72ubus

IMAGE_NAME:  gt72ubus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47ac3658

FAILURE_BUCKET_ID:  X64_0xA_gt72ubus+ab60

BUCKET_ID:  X64_0xA_gt72ubus+ab60

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

Pink401k · Aug 9, 2010

Thanks very much for the prompt reply! I'll check all these out, and hopefully get this problem taken care of!

CarlTR6 · Aug 10, 2010

You are very welcome; but I have some further suggestions.

You said this is a brand new system; but I find some obsolete drivers. Win 7 does not like older drivers and they can cause crashes.

000.fcl Fri Sep 26 09:11:22 2008
Gt51Ip.sys Mon Feb 18 10:14:48 2008
gt72ubus.sys Fri Feb 08 06:00:40 2008
gtptser.sys Fri Mar 30 07:38:14 2007
swmsflt.sys Fri Jan 11 14:01:29 2008

Update these drivers ASAP. gt72ubus.sys was pointed to in one of the dumps. If there are no updates available, uninstall the software and/or hardware these drivers are associated with.

If you need help finding drivers, let us know.

How to find drivers:

[FONT=&quot]- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.[/FONT]
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Pink401k · Aug 19, 2010

Thanks again for the help. I got rid of some of the software that went with the old drivers. The gt72ubus.sys seems to go with my wireless adapter maybe? I'm not sure, but the link in the driver reference page says I need a serial number. Any idea on where that might be located?

EDIT: I'm beginning to think there may be a problem with my memory. I got This error the other day, which can point to memory, and the video driver error said there could be a problem with my memory as well. I'm going to try to get Memtest86+ to run tonight and see if there might be a problem there too...

CarlTR6 · Aug 19, 2010

Pink401k said:
Thanks again for the help. I got rid of some of the software that went with the old drivers. The gt72ubus.sys seems to go with my wireless adapter maybe? I'm not sure, but the link in the driver reference page says I need a serial number. Any idea on where that might be located?

The serial number should be on the adapter card and the box - if you still have the box.

gt72ubus.sys - Globetrotter 3g or Option Icon 225 USB data stick from Orange http://www.option.com/en/support/software-download/

EDIT: I'm beginning to think there may be a problem with my memory. I got This error the other day, which can point to memory, and the video driver error said there could be a problem with my memory as well. I'm going to try to get Memtest86+ to run tonight and see if there might be a problem there too...

Let us know the results of Memtest. Any errors will show up in red. Page fault can be caused by faulty RAM; but it can be caused by other things, too.

Multiple BSODs

Pink401k

New member

My Computer

CarlTR6

Antique Senior Member

My Computer

Pink401k

New member

My Computer

CarlTR6

Antique Senior Member

My Computer

Pink401k

New member

My Computer

CarlTR6

Antique Senior Member

My Computer