New Computer, BSOD in windows 7

Hi
I bought a new computer and started getting lots of bluescreens. I did a memtest and got lots of errors, so I sent back my ram. Today I got some new ram, and I still get bluescreens and memtest errors. I think the bluescreen I got was different from the ones I got last time though. I would really appreciate if anyone can have a look at the dump file for me, cause I'm not really that good with it myself.

My computer setup is:
Motherboard: ASUS pQ5 SE2, P45, Socket-775
Processor: Intel Core 2 Quad Q9550 2.83GHz, 1333MHz
Graphics card: XFX Geforce GTS 250 1GB Physx CUDA
RAM: Corsair TWIN2X PC6400C4DHX DDR2 4GB kit
w/2x 2GB XMS2-6400 dimm's CL4-4-4-12 800MHz, DHX

Only got one BSOD so far, simply for the reason that I don't really get them while at desktop, only when I'm playing games. Put the .dmp in a rar and attached it. Like I said, any help is greatly appreciated!

if anyone could please analyze the dump file for me, that would be great I've tried to do it myself, but failed cause I'm pretty new to this. If you need more info please tell me. I really appreciate it if someone could spare the time.

pubbe said:

if anyone could please analyze the dump file for me, that would be great I've tried to do it myself, but failed cause I'm pretty new to this. If you need more info please tell me. I really appreciate it if someone could spare the time.

Pubbe

I took a quick look at it and afd.sys caused it. ita part of the tcpip stack. Hl2.exe (a steam file) was involved. the way it looks to me the game (hl2.exe) made a request to the server (tcpip) incorrectly corrpting the memory pool

things you can do: A couple of the drivers are fairly old. I would reinstalling the wifi/lan driver.

From the looks of it I wonder: are you overclocking? are you having a heat issue in CPU/GPU? check temps
I would also run a system file check to verify and fix system files. Its run by going to seach and typing cmd>right click run as admin>sfc scannow

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


Loading Dump File [C:\Users\K\Desktop\101609-29328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02861000 PsLoadedModuleList = 0xfffff800`02a9ee50
Debug session time: Fri Oct 16 10:08:17.350 2009 (GMT-4)
System Uptime: 0 days 2:13:33.301
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {fffff8807fcd3d18, 2, 0, fffff80002a059bb}

Probably caused by : afd.sys ( afd!AfdPollGetInfo+21 )

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

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffff8807fcd3d18, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002a059bb, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExAllocatePoolWithTag+5eb
fffff800`02a059bb 4c8ba42408010000 mov r12,qword ptr [rsp+108h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: hl2.exe



STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdPollGetInfo+21
fffff880`02c93371 488903 mov qword ptr [rbx],rax

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: afd!AfdPollGetInfo+21

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184

FAILURE_BUCKET_ID: X64_0xC5_2_afd!AfdPollGetInfo+21

BUCKET_ID: X64_0xC5_2_afd!AfdPollGetInfo+21

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

Thank you so much.

I will try to install some new drivers then.

No, I'm not overclocking, although I did try to set some different volt values in bios for my RAM before I sent the old RAM back in and got new ones. I set the values to what they recommended at the corsair forum.

Do you think maybe there could be something wrong with my components?

Again, thanks for the help

pubbe said:

Thank you so much.

I will try to install some new drivers then.

No, I'm not overclocking, although I did try to set some different volt values in bios for my RAM before I sent the old RAM back in and got new ones. I set the values to what they recommended at the corsair forum.

Do you think maybe there could be something wrong with my components?

Again, thanks for the help

\
Pubbe

I would also run a memory test by downloading memtestx86 and running it overnight. if you keep having problems you might want to put the voltages back to default.

good luck

Okidok. Thanks for the replies

Hi


First lets asume you arent

Overclocking

Running A RAID

Have a "odd" device attached like a fingerprint reader, card reader, etc

You shoul run a system file checker to verify and repair system fileds

You do that by typing cmd in search>right click and run as admn> sfc /scannow

Let us know the results

You should also run a memory test like memtestx86 opreferable overnight

Ken