Desktop freezing...

Hi, having problems with my desktop freezing up. Lately it has been happening when trying to transfer files from my laptop to my desktop, networked. I transferred 1 folder but the second one I attempted, which was a bigger folder forced my desktop to crash and need a hard reset, no blue screen. Also, I was getting the same problem when I was trying to stream movies from Vuze to my TV, via Xbox. When I pressed the play button on the xbox my desktop use to just freeze, only way I managed to fix this was by reinstalling the graphics card drivers, every time.

Wonder if it is a dodgy driver, bad hardware on my behalf, or possibly incompatibility issues? Running Windows 7 64bit. Any further information, hardware wise please ask

Thanks.

 

A quick look over suggests it might be an old network/motherboard driver clashing with recently updated Windows files but with Vuze and Xbox in the mix, it could easily be the firewall or another security program; are you running ZoneAlarm?

Can you get some Event viewer logs uploaded, preferably filtered to within an hour either side of the reboot(s)?

A full hardware inventory and networked device list would be helpful.

 

Hey mate, here are the files you requested..

Thanks,

Luke

 

The driver detected a controller error on \Device\Harddisk3\DR5. <--- this will need investigating, you do not want a drive to die without having at least 1 working and tested copy of any valued data.

The below will need investigating too, your logs are full of this!

Code:

Log Name:      System
Source:        [B]amdkmdag[/B]
Date:          7/8/2011 17:32:28
[B]Event ID:      62464[/B]
Task Category: [B]DVD_OV[/B]
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Lukas-PC
Description:
UVD Information
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="amdkmdag" />
    <EventID Qualifiers="16384">62464</EventID>
    <Level>4</Level>
    <Task>61</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-07-08T16:32:28.987213400Z" />
    <EventRecordID>19319</EventRecordID>
    <Channel>System</Channel>
    <Computer>Lukas-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>00006000010000003D00000000F40040000000000000000000000000000000000000000000000000FFFFFFFF0004065800803E001800000000000000030000000B00000003000000030000000B00000003000000030000000B000000030000000300000000000000000000000300000000000000000000000FFF7F0000803E003C00000000000000</Binary>
  </EventData>
</Event>

I couldn't see any obvious reason for a crash or freeze (except an overdose of log-writing), sometimes it seems to happen with a new install after a lot of new software has been installed or there's an update waiting to reboot.

Usually best to keep the installs and maintenance simple, don't change too many things at once.

Learn to check your firewall logs to look for strange or excessive activity too

 

What ati driver set you running? I've been finding issues with the 10.5 and 10.6. Also, what motherboard ye running?

 

Hey, I am on a Asus m2v link - obviously not the greatest board in the world

Also my driver version is in the attachment.

Cheers for the help Satrow, sorry for whatever you think I did sir, please note, all the help so far from yourself was greatly appreciated Contact me back if you have a change of mine,

Thanks,

Luke

 

Attached bsod.

 

This points to an issue related to the graphics drivers:

Code:

Could not read faulting driver name
Probably caused by : [B]dxgmms1.sys[/B] ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88007a66768, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880049aa0b9, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb90e0
 fffff88007a66768 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`049aa0b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007f420a0 -- (.trap 0xfffff88007f420a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000ec rbx=0000000000000000 rcx=0000000000000076
rdx=fffff88007a66000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880049aa0b9 rsp=fffff88007f42230 rbp=fffff88007f42a40
 r8=fffffa80050d1018  r9=0000000000000001 r10=fffff8a003904a70
r11=0000000040001d80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169:
fffff880`049aa0b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8] ds:4000:fffff880`07a66768=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d02024 to fffff80002c81700

STACK_TEXT:  
fffff880`07f41f38 fffff800`02d02024 : 00000000`00000050 fffff880`07a66768 00000000`00000000 fffff880`07f420a0 : nt!KeBugCheckEx
fffff880`07f41f40 fffff800`02c7f7ee : 00000000`00000000 00000000`00000000 fffff900`c08b0f00 fffff960`002054cb : nt! ?? ::FNODOBFM::`string'+0x427f7
fffff880`07f420a0 fffff880`049aa0b9 : 00000000`00000000 fffff880`07f42db0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07f42230 fffff880`049903e7 : fffffa80`069ca201 fffffa80`04f22c90 00000000`03f50018 00000000`00000022 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169
fffff880`07f42320 fffff880`04908f12 : 00000000`035de228 00000000`00000200 fffff880`07f42a40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`07f42370 fffff880`049086d7 : fffff8a0`00000001 fffff8a0`07b85520 fffff880`07f429f0 fffff880`049a9d2c : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`07f42980 fffff960`0025df8e : 00000000`035de110 fffff880`07f42ca0 fffff800`000007dc fffff800`00000000 : dxgkrnl!DxgkRender+0x3e7
fffff880`07f42bf0 fffff800`02c80953 : fffffa80`05070060 fffff880`07f42ca0 fffff960`001aa20c 00000000`00000020 : win32k!NtGdiDdDDIRender+0x12
fffff880`07f42c20 00000000`7518143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`035de0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7518143a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`049aa0b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

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

Uninstall your current graphics driver using DriverSweeper then install the latest version.

Also create a MemTest86+ CD and boot from it to test the memory, allow 7+ runs.

 

Satrow, followed your instructions thus far, removed drivers with DriverSweeper and installed the newest ones from the company's website. Currently doing the memtest you advised, will post back the results soon.

Cheers,

Luke

 

Memtest ran for almost 3 hours, no errors, passed 7 runs

Thanks,

Luke

 

Keep using it until you get another BSOD.

If it fails with the same BSOD, do the DriverSweeper thing and install earlier drivers for the graphics, run OCCT to stress test.

 

Hey, I am unsure on how to use OCCT to performe a stress test, yes I have the software but as far as using it I have no clue

Thanks,

Luke

 

You could also test with FurMark.

 

Hi, I opened OCCT and checked automatic and then hit "on" within 1 minute of it on I got a blue screen, attached the dump file

Thanks,

Luke

 

It looks like it's caused by a bug in the CPU second core:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, fffff880009e6180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e6180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`031394c8 fffff800`02c80473 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e6180 : nt!KeBugCheckEx
fffff880`031394d0 fffff800`02cdade7 : 00000000`00000000 fffff800`00000001 00000000`00026160 fffff800`02e0376d : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`03139560 fffff800`02c23895 : fffff800`02c48460 fffff880`03139710 fffff800`02c48460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03139660 fffff800`02ccebf3 : 00000000`72f02430 fffff800`02e4ce80 00000000`000067fc 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`03139690 fffff800`02d07e3b : fffff880`00000000 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03139820 fffff800`02ce063c : 00000000`00000000 00000000`0000493b 7f900000`0b946d00 7fa00000`875a5d00 : nt!KxFlushEntireTb+0x93
fffff880`03139860 fffff800`02ce6790 : 00000000`0000493b 00000000`00000001 00000000`00000000 00000000`0000493a : nt!KeFlushMultipleRangeTb+0x28c
fffff880`03139930 fffff800`02d54b6e : fffff800`02e5eb40 fffff880`00000001 00000000`00000001 fffff880`03139bb0 : nt!MiAgeWorkingSet+0x651
fffff880`03139ae0 fffff800`02ce6ef2 : 00000000`00004bef 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x49696
fffff880`03139b80 fffff800`02ce7183 : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`02f75bc6 : fffffa80`039eab60 00000000`00000080 fffffa80`039cd040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`02cb0bc6 : fffff800`02e4ce80 fffffa80`039eab60 fffff800`02e5ac40 2c24a434`0c8f382c : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

There maybe a driver that's causing it though:

Rollback to standard W7 drivers and test again (disable any non-vital drivers that can't be rolled back).

If all is good, install SP1 and test again.

Still good? Install 'correct' drivers singly, testing between each update.


EDIT: A BIOS update may also provide a fix.

 

Ok so like I said when I messaged you, I don't know how to solve ths BIOS update and I have no idea which drivers to roll back. Tried to contact you but no luck

Thanks,

Luke

 

Asus download page.

 

As you can see from that download page there is no Windows 7 in the OS drop down menu

 

BIOS is indepentent of OS, whether it's Windows, Unix or w/e.

 

Ok well I have never done a BIOS update before heh. The BIOS utilities from the site don't seem to run so I am at a loss at how to BIOS update, was told have to be careful with it so not exactly going to just jump in without caution.

 

Is your CPU on this list? If so, which BIOS version is needed to support it and which version do you have?

 

This is my CPU, I think it matches up - link

See attachment...

Will post my current bios in a few, need reboot...

Thanks, Luke

EDIT :

AMIBIOS
Version : 1706
Build Date : 04/30/07 <-- US format lol

 

Well, I THINK there is my processor I linked, I downloaded everest and took a screenshot of what that said about the CPU...

See attachment...

 

So you need the latest BIOS.

From the Knowledge page, it looks like there are at least 2 methods of updating the BIOS.

 

Ok what might look obvious and easy to yourself I am lost and have NO clue at all on how this is done or even where to start so within so real help and step by step instructions I am not going to be able to do this

 

It doesn't look obvious or easy to me either, maybe you should checkout Asus' forums?

 

Will give them a try in the morning. Any other ways? If not were all my mobo drivers ok when you checked?