Windows Vista blue screen errors

Here are some dump files (.dmp changed to .txt)
Mini062809-01.txt
Mini062909-02.txt
Mini063009-01.txt

seems to be driver problems please update all drivers. (how to check wich drivers are outdated: http://driveragent.com/scan_step1.php?r=8)

Here's the last crash after following the steps from asrdias, reporting error  SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION in the blue screen itself

See attached dump file

Extra informatie over het probleem
BCCode:      c1
BCP1:      B4648EB8
BCP2:      B4648A2F
BCP3:      00AF0148
BCP4:      00000032
OS Version:      6_0_6001
Service Pack:      1_0
Product:      768_1
Servergegevens:      496403e7-8aac-4c41-ad0f-4f3a03e467ef

Mini070109-02.txt

So...

Verifier is enabled we can verify that:

0: kd> !verifier

Verify Level 9 ... enabled options are:
      Special pool
      All pool allocations checked on unload

Summary of All Verifier Statistics

RaiseIrqls                             0x2bc168
AcquireSpinLocks                       0xef9443
Synch Executions                       0x5ed1f
Trims                                  0x0

Pool Allocations Attempted             0x787e29
Pool Allocations Succeeded             0x787e29
Pool Allocations Succeeded SpecialPool 0x3e8f2d
Pool Allocations With NO TAG           0x36
Pool Allocations Failed                0x0
Resource Allocations Failed Deliberately   0x0

Current paged pool allocations         0x135f1 for 01547744 bytes
Peak paged pool allocations            0x1360b for 015597F8 bytes
Current nonpaged pool allocations      0x1264f for 01611654 bytes
Peak nonpaged pool allocations         0x12687 for 03548844 bytes

GetPointerFromAddress: unable to read from 82548868
Unable to read MiSystemVaType memory at 82528420

Let try to see who caused the pool curruption...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: b4648eb8, address trying to free
Arg2: b4648a2f, address where one bit is corrupted
Arg3: 00af0148, (reserved)
Arg4: 00000032, caller is freeing an address where nearby bytes within the same page have a single bit error

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


BUGCHECK_STR:  0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE:  32

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 824a8a53 to 824de0e3

STACK_TEXT:  
ChildEBP RetAddr  Args to Child              
82506844 824a8a53 000000c1 b4648eb8 b4648a2f nt!KeBugCheckEx+0x1e (CONV: stdcall)
8250693c 824fef78 b4648eb8 00000000 b4648eb8 nt!MmFreeSpecialPool+0x6c (CONV: stdcall)
825069a4 8244e1bc b4648eb8 00000000 825069e0 nt!ExFreePoolWithTag+0xeb (CONV: stdcall)
825069c0 826f31cd b4648eb8 b4648eb8 8f9b8db0 nt!IopFreeIrp+0x56 (CONV: stdcall)
825069d8 8d569986 00000000 b4648eb8 82506a9c nt!IovFreeIrpPrivate+0x58 (CONV: stdcall)
825069f4 826f3d4d 00000000 b4648eb8 8f9b8db0 irsir!SerialIoCompleteRead+0x96 (FPO: [Non-Fpo]) (CONV: stdcall)
82506a2c 8244b10c 00000000 b4648eb8 82506a9c nt!IovpLocalCompletionRoutine+0x16e (CONV: stdcall)
82506a64 826f3b95 b4648eb8 8b1f794c 8b1f7890 nt!IopfCompleteRequest+0x11d (CONV: fastcall)
82506ad4 8d55179a 00000000 8b1f794c 82506b08 nt!IovCompleteRequest+0x11c (CONV: fastcall)
82506ae4 8d551730 8b1f794c 8b1f792c 82506b3c serial!SerialGetNextIrpLocked+0x61 (FPO: [Non-Fpo]) (CONV: stdcall)
82506b08 8d551d8e 8b1f794c 8b1f792c 82506b3c serial!SerialGetNextIrp+0x27 (FPO: [Non-Fpo]) (CONV: stdcall)
82506b30 8d5452a9 8b1f7890 00000000 8b1f7802 serial!SerialTryToCompleteCurrent+0x7a (FPO: [Non-Fpo]) (CONV: stdcall)
82506b68 824c7c40 8b1f7ab4 8b1f7802 95b64179 serial!SerialReadTimeout+0x68 (FPO: [Non-Fpo]) (CONV: stdcall)
82506c88 824c7800 82506cd0 8b3e9202 82506cd8 nt!KiTimerListExpire+0x367 (CONV: fastcall)
82506ce8 824c73c3 00000000 00000000 000069ae nt!KiTimerExpiration+0x22a (CONV: stdcall)
82506d50 824c5edd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba (CONV: fastcall)
82506d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49 (FPO: [0,0,0])



STACK_COMMAND:  kb

FOLLOWUP_IP:
irsir!SerialIoCompleteRead+96
8d569986 385dff          cmp     byte ptr [ebp-1],bl

SYMBOL_STACK_INDEX:  5

MODULE_NAME: irsir

IMAGE_NAME:  irsir.sys <- This is your problematic driver....

****************************************************************************************************************


My advice is disable this driver:  irsir.sys
Check if your system stops crashing. If it crashes with this driver disabled send the new minidump but keep verifier on !
Its very unusual to see this driver causing this kind of problems. You might have to check with MS about this issue.

Driver info:

0: kd> lmvm  irsir
start    end        module name
8d567000 8d572000   irsir
    Loaded symbol image file: irsir.sys
    Image path: \SystemRoot\system32\DRIVERS\irsir.sys
    Image name: irsir.sys
    Timestamp:        Sat Jan 19 05 2008
    File version:     6.0.6001.18000
    Product version:  6.0.6001.18000
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     IRSIR.SYS
    OriginalFilename: IRSIR.SYS
    ProductVersion:   6.0.6001.18000
    FileDescription:  Serial Infrared Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Thanks!

I kept having problems, with all sort of drivers, so the problem actually being all of hose single drivers became less and less likely.

I then folllowed an instruction in a blue screen telling to update the bios (didn't help) and disable bios caching options. The latter seemed to be helpful. Have had one blue screen since but that was after having moved the pc and reconnected to AC, I have seen that happen before on other pc's. Now I will follow up and wait for the client to report if the problem still exists, haven't hears from him now for two days...

You may have some problem at the hardware level.
Something is making the drivers write at memory locations that dont belong to them.
CPU? Bad memory chips... Test with new memory chips first. That would be my first test...

solved the question myself but comments where helpful anyway