Daily BSOD, on multiple processes

hello there, i'm glad i found this forum and i'd like to mention i'm a newbie here , but here it goes; i've been getting BSOD's on a daily basis while playing , browsing , or just booting up my windows, i've tried everything and then i found the WinDBG tool, but it doesen't help me as much as the next guy since i'm let's say on a begginer level

i've only attached one dump file since i deleted the rest by accident

Computer specs : Intel QuadCore Q6660 @2.40ghz, 2.4gb RAM, 32-bit Windows 7 OS nVidia GeForce 9400 GT , maxtor ide 80gb HDD, asus p5w64 WS pro motherboard, Realtek RTL8139/810x Family Fast Ethernet NIC, onboard soundcard

I've gotten a new BSOD since the last time i posted, i`ll upload the dump

bump, some assistance would be appreciated.

Possible out of date driver:

Code:

Rtnicxp	92a00000	92a0f000	Fri May 30 09:12:11 2008 (4840194b)	00018af7		Rtnicxp.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\AndreiN\042012-23384-01\042012-23384-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a42000 PsLoadedModuleList = 0x82b8a810
Debug session time: Fri Apr 20 13:49:07.009 2012 (UTC - 6:00)
System Uptime: 0 days 2:18:29.897
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 82b77eb8, the pool entry being checked.
Arg3: 82b77eb8, the read back flink freelist value (should be the same as 2).
Arg4: 00000000, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82af5759 to 82b62232

STACK_TEXT:  
81f93af4 82af5759 00000018 000004b8 d0646641 nt!ExAllocatePoolWithTag+0x682
81f93b18 8ec35114 84e9a980 000004b8 d0646641 nt!ExAllocatePoolWithQuotaTag+0x57
81f93b5c 8ec3452a 000004b4 81f93be4 00012024 afd!AfdPollGetInfo+0x20
81f93bec 8ec2d504 86601288 85befbd0 81f93c14 afd!AfdPoll+0xb2
81f93bfc 82a7e4bc 85befbd0 86d71638 86d71638 afd!AfdDispatchDeviceControl+0x3b
81f93c14 82c7feee 86601288 86d71638 86d71714 nt!IofCallDriver+0x63
81f93c34 82c9ccd1 85befbd0 86601288 00000000 nt!IopSynchronousServiceTail+0x1f8
81f93cd0 82c9f4ac 85befbd0 86d71638 00000000 nt!IopXxxControlFile+0x6aa
81f93d04 82a8542a 00000240 0000025c 00000000 nt!NtDeviceIoControlFile+0x2a
81f93d04 77c464f4 00000240 0000025c 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0370cabc 00000000 00000000 00000000 00000000 0x77c464f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdPollGetInfo+20
8ec35114 8b4d0c          mov     ecx,dword ptr [ebp+0Ch]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  afd!AfdPollGetInfo+20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf62

FAILURE_BUCKET_ID:  0x19_3_afd!AfdPollGetInfo+20

BUCKET_ID:  0x19_3_afd!AfdPollGetInfo+20

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

Your crash is network related. The possible out of date driver is a network driver, so I suspect the two are related. You can find the update for the driver on your motherboard support site. http://www.asus.com/Motherboards/Int..._Professional/ -> Download -> OS: Windows 7 32bit -> Network


Note: I have been having trouble accessing the ASUS motherboard sites all weekend, so the site may be down currently. You may have to wait a few days before you can update the driver.

thanks , i`ll try your fix,but i'm still getting a ton of bsod's, i'll post a reply with a dump zip in a few hours.

these are just a few bsods i got since yesterday up untill right now, i've no idea what's going on, i've tried everything, i even cleaned out my RAM pins with alcohol ,everything is up to date as far as i can tell, i'm just left in the dark here, and it's really really frustrating.
thanks in advance, Andrei.

Just a few!?!


The Verifier enabled crashes were a variety of things. Network related crashes, memory corruption, and hard drive corruption were the common factors.

• If you are overclocking any hardware, please stop.
  
  
• Disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

I'll do the following and i'll come back with a log in a few then, thank you.