Win 7 Ultimate 32bit Freezing - Help!

[kaaskop]

As been said. Remove all harddrives exept the one youre doing the installation on. All other cards and work with 1 ram stick only. If it still happens change the ram stick and so on. The only way.

Add 1 item at time untill you find the culprit.

 

[gasboi]

Fudzy, you manage to fix ?

 

[Fudzy]

Fudzy, you manage to fix ?

Yes and no, my supplier replaced the motherboard. It isn't freezing as much but it is still freezing. I'm trying to look into reading the minidump but for some reason Windows 7 has stopped generating them since I opened the last one.

The motherboard is another P55, this one made by Gigabyte though.

 

[ponder]

It might be but even with linux a hardware fault that affects windows may not affect linux right?

Sorry, I meant software

 

[Fudzy]

Bump any updates?

 

[bekdik]

does it freeze if you boot in safe mode?

have you tried disabling all startups with msconfig?

 

[Fudzy]

Any minidump gurus here?

I have queried the minidump and I need help deciphering it.

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


Loading Dump File [C:\crash\110609-16848-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c38000 PsLoadedModuleList = 0x82d80810
Debug session time: Fri Nov  6 17:01:24.190 2009 (GMT+2)
System Uptime: 0 days 21:38:52.000
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {a6e5b2fb, 2, 0, 82d5ea90}

Probably caused by : hardware ( usbhub!UsbhAllocWorkItem+80 )

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: a6e5b2fb, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82d5ea90, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82da0718
Unable to read MiSystemVaType memory at 82d80160
 a6e5b2fb 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDoubleFaultStack+2a90
82d5ea90 8b831b922820    mov     eax,dword ptr [ebx+2028921Bh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

MISALIGNED_IP: 
nt!KiDoubleFaultStack+2a90
82d5ea90 8b831b922820    mov     eax,dword ptr [ebx+2028921Bh]

LAST_CONTROL_TRANSFER:  from 921b8738 to 82d5ea90

STACK_TEXT:  
82d5ea74 921b8738 86bd2028 921e7000 86bd2bf4 nt!KiDoubleFaultStack+0x2a90
82d5ea8c 921b838b 86bd2028 921b8524 86bd2838 usbhub!UsbhAllocWorkItem+0x80
82d5eab4 921b84ff 86bd2028 00000001 921b8524 usbhub!UsbhQueueWorkItem+0x69
82d5ead8 921b81d2 86bd2b5c 86bd2028 00000000 usbhub!UsbhHubSSH_Timer+0x49
82d5eb18 82cc1831 86bd2028 86bd2028 82d5ebb8 usbhub!UsbhDmTimer+0x10b
82d5eb38 82ca204d 82d9e6e0 02d9e698 01fc8a5b nt!IopTimerDispatch+0x49
82d5eb7c 82ca1ff1 82d61d20 82d5eca8 00000003 nt!KiProcessTimerDpcTable+0x50
82d5ec68 82ca1eae 82d61d20 82d5eca8 00000000 nt!KiProcessExpiredTimerList+0x101
82d5ecdc 82ca020e 004c3a19 87b3e858 82d6b280 nt!KiTimerExpiration+0x25c
82d5ed20 82ca0038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82d5ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhAllocWorkItem+80
921b8738 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  usbhub!UsbhAllocWorkItem+80

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

Any suggestions?