Blue Screen of Death and Error Messages

Splash_EAF92 · April 6, 2011, 1:02pm

Meaks that is the card I put in today :), I tried ROF on Max settings and it only came out at 71% usage, when I had the 295 in I couldn’t max it out as that would have taken it to 114%.

Your motherboard is close to mine I have EX58-UD5 but with 12 Gb of RAM. I like Win 7 but saying that I never had a problem with Vista. The only thing is Win 7 uses less resources from what I have read, I haven’t noticed any massive difference.

Win 7 has an index which runs between 1.0 and 7.9 I think, shows how good your computer is. That graphics card is tops and my worst is as Mikke says my HDD in at 7.0. Might have to do the SSD myself but they are a bit small storage wise for my liking at the moment.

Format/Re-install and see what happens is what I would do first, if systems persist maybe the graphics card. 6 Gb RAM is good anyway I just kicked the ar*e out of it.

Splash

EAF92_Meako · April 6, 2011, 1:06pm

Yes i get a least one BSOD daily, last one was last night in ROF.

The file is 741mb i have emailed a link to you i have hosted it on my rapidshare as its too big to mail check your yahoo mail accnt for 30/3/2011.

EAF92_Brigstock · April 6, 2011, 2:51pm

Meaks
The error message you are getting is a memory access error, that does not neccessarily mean your memory is at fault, it is a fairly generic memory access error message that could mean hardware or even software issues.
Looking at the dust build up on the heatsink too, although not good, it is not outrageous either. In situations like this I’d do a install of the OS, followed by systematic replacement of hardware. But then I do have untold bits and pieces hanging around and a limitless supply at work too.

Your problem could well point to the graphics card as it is when playing games and the card is stressed that you are getting the error. In your position I’d replace the 285 with a 480 and move to Win7. Firstly replacing the card, it most likely that causing the issue and if you can afford it upgrading to the 480 is smart move now OCUK have dropped the price considerably over the last few weeks. Secondly Vista is a resource hogging mess of an OS, Win 7 is much better and I can help in that department I’ll PM you.

Try Win7 first, if you still get the BSOD. Then swap the card.

EAF92_Meako · April 6, 2011, 3:38pm

My gut feeling is the graphics card is behind some if not all of my BSOD.

Would i get a performance boost with the 480 over the 285, i am thinking COD may not always be porked and anything that helps get me off lowest settings would be a worthwhile investment.

EAF92_Brigstock · April 6, 2011, 4:03pm

The jump to 480 from 285 is noticable, I did the exact same route 6 months ago and now that the card has come down in price why not.
You’ll not be able to max CoD, but I don’t think anyone will for a while yet

EAF92_Meako · April 6, 2011, 11:57pm

480 ordered last night.

EAF92_Meako · April 7, 2011, 12:06am

Brigs postcode on first pm wrong its on separate pm

EAF92_Keets · April 7, 2011, 4:36am

WinDBG info on your BSOD:

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: fffffa6010b65610, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffffa6010b65610, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

WRITE_ADDRESS: fffffa6010b65610

FAULTING_IP:
+6630376636623862
fffffa60`10b65610 ?? ???

MM_INTERNAL_CODE: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffffa600237ea70 – (.trap 0xfffffa600237ea70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa6000f4c780
rdx=fffffa6000f4c000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6010b65610 rsp=fffffa600237ec08 rbp=fffffa6000f4c790
r8=0000000000000001 r9=0000000000000000 r10=0000000000000006
r11=fffffa600237ec88 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffffa60`10b65610 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800076caa8a to fffff8000766a490

STACK_TEXT:
fffffa600237e988 fffff800076caa8a : 0000000000000050 fffffa6010b65610 0000000000000008 fffffa600237ea70 : nt!KeBugCheckEx
fffffa600237e990 fffff80007669019 : 0000000000000008 0000000000000000 ffffffdffcd4d800 fffffa6000f4c6c0 : nt! ?? ::FNODOBFM::string'+0x2c465 fffffa600237ea70 fffffa6010b65610 : fffffa6000b65545 fffffa80051d0138 fffffa600211e7f0 fffffa80051d0040 : nt!KiPageFault+0x119 fffffa600237ec08 fffffa6000b65545 : fffffa80051d0138 fffffa600211e7f0 fffffa80051d0040 fffff800077a18f8 : 0xfffffa6010b65610
fffffa600237ec10 fffffa6000b65c2e : 0000000000000000 0000000000000000 fffffa6000f4c6c0 0000000020206f49 : NETIO!WfpTimerWheelTimeoutHandler+0x175
fffffa600237ec90 fffff800078cb203 : fffffa80063c24f0 fffff8000779f520 0000000000000001 fffffa80051d0040 : NETIO!WfpSysTimerNdisPassiveCallback+0x2e
fffffa600237ecc0 fffff800076718c3 : fffff800079f0d70 fffff800077a1801 fffffa80051d0000 0000000000000000 : nt!IopProcessWorkItem+0x27
fffffa600237ecf0 fffff80007874f77 : fffffa8006ba3c30 e80a7459c085ffff fffffa80051d0040 0000000000000080 : nt!ExpWorkerThread+0xfb
fffffa600237ed50 fffff800076a7636 : fffffa600211e180 fffffa80051d0040 fffffa6002127d40 fffffa80051d3ca8 : nt!PspSystemThreadStartup+0x57
fffffa600237ed80 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!WfpTimerWheelTimeoutHandler+175
fffffa60`00b65545 f0838668060000ff lock add dword ptr [rsi+668h],0FFFFFFFFh

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: NETIO!WfpTimerWheelTimeoutHandler+175

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 49e02e06

FAILURE_BUCKET_ID: X64_0x50_NETIO!WfpTimerWheelTimeoutHandler+175

BUCKET_ID: X64_0x50_NETIO!WfpTimerWheelTimeoutHandler+175

Followup: MachineOwner

The debug points to your NETIO.sys which are network drivers…

Have you upgraded or installed a 3rd party driver for your network adapter, or has any s/w changed the network drivers?

Or, do you have any other s/w which is “managing” your network adapters?

First thing I’d do is find out what network adapter I had and update the drivers.

I’d uninstall Kaspersky as well, though not related.

EAF92_Meako · April 7, 2011, 9:07am

I have not knowingly touched my network drivers.

I can and will look to update these drivers.

Interested that you say delete Kaspersky, i did renew my Kaspersky about a month ago and maybe that is causing the issue?

Are you saying delete and reinstall or delete and go with another AV solution ?

EAF92_Keets · April 7, 2011, 9:18am

I’d uninstall it and then use a registry cleaner to make sure Kaspersky has gone completely.

If you are behind a router, you’ll be safe enough for a couple of days, no pr0n sites though, and run like that. If you’re BSOD’s disappear then you’re on to something, if they don’t then re-install.

With regards your network drivers, I’d go here:

http://us.test.giga-byte.com/Support/Motherboard/Driver_Model.aspx?ProductID=2991&ost=others

Download and update the latest drivers and chipset for your MoBo. Your board should be running realtek drivers and I can’t see them from your kernel dump installed on your system, which means you’ll be using the windows drivers.

MAKE SURE YOU GET THE RIGHT REVISION OF YOUR MOBO

Do the chipset first, then LAN drivers etc.

Debugging BSOD’s is a process of elimination. If you post this on M$oft’s technet, they’d have you rip out all 3rd party s/w, update your mobo chipset, all drivers (only install WHQL versions) and then report back.