Windows 7 Blue Screen Problem (Win764Bit)

[cblemmy]

Hey there,
I've been getting blue screen errors at unpredictable times since I downloaded Catalyst 10.2. What's even more interesting is that before I got Catalyst 10.2, I was having grey (or grey screen with stripes and an awful sound) screen errors (both on 10.1 and 9.12). I did do clean installs of each new driver so I'm not sure exactly what happened. Anyways, here are my system specs:
HIS Radeon 5770
80 gb dane-elec SSD
3.0 ghz amd quad core (phenom II x4 945 Deneb)
4 GB of g-skill ddr2 sdram
Biostar TA790GXE amd motherboard
Corsair 400w psu w/ 12v rail

and from reading some of the other messages it looks like I should attach the minidump files. Here are the last 4...
thank you in advance for your help

 

[Saltgrass]

Did you check the requirement for a power supply before you got the video card? From what I can see, it needs at least 450W.

Newegg.com - HIS H577FM1GD Radeon HD 5770 1GB 128-bit GDDR5 PCI Express 2.0 x16 HDCP Ready CrossFireX Support Video Card - Desktop Graphics / Video Cards

 

[cblemmy]

That's what I thought it might be, but it seemed to work fine until mid-january. Is this a psu related problem? every time it happens it's the "driver not less or equal" error

 

[Saltgrass]

I do not know for sure it is the power supply, but if you are running lower than required power levels, it might be causing other things to go wrong.

I would first suggest you upgrade the power supply and then see what happens. It says a minimum is 450 Watts. I normally run a 550 to 600 W with one GTX 260. So I would go at least that far.

 

[Trouble]

All four dumps are virtually identical pointing to an issue with athrxusb.sys a driver apparently associated with and Atheros USB network adapter, located in C:\Windows\System32\Drivers\athrxusb.sys

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

Loading Dump File [C:\Users\WhoEver\Desktop\New folder\021910-16052-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50
Debug session time: Fri Feb 19 18:12:26.567 2010 (GMT-6)
System Uptime: 0 days 2:10:37.611
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8005d0ea8e, 2, 0, fffff88003a850e1}
Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+760e1 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000008005d0ea8e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003a850e1, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f010e0
0000008005d0ea8e
CURRENT_IRQL: 2
FAULTING_IP:
athrxusb+760e1
fffff880`03a850e1 8b402c mov eax,dword ptr [rax+2Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: DOW2.exe
TRAP_FRAME: fffff880009b06f0 -- (.trap 0xfffff880009b06f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000008005d0ea62 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa8005cf1030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003a850e1 rsp=fffff880009b0880 rbp=0000000000000000
r8=fffffa800599c290 r9=0000000000000000 r10=fffff88002fd3e20
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
athrxusb+0x760e1:
fffff880`03a850e1 8b402c mov eax,dword ptr [rax+2Ch] ds:00000080`05d0ea8e=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cca469 to fffff80002ccaf00
STACK_TEXT:
fffff880`009b05a8 fffff800`02cca469 : 00000000`0000000a 00000080`05d0ea8e 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b05b0 fffff800`02cc90e0 : fffffa80`00000000 fffffa80`04bcbcc0 fffffa80`05b519a0 fffff800`02dfe2dd : nt!KiBugCheckDispatch+0x69
fffff880`009b06f0 fffff880`03a850e1 : fffff880`01559110 fffffa80`03de6050 00000000`00000286 fffff880`03a206b0 : nt!KiPageFault+0x260
fffff880`009b0880 fffff880`01559110 : fffffa80`03de6050 00000000`00000286 fffff880`03a206b0 00000000`00000000 : athrxusb+0x760e1
fffff880`009b0888 fffffa80`03de6050 : 00000000`00000286 fffff880`03a206b0 00000000`00000000 fffffa80`03de6050 : ndis!WPP_GLOBAL_Control
fffff880`009b0890 00000000`00000286 : fffff880`03a206b0 00000000`00000000 fffffa80`03de6050 00000000`00000000 : 0xfffffa80`03de6050
fffff880`009b0898 fffff880`03a206b0 : 00000000`00000000 fffffa80`03de6050 00000000`00000000 fffff880`03a4bca1 : 0x286
fffff880`009b08a0 00000000`00000000 : fffffa80`03de6050 00000000`00000000 fffff880`03a4bca1 00000001`060af810 : athrxusb+0x116b0

STACK_COMMAND: kb
FOLLOWUP_IP:
athrxusb+760e1
fffff880`03a850e1 8b402c mov eax,dword ptr [rax+2Ch]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: athrxusb+760e1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrxusb
IMAGE_NAME: athrxusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 488f1151
FAILURE_BUCKET_ID: X64_0xD1_athrxusb+760e1
BUCKET_ID: X64_0xD1_athrxusb+760e1
Followup: MachineOwner
---------
3: kd> lmvm athrxusb
start end module name
fffff880`03a0f000 fffff880`03b1c000 athrxusb T (no symbols)
Loaded symbol image file: athrxusb.sys
Image path: \SystemRoot\system32\DRIVERS\athrxusb.sys
Image name: athrxusb.sys
Timestamp: Tue Jul 29 07:47:13 2008 (488F1151)
CheckSum: 00107E18
ImageSize: 0010D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[cblemmy]

Oh awesome! Alright this makes sense... what should I do with this file? Delete it?

 

[Trouble]

Not sure, are you using or have you used in the past any such device. I always recommend renaming a file rather that deleting it so you can try renaming it to something like athrxusb.old or whatever you like just make note of the original name so you can rename it properly if that doesn't prove to be the actual cause of your problem

 

[cblemmy]

Hey, that worked out well! It was my wireless card file and the wireless doesn't work but I don't care cause I prefer ethernet anyways. Everything was going completely fine until today I got one more bluescreen error. here's the file:

And I also got a 650w psu hopefully that'll change things? I dunno.

 

[Trouble]

This one is different seems to be pointing at dxgmms1.sys, I would assume something relating to directX and a graphics driver, but could also be related to a sound card driver try googling (dxgmms1.sys windows 7) and see what you find

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

Loading Dump File [C:\Users\JohnSmith\Desktop\New folder\022210-15428-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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Mon Feb 22 11:12:46.915 2010 (GMT-6)
System Uptime: 0 days 0:33:59.959
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004f7c822, fffff880025906d8, fffff8800258ff30}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+d8e )
Followup: MachineOwner
---------
0: 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: fffff88004f7c822, The address that the exception occurred at
Arg3: fffff880025906d8, Exception Record Address
Arg4: fffff8800258ff30, 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: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+d8e
fffff880`04f7c822 8902            mov     dword ptr [rdx],eax
EXCEPTION_RECORD:  fffff880025906d8 -- (.exr 0xfffff880025906d8)
ExceptionAddress: fffff88004f7c822 (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x0000000000000d8e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000102
Attempt to write to address 0000000000000102
CONTEXT:  fffff8800258ff30 -- (.cxr 0xfffff8800258ff30)
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa80059e7670
rdx=0000000000000102 rsi=fffff8a008af9010 rdi=fffffa80059c9000
rip=fffff88004f7c822 rsp=fffff88002590910 rbp=fffffa8003b55000
 r8=fffffa8003ba8850  r9=fffff88002590901 r10=0000000000000000
r11=fffffa8005880410 r12=0000000000000000 r13=0000000000000000
r14=fffffa8003bdb7f0 r15=00000000000001ba
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd8e:
fffff880`04f7c822 8902            mov     dword ptr [rdx],eax ds:002b:00000000`00000102=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
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:  0000000000000001
EXCEPTION_PARAMETER2:  0000000000000102
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf0e0
 0000000000000102 
FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+d8e
fffff880`04f7c822 8902            mov     dword ptr [rdx],eax
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from fffff88004f9665d to fffff88004f7c822
STACK_TEXT:  
fffff880`02590910 fffff880`04f9665d : 00000000`00000000 fffff8a0`028c9600 fffffa80`00000000 fffffa80`03bdb7f0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd8e
fffff880`02590ae0 fffff880`04f96398 : fffff800`00b96080 fffff880`04f95d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02590cd0 fffff880`04f95e96 : 00000000`00000000 fffffa80`03c4dd50 00000000`00000080 fffffa80`05880410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02590d00 fffff800`02f2c166 : 00000000`019dc67f fffffa80`0586db60 fffffa80`039d3040 fffffa80`0586db60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02590d40 fffff800`02c67486 : fffff800`02e01e80 fffffa80`0586db60 fffff800`02e0fc40 fffff880`01264534 : nt!PspSystemThreadStartup+0x5a
fffff880`02590d80 00000000`00000000 : fffff880`02591000 fffff880`0258b000 fffff880`02590690 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+d8e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
STACK_COMMAND:  .cxr 0xfffff8800258ff30 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+d8e
BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+d8e
Followup: MachineOwner
---------
0: kd> lmvm dxgmms1
start             end                 module name
fffff880`04f5e000 fffff880`04fa4000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symbols\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Mon Jul 13 18:38:32 2009 (4A5BC578)
    CheckSum:         0004AD44
    ImageSize:        00046000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[cblemmy]

I did some reading up about it, people claim it only really happens when the video card is overclocked and not cooled enough. I'm pretty sure renaming or messing with it would cause some problems. Thanks for all your help, the Bsod's have cut down 90%!