[joeldamole]

Hey ok so i have just reformatted my pc and have installed up to the latest with all my drivers and such. But I have had a blue screen of death twice since reformating, the first was when i playing the game (global agenda) and then this time when i was playing the beta for Battlefield. Now the way it happens by freezing the game for around 1 second then i get a fuzzy screen like when you go on a tv channel with no ariel. Heres my DXdiag and my event log.

Thanks!


+ System - Provider [ Name] EventLog
- EventID 6008 [ Qualifiers] 32768
Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2010-02-08T22:58:24.000Z
EventRecordID 28388 Channel System Computer joel-PC Security
- EventData


22:56:40


08/02/2010










15117










DA07020001000800160038002800EB01DA07020001000800160038002800EB01600900003C0 00000010000006009000000000000B004000001000000E7260000
Binary data:

In Words
0000: 000207DA 00080001 00380016 01EB0028
0008: 000207DA 00080001 00380016 01EB0028
0010: 00000960 0000003C 00000001 00000960
0018: 00000000 000004B0 00000001 000026E7

In Bytes
0000: DA 07 02 00 01 00 08 00 Ú.......
0008: 16 00 38 00 28 00 EB 01 ..8.(.ë.
0010: DA 07 02 00 01 00 08 00 Ú.......
0018: 16 00 38 00 28 00 EB 01 ..8.(.ë.
0020: 60 09 00 00 3C 00 00 00 `...<...
0028: 01 00 00 00 60 09 00 00 ....`...
0030: 00 00 00 00 B0 04 00 00 ....°...
0038: 01 00 00 00 E7 26 00 00 ....ç&..


And in XML view


BODY{font:x-small 'Verdana';margin-right:1.5em} .c{cursor:hand} .b{color:red;font-family:'Courier New';font-weight:bold;text-decoration:none} .e{margin-left:1em;text-indent:-1em;margin-right:1em} .k{margin-left:1em;text-indent:-1em;margin-right:1em} .t{color:#990000} .xt{color:#990099} .ns{color:red} .dt{color:green} .m{color:blue} .tx{font-weight:bold} .db{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;border-left:1px solid #CCCCCC;font:small Courier} .di{font:small Courier} .d{color:blue} .pi{color:blue} .cb{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;font:small Courier;color:#888888} .ci{font:small Courier;color:#888888} PRE{margin:0px;display:inline} - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="EventLog" />

<EventID Qualifiers="32768">6008</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2010-02-08T22:58:24.000Z" />

<EventRecordID>28388</EventRecordID>

<Channel>System</Channel>

<Computer>joel-PC</Computer>

<Security />

</System>


- <EventData>
<Data>22:56:40</Data>

<Data>08/02/2010</Data>

<Data />

<Data />

<Data>15117</Data>

<Data />

<Data />

<Binary>DA07020001000800160038002800EB01DA07020001000800160038002800EB01600 900003C000000010000006009000000000000B004000001000000E7260000</Binary>

</EventData>


</Event>

[joeldamole]

Hi just wanted to add i have just done a debuglog can anyone make sense on this? thanks

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


Loading Dump File [C:\Windows\Minidump\Mini020710-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18304.amd64fre.vistasp1_gdr.090805-0102
Machine Name:
Kernel base = 0xfffff800`01c18000 PsLoadedModuleList = 0xfffff800`01ddddb0
Debug session time: Sun Feb 7 17:25:10.036 2010 (GMT+0)
System Uptime: 0 days 5:54:08.476
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.....
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffff448c, 2, 1, fffff80001c4e867}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+396e1 )

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: 00000000ffff448c, 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: fffff80001c4e867, address which referenced memory

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


WRITE_ADDRESS: 00000000ffff448c

CURRENT_IRQL: 2

FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+396e1
fffff800`01c4e867 00488d add byte ptr [rax-73h],cl

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: GlobalAgenda.ex

TRAP_FRAME: fffff80002e6cb10 -- (.trap 0xfffff80002e6cb10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffff44ff rbx=0000000000000000 rcx=0000000b07cce1ea
rdx=0000003c31ed65ba rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001c4e867 rsp=fffff80002e6cca0 rbp=0000000000000000
r8=0000000007cce1ea r9=0000000000000010 r10=fffff78000000014
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt! ?? ::FNODOBFM::`string'+0x396e1:
fffff800`01c4e867 00488d add byte ptr [rax-73h],cl ds:e1ea:00000000`ffff448c=??
Resetting default scope

MISALIGNED_IP:
nt! ?? ::FNODOBFM::`string'+396e1
fffff800`01c4e867 00488d add byte ptr [rax-73h],cl

LAST_CONTROL_TRANSFER: from fffff80001c6c46e to fffff80001c6c6d0

STACK_TEXT:
fffff800`02e6c9c8 fffff800`01c6c46e : 00000000`0000000a 00000000`ffff448c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`02e6c9d0 fffff800`01c6b34b : 00000000`00000001 fffff800`01c96b63 fffffa80`073bd700 fffff800`02e6cd08 : nt!KiBugCheckDispatch+0x6e
fffff800`02e6cb10 fffff800`01c4e867 : fffff800`02e6cd08 00000000`00000000 fffff800`01d8ccf0 00000000`00000004 : nt!KiPageFault+0x20b
fffff800`02e6cca0 fffff800`01c75538 : fffff800`02e6cf00 fffff800`01ce8b02 fffff800`02e6cef8 00000000`00000010 : nt! ?? ::FNODOBFM::`string'+0x396e1
fffff800`02e6ced0 fffff800`01c75d9f : 0000080f`5451df10 fffffa60`09495ca0 fffff800`00000010 fffff800`01d8fa80 : nt!KiTimerExpiration+0x1d8
fffff800`02e6cf40 fffff800`01c6fba5 : fffffa60`00c0e720 fffff800`01d8c680 fffffa60`09495ca0 fffff800`0215d460 : nt!KiRetireDpcList+0x1df
fffff800`02e6cfb0 fffff800`01c6f9b7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffffa60`09495be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+396e1
fffff800`01c4e867 00488d add byte ptr [rax-73h],cl

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+396e1

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

[Rollin' Rog]

"Hardware" errors are usually due to either faulty or mismatched ram or overheating.

If this is only occurring under high stress conditions, overheating or overclocking may be suspect. If you are overclocked -- reset to the defaults.

But you should test the ram for starters >>

Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.

On Vista and Win7 you can run mdsched.exe -- once rebooted to the scanner press F1 for Advanced options and run the "extended" tests.

Another, some think better, program that can be used on all operating systems is memtest86

Beginners Guides: Diagnosing Bad Memory

Memtest86 - A Stand-alone Memory Diagnostic

-------------------------------------------------

You can also monitor the heat load under stress by using something like SpeedFan. Run a game and max out the processor for a few minutes and then check to see the highest temps for both the CPU and GPU.

http://www.majorgeeks.com/download337.html

[joeldamole]

Hey again thanks for the reply and i have just finished a 2 hour memory diagnostic scan and it came up clean with no problems. So i plan to max my processor then check the CPU an such, looking at my specs what would you say an average CPU tempurate is?

thanks

[joeldamole]

Wow ok i have just used the speed fan and went ingame on battlefield bad company 2 and i minimised when there was alot going on and two of the 5 fans were showin the on fire sign? now im thinking this can't be good so how do i adjust my fans to be quicker?

Thanks

[Rollin' Rog]

Can't always go by the fire icon. What were the maximum temps for CPU and GPU and what is your processor model?

I usually check these out (for the CPU anyway) using >> http://mysite.verizon.net/pchardwarelinks/elec.htm

You may not be able to adjust the fan speed, although you can experiment with Speedfan's adjustment -- I don't think it works in most cases.

Typically fan speeds are set by BIOS programming and are not readily adjustable

Do ensure that all vents are dust free.

[joeldamole]

ah yeh you were right don't always go by the fire icon as my mate who has a similar spec pc to me also has the fire icon, it seems its defiantly not my fans as i get a temperature of around 45'c which is lower than my mates. Following on the only difference that i had when i reformatted was i went straight onto the Radeon wedsite and downloaded the latest graphics driver from there which was 1/26/10 now i'm hoping this was the problem as i have reformatted again carefully installing everything in the correct order from my disks and i was playing BF for around 2 hours earlier with no crash. So i am hoping it is fixed but i would love for someone to tell me that the driver problem could well of been the cause of my problem?

Thanks again.

[Rollin' Rog]

Well since both seemed to involve video games -- a display driver suspicion is always a good one if you have ruled out bad memory and overheating.

Keep track of errors and changes using the "Reliability Monitor" and you can see if anything changed just preceding a problem.

http://www.howtogeek.com/howto/windo...shoot-crashes/