Weird problem with BSODs whilst running Windows 7 Ultimate x64

TeaganP

TeaganP

TeaganP

Associate
Joined
20 Jan 2010
Posts
72
Hi there folks...

I've been having some very strange problems recently with my Windows 7 Ultimate x64 machine. I keep getting these Blue Screens of Death all the time and my system isn't very stable it seems. I'm not sure what's going on, not so long ago I purchased the Windows 7 Ultimate 64 bit OEM version from Overclockers for my PC. I've been having these problems when I do a fresh install. I used to run Windows XP Professional (SP3) on this machine before and it was fine, used to run really well but my XP installation messed up recently so I've decided now not to bother with XP anymore and move onto Windows 7.

I'm just in the process of installing it again and I'm being very careful what I'm putting on this time. I have downloaded the correct drivers for my motherboard (ASUS P5Q Deluxe) from the Asus site and I have one a time installed them. I'm not doing anything wrong as far as I know and I have installed systems many times before but on this occasion I just get BSOD every so often.

I have been looking into trying to find out more about Blue Screens of Death and I have been working out how to open a minidump file using a debug program provided by Microsoft. I am about to install this program again so I can look at the most recent minidump file and see what I can learn from it. I have also discovered with Windows 7 that you can use the program built into Windows called Verifier to test your drivers etc.. I have tried using this and it has caused it to blue screen on purpose by stressing out the drivers to see whether it will crash or not. I also understand that when using Verifier you have to boot the machine back up in Safe Mode so you can cancel the settings to allow your machine to run normally again. I have tried all this, I wanted to come here really and post up some of the minidump files so that somebody here might be able to help understand what's causing the problem.

I was installing my machine again over last night and I kept getting a BSOD with the same message all the time which said SYSTEM_SERVICE_EXCEPTION 3B. I did try googling this and on one page for Microsort support on this error it said there was a hotfix to solve this problem. I downloaded the hotfix and tried to install it but it said that "this machine cannot install this update". I was a bit annoyed that it didn't work. I also found various other pages saying different things about this BSOD error.

I need to start again now with this really, I've just made a fresh clean install of Windows 7 Ultimate x64 and it's just updating from Microsoft at the moment. I've put barely any programs on it. I'm sure at some point it will Blue Screen again. At that point I will try and provide more information as to what's happening here.

I do need some help really with all this, it's starting to get me down a bit and I've been trying my best to make my machine work but it's being a pig.

As far as my machine spec is concerned this is what I'm running:

CPU = Intel Core 2 Quad Q9550 @ 2.83Ghz
COOLER = Coolermaster V8
RAM = Corsair Dominator 4GB (2 x 2GB DDR2 1066Mhz)
MOBO = Asus P5Q Deluxe - Bios Version 2301
STORAGE = System drive, WD Blue SATA 500GB
STORAGE 2 = RAID 10, WD Green Caviar SATA 1TB x 4
PSU = Coolermaster ATX 1000Watt
GRAPHICS = ATI Radeon HD 4870 x 2 in Crossfire mode
TV CARD = Compro T750
SOUNDCARD = M-Audio Delta AP 192
CASE = Coolermaster CM Stacker 832
OS = Windows 7 Ultimate x64

I was thinking that there might have been some sort of problem with my System hard drive (WD Blue 500GB) so I plugged it into another machine today and I tested it for errors using HD Tune but it didn't seem to have any problems really. I also tried before I installed Windows 7 again, formatting the entire machine in NTFS very slowly to make sure it was fully wiped before I installed Windows 7 again. I don't think there's anything wrong with the hard drive I'm using. As far as my machine goes there's nothing really wrong with the hardware, everything is plugged in correctly and it seems to be working as it should. It seems to be more of a software problem I'm having. I've also tested the memory in my machine using MemTest and it passed fine, I don't think I have faulty memory as far as I know, it did a couple of passes in MemTest and it was OK.

Not sure what's going on really, I'm trying to be very careful with using it at the moment and I'm sure at some point it will Blue Screen again.

Any help I can get with this will be VERY appreciated.
 
Did the ASUS P5Q Deluxe have heat issues with heatsinks with crossfire and SLI on the mobo? Have you tried with one GPU?

From what i have used with this mobo in the past its needs loads of cooling with crossfire and SLI. Especially around the CPU as the stock cooler would cool the heatsinks.
 
Last edited:
And If your overclocked knock it back to default settings and try a reinstall. OC'ing and installing windows can cause some very strange errors
 
TWiNKLeT0Es said:
Did the ASUS P5Q Deluxe have heat issues with heatsinks with crossfire and SLI on the mobo? Have you tried with one GPU?

From what i have used with this mobo in the past its needs loads of cooling with crossfire and SLI. Especially around the CPU as the stock cooler would cool the heatsinks.
Click to expand...

Well the point is that when I was running it with Windows XP Pro it was fine, I had it running for about 2 years and had no heat issue problems. Of course I could always try running it on one card just to see. I've got some good cooling in it, I've not actually installed any extra fans in the case (CM Stacker 832). I've got the fan at the front for the hard drive cage, the one at the back. There's the CPU Cooler which is the Coolermaster V8 cooler, this is always set to maximum. I always have my Bios settings set to turbo mode for both the case and CPU fans. I have also a cooler on my RAM modules, infact it was one that came with the Corsair Dominator but been having a slight problem with the fan bearings on that so I've ordered an upgrade and bought the slightly better Corsair Dominator GT fan cooler instead to replace the earlier one. There's the 2 fans systems on the Radeon HD 4870s that I've got and they're usually set at manual setting of 55%. The temps for the cards are usually around 50 or so degrees when I look.

I always have this option that in my CM Stacker 832 case (which I bought from Overclockers, and is a good case) that I could install more fans like on the door system that closes over the motherboard, there's 3 spare houses for some more fans. I could always take some pictures if you want me to show you more about it to give you a visual.
 
BigBoy said:
And If your overclocked knock it back to default settings and try a reinstall. OC'ing and installing windows can cause some very strange errors
Click to expand...

Yes good point, but I don't overclock. I'm not really into that I just set everything to auto usually. I just run it at the speed it normally runs at. My bios settings are all quite normal really. At the moment it seems to be running alright, last night when I'd installed the graphics driver it went a bit weird and I had to hard reset the machine because the screen was flashing off and on for a bit and then went blank so once I'd hard reset it was fine and came back on and has been fine since, maybe it was a bit hot. I was just turning the fans up a bit on the cards and the temps were high because it was a clean install. I've got them running at 55% now. The thing with my Radeon HD 4870 cards is that they're the overclocked ones the XXX ones and they're both exactly the same, the exact same models.
 
Interesting, just got a blue screen just before. Was trying to do an auto tune with the graphics cards and it came up saying... MEMORY_MANAGEMENT 1A

Any ideas???
 
also do you have all of the latest drivers from manufactureres website?

nb sorry about the multiple posts, at work, no javascript to make edit button work
 
HyperSonic said:
run memtest86 and chkdsk to eliminate memory problems as it sounds like your getting different errors
Click to expand...

Yes I have already run MemTest86 and it said it was fine. I don't think there's anything wrong with my RAM and I've got a cooler on it also so surely it can't be overheating.

I have already run chkdsk and it seemed fine, it rebooted and came on and did the disk check and said there was no problems.
 
Last edited:
HyperSonic said:
also do you have all of the latest drivers from manufactureres website?

nb sorry about the multiple posts, at work, no javascript to make edit button work
Click to expand...

Yes I do have all the drivers, I've been through the drivers that are listed on Asus for my board http://uk.asus.com/Motherboards/Intel_Socket_775/P5Q_Deluxe/#download and I've used the ones for Windows 7 64 bit. There's not really much more I can install from there.

The graphics driver is on, my soundcard driver is on, also the TV card driver is installed.
 
I've opened up some dump files and this is what it said...

This is from yesterday 23rd of October 2012 at 20:52:

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


Loading Dump File [C:\Dump Files\102312-33493-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02ea2e90
Debug session time: Tue Oct 23 20:45:17.957 2012 (UTC + 1:00)
System Uptime: 0 days 0:24:06.237
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

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

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+3533653262383061
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: TrustedInstall

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff88003322978 -- (.exr 0xfffff88003322978)
ExceptionAddress: fffff80002ce777f (nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x000000000000004f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88003322a20 -- (.trap 0xfffff88003322a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88003322d40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ce777f rsp=fffff88003322bb0 rbp=0000000000000000
r8=fffff88003322d40 r9=fffff88003322c50 r10=fffff88004c2c000
r11=fffff8800a1d7b20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f:
fffff800`02ce777f 488713 xchg rdx,qword ptr [rbx] ds:e040:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cd4ffe to fffff80002cdd610

STACK_TEXT:
fffff880`03321a58 fffff800`02cd4ffe : 00000000`00000000 00000000`00000000 fffff880`033221d0 fffff800`02d092a0 : nt!KeBugCheck
fffff880`03321a60 fffff800`02d08f6d : fffff800`02ee4a10 fffff800`02e20c78 fffff800`02c5d000 fffff880`03322978 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03321a90 fffff800`02d07d45 : fffff800`02e24028 fffff880`03321b08 fffff880`03322978 fffff800`02c5d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03321ac0 fffff800`02d18dc1 : fffff880`03322978 fffff880`033221d0 fffff880`00000000 fffff880`00000004 : nt!RtlDispatchException+0x415
fffff880`033221a0 fffff800`02cdccc2 : fffff880`03322978 fffbfa80`06b40b10 fffff880`03322a20 fffff880`009f3180 : nt!KiDispatchException+0x135
fffff880`03322840 fffff800`02cdb5ca : fffffa80`03c941a0 fffffa80`03c941a0 fffffa80`04df7278 fffff880`0130ef64 : nt!KiExceptionDispatch+0xc2
fffff880`03322a20 fffff800`02ce777f : fffffa80`04b0c5c8 00000000`00000004 fffffa80`04b0c5c8 00000000`00000004 : nt!KiGeneralProtectionFault+0x10a
fffff880`03322bb0 fffff880`04c586df : 00000000`00000000 fffbfa80`06b40b10 fffff880`03322d40 fffffa80`0657658e : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f
fffff880`03322c00 00000000`00000000 : fffbfa80`06b40b10 fffff880`03322d40 fffffa80`0657658e fffff880`03322cd0 : atikmdag+0x2c6df


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+2c6df
fffff880`04c586df ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: atikmdag+2c6df

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ff3d19d

FAILURE_BUCKET_ID: X64_0x1E_0_atikmdag+2c6df

BUCKET_ID: X64_0x1E_0_atikmdag+2c6df

Followup: MachineOwner
---------
Click to expand...
 
Also then this happened this morning on the 24th of October 2012 at 7:40

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


Loading Dump File [C:\Dump Files\102412-42510-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eab670
Debug session time: Wed Oct 24 07:36:18.949 2012 (UTC + 1:00)
System Uptime: 0 days 0:00:43.229
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ca0b06, fffff88007cb9e40, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeSignalGateBoostPriority+56 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ca0b06, Address of the instruction which caused the bugcheck
Arg3: fffff88007cb9e40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP:
nt!KeSignalGateBoostPriority+56
fffff800`02ca0b06 488b36 mov rsi,qword ptr [rsi]

CONTEXT: fffff88007cb9e40 -- (.cxr 0xfffff88007cb9e40)
rax=0000000000000002 rbx=fffff880031d3180 rcx=fffffa8003c5e160
rdx=fffbfa8006e21168 rsi=fffbfa8006e21168 rdi=fffffa8003c5e160
rip=fffff80002ca0b06 rsp=fffff88007cba820 rbp=fffffa8003c5e168
r8=0000000000000003 r9=fffffa8003c5e2b0 r10=fffffa8003c5e148
r11=fffffa8003c9e2da r12=fffffa8003c5e101 r13=0000000000000000
r14=0000000000000001 r15=0000000069634d43
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!KeSignalGateBoostPriority+0x56:
fffff800`02ca0b06 488b36 mov rsi,qword ptr [rsi] ds:002b:fffbfa80`06e21168=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ca0b06

STACK_TEXT:
fffff880`07cba820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSignalGateBoostPriority+0x56


FOLLOWUP_IP:
nt!KeSignalGateBoostPriority+56
fffff800`02ca0b06 488b36 mov rsi,qword ptr [rsi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KeSignalGateBoostPriority+56

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

STACK_COMMAND: .cxr 0xfffff88007cb9e40 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!KeSignalGateBoostPriority+56

BUCKET_ID: X64_0x3B_nt!KeSignalGateBoostPriority+56

Followup: MachineOwner
---------
Click to expand...
 
And then shortly afterwards came this minidump at 7:53 on the 24th of October 2012

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


Loading Dump File [C:\Dump Files\102412-36878-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Wed Oct 24 07:50:32.123 2012 (UTC + 1:00)
System Uptime: 0 days 0:11:03.777
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002c8b0db, fffff880033c4328, fffff880033c3b80}

Probably caused by : tcpip.sys ( tcpip!TcpTimerReschedule+4a )

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

1: 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: fffff80002c8b0db, The address that the exception occurred at
Arg3: fffff880033c4328, Exception Record Address
Arg4: fffff880033c3b80, 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:
nt!KiInsertTimerTable+13b
fffff800`02c8b0db 488b42f8 mov rax,qword ptr [rdx-8]

EXCEPTION_RECORD: fffff880033c4328 -- (.exr 0xfffff880033c4328)
ExceptionAddress: fffff80002c8b0db (nt!KiInsertTimerTable+0x000000000000013b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880033c3b80 -- (.cxr 0xfffff880033c3b80)
rax=0000000000000002 rbx=fffffa80057a4e00 rcx=0000000000000002
rdx=fffbfa8006ec7140 rsi=00000000000008c0 rdi=fffff88003163180
rip=fffff80002c8b0db rsp=fffff880033c4560 rbp=fffff88003165c48
r8=fffffa80057a4dc0 r9=0000000000000036 r10=fffff880009f3180
r11=0000000000000000 r12=fffff88003165c48 r13=0000000000000001
r14=fffffa80057a4d00 r15=000000018ba5f091
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293
nt!KiInsertTimerTable+0x13b:
fffff800`02c8b0db 488b42f8 mov rax,qword ptr [rdx-8] ds:002b:fffbfa80`06ec7138=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

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 fffff80002eaf100
ffffffffffffffff

FOLLOWUP_IP:
tcpip!TcpTimerReschedule+4a
fffff880`0186543a 4883c428 add rsp,28h

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80002c8ada0 to fffff80002c8b0db

STACK_TEXT:
fffff880`033c4560 fffff800`02c8ada0 : ffffffff`fffe7960 fffff880`009f3180 fffffa80`057a4e00 00000000`00000002 : nt!KiInsertTimerTable+0x13b
fffff880`033c45c0 fffff800`02c8b87d : fffffa80`057a4d30 ffffffff`fffe7960 00000000`00000001 00000000`00000000 : nt!KiSetTimerEx+0xf0
fffff880`033c4650 fffff880`0186543a : fffffa80`057f1b01 00000000`00000001 00000000`bd0457ee 00000000`0001036c : nt!KeSetTimerEx+0x11
fffff880`033c4690 fffff880`018634f2 : fffffa80`057a4d30 fffffa80`057a4d30 fffffa80`045accf0 00000000`bd0457f3 : tcpip!TcpTimerReschedule+0x4a
fffff880`033c46c0 fffff880`01865037 : fffffa80`070171c0 00000000`0000000e 00000000`00000000 00000000`bd0457f3 : tcpip!TcpTimerUpdateNextExpirationTick+0xb2
fffff880`033c4700 fffff880`0192f75c : fffffa80`0578b6a0 fffffa80`0578b6a0 fffffa80`045accf0 fffffa80`04493830 : tcpip!TcpPartitionUpdateNextExpirationTick+0x77
fffff880`033c4730 fffff880`018baed3 : fffffa80`058ff080 fffffa80`057b1890 fffffa80`070171c0 fffffa80`045accf0 : tcpip!TcpReplaceSynTcb+0xac
fffff880`033c4780 fffff880`01936ef3 : fffffa80`04493810 fffffa80`04493830 00000000`4158add6 fffffa80`04493830 : tcpip! ?? ::FNODOBFM::`string'+0x40564
fffff880`033c48e0 fffff880`018bf6ac : fffffa80`04493830 fffffa80`06ec1800 00000000`00000000 00000000`00000000 : tcpip!TcpSynTcbReceive+0x273
fffff880`033c4970 fffff880`0185fbfb : fffffa80`04189ac0 fffffa80`06ec1800 00000000`00000000 fffffa80`04569400 : tcpip! ?? ::FNODOBFM::`string'+0x44eb3
fffff880`033c4ac0 fffff880`0183b36a : fffffa80`057b1890 fffffa80`0000a4c0 fffff880`0000302f fffff880`033c302f : tcpip!TcpPreValidatedReceive+0x36b
fffff880`033c4b90 fffff800`02f72583 : fffffa80`057b48e0 00000000`00000006 00000000`00000000 fffffa80`03d01660 : tcpip!IppLoopbackTransmit+0x11a
fffff880`033c4c40 fffff800`02c89641 : fffff800`02e1d200 fffff800`02f72501 fffffa80`03d01600 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`033c4c70 fffff800`02f16e5a : 00000007`00000050 fffffa80`03d01660 00000000`00000080 fffffa80`03cec890 : nt!ExpWorkerThread+0x111
fffff880`033c4d00 fffff800`02c70d26 : fffff880`03163180 fffffa80`03d01660 fffff880`0316dfc0 fffff880`00000008 : nt!PspSystemThreadStartup+0x5a
fffff880`033c4d40 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`033c49a0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: tcpip!TcpTimerReschedule+4a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5034f727

STACK_COMMAND: .cxr 0xfffff880033c3b80 ; kb

FAILURE_BUCKET_ID: X64_0x7E_tcpip!TcpTimerReschedule+4a

BUCKET_ID: X64_0x7E_tcpip!TcpTimerReschedule+4a

Followup: MachineOwner
---------
Click to expand...
 
Just to let you know, I got my new Corsair Dominator GT fan today for the memory, to replace the old one that was making a funny noise. I've just installed that and also reseated my memory and made sure that I've got rid of dust etc..

Also I've taken onboard your advice and I've removed one of the crossfire cards also to see how it performs. I've also removed my TV card because I wasn't using it. It's just running on 1 graphics card now. I've checked all the fans and they're all working properly.

I was thinking if this problem is to do with my graphics cards and that they were crossfire enabled also, I could well replace the ATI Radeon 4870 that I'm running on now. I could possibly buy a replacement card and just have one card instead of 2. Also making sure that I buy something that's powerful so I don't need to have crossfire. Maybe the crossfire is what's causing the problem with these random BSOD.
 
Bad news :-( It's just blue screened again. With only 1 graphics card running. I'm not sure what's going on here but it's really doing my head in now.

Can't figure it out at all. I can post another minidump from the blue screen that just happened before. That's all I can do really, I was thinking maybe take the other card I've just taken out and put it in the machine and swap it with the one that's in now? Just to see if there's something wrong with it.
 
This is the latest one:

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


Loading Dump File [C:\Dump Files\102412-40513-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e51670
Debug session time: Wed Oct 24 20:44:45.906 2012 (UTC + 1:00)
System Uptime: 0 days 0:44:22.560
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {9f1b1, 2, 1, fffff80002c84770}

Probably caused by : hardware ( nt!KiPageFault+260 )

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

2: 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: 000000000009f1b1, 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: fffff80002c84770, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb100
000000000009f1b1

CURRENT_IRQL: 2

FAULTING_IP:
nt!ZwQueryObject+10
fffff800`02c84770 3000 xor byte ptr [rax],al

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800350f980 -- (.trap 0xfffff8800350f980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000009f1b1 rbx=0000000000000000 rcx=fffff6fc40018e60
rdx=0000098000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c84770 rsp=fffff8800350fb10 rbp=fffffa8001dd5130
r8=fffff880031cc000 r9=0000000000000001 r10=0000000000000002
r11=fffffa80044b3490 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po nc
nt!ZwQueryObject+0x10:
fffff800`02c84770 3000 xor byte ptr [rax],al ds:00b3:00000000`0009f1b1=??
Resetting default scope

MISALIGNED_IP:
nt!ZwQueryObject+10
fffff800`02c84770 3000 xor byte ptr [rax],al

LAST_CONTROL_TRANSFER: from fffff80002c8b569 to fffff80002c8bfc0

STACK_TEXT:
fffff880`0350f838 fffff800`02c8b569 : 00000000`0000000a 00000000`0009f1b1 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0350f840 fffff800`02c8a1e0 : 00000000`00000000 fffff800`02e13588 00000000`00000000 fffffa80`080f6000 : nt!KiBugCheckDispatch+0x69
fffff880`0350f980 fffff800`02c84770 : 00000000`0dd328c0 00000000`0dd328c0 00000000`000af402 fffffa80`000000b3 : nt!KiPageFault+0x260
fffff880`0350fb10 00000000`0dd328c0 : 00000000`0dd328c0 00000000`000af402 fffffa80`000000b3 fffffa80`05850010 : nt!ZwQueryObject+0x10
fffff880`0350fb18 00000000`0dd328c0 : 00000000`000af402 fffffa80`000000b3 fffffa80`05850010 00000000`00000001 : 0xdd328c0
fffff880`0350fb20 00000000`000af402 : fffffa80`000000b3 fffffa80`05850010 00000000`00000001 fffffa80`05850020 : 0xdd328c0
fffff880`0350fb28 fffffa80`000000b3 : fffffa80`05850010 00000000`00000001 fffffa80`05850020 fffffa80`05850030 : 0xaf402
fffff880`0350fb30 fffffa80`05850010 : 00000000`00000001 fffffa80`05850020 fffffa80`05850030 fffffa80`080f6000 : 0xfffffa80`000000b3
fffff880`0350fb38 00000000`00000001 : fffffa80`05850020 fffffa80`05850030 fffffa80`080f6000 fffff880`031cc000 : 0xfffffa80`05850010
fffff880`0350fb40 fffffa80`05850020 : fffffa80`05850030 fffffa80`080f6000 fffff880`031cc000 fffffa80`044b3490 : 0x1
fffff880`0350fb48 fffffa80`05850030 : fffffa80`080f6000 fffff880`031cc000 fffffa80`044b3490 fffff8a0`0f20d080 : 0xfffffa80`05850020
fffff880`0350fb50 fffffa80`080f6000 : fffff880`031cc000 fffffa80`044b3490 fffff8a0`0f20d080 fffffa80`080f6030 : 0xfffffa80`05850030
fffff880`0350fb58 fffff880`031cc000 : fffffa80`044b3490 fffff8a0`0f20d080 fffffa80`080f6030 fffff8a0`0f20e000 : 0xfffffa80`080f6000
fffff880`0350fb60 fffffa80`044b3490 : fffff8a0`0f20d080 fffffa80`080f6030 fffff8a0`0f20e000 fffffa80`044b3488 : 0xfffff880`031cc000
fffff880`0350fb68 fffff8a0`0f20d080 : fffffa80`080f6030 fffff8a0`0f20e000 fffffa80`044b3488 fffffa80`044b3458 : 0xfffffa80`044b3490
fffff880`0350fb70 fffffa80`080f6030 : fffff8a0`0f20e000 fffffa80`044b3488 fffffa80`044b3458 fffffa80`0563aa30 : 0xfffff8a0`0f20d080
fffff880`0350fb78 fffff8a0`0f20e000 : fffffa80`044b3488 fffffa80`044b3458 fffffa80`0563aa30 fffffa80`01dd5130 : 0xfffffa80`080f6030
fffff880`0350fb80 fffffa80`044b3488 : fffffa80`044b3458 fffffa80`0563aa30 fffffa80`01dd5130 fffffa80`046a9350 : 0xfffff8a0`0f20e000
fffff880`0350fb88 fffffa80`044b3458 : fffffa80`0563aa30 fffffa80`01dd5130 fffffa80`046a9350 00000000`03300000 : 0xfffffa80`044b3488
fffff880`0350fb90 fffffa80`0563aa30 : fffffa80`01dd5130 fffffa80`046a9350 00000000`03300000 00000000`03100000 : 0xfffffa80`044b3458
fffff880`0350fb98 fffffa80`01dd5130 : fffffa80`046a9350 00000000`03300000 00000000`03100000 00000000`00000282 : 0xfffffa80`0563aa30
fffff880`0350fba0 fffffa80`046a9350 : 00000000`03300000 00000000`03100000 00000000`00000282 fffff880`0350fbd8 : 0xfffffa80`01dd5130
fffff880`0350fba8 00000000`03300000 : 00000000`03100000 00000000`00000282 fffff880`0350fbd8 ffffffff`ffffffff : 0xfffffa80`046a9350
fffff880`0350fbb0 00000000`03100000 : 00000000`00000282 fffff880`0350fbd8 ffffffff`ffffffff 00000000`00000000 : 0x3300000
fffff880`0350fbb8 00000000`00000282 : fffff880`0350fbd8 ffffffff`ffffffff 00000000`00000000 00000000`00000001 : 0x3100000
fffff880`0350fbc0 fffff880`0350fbd8 : ffffffff`ffffffff 00000000`00000000 00000000`00000001 00000000`00000000 : 0x282
fffff880`0350fbc8 ffffffff`ffffffff : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`039e8b50 : 0xfffff880`0350fbd8
fffff880`0350fbd0 00000000`00000000 : 00000000`00000001 00000000`00000000 fffffa80`039e8b50 00000000`00000010 : 0xffffffff`ffffffff


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02c8a1e0 440f20c0 mov rax,cr8

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+260

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

Followup: MachineOwner
---------
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom