New
#1
Constant Freezing up
I have updated my drivers to the best I know how, run windows update, used CCleaner. But still have these frequent crashes.
Running Winows 7 32 bit
quad 3ghz
4 gigs of ram
Nvidia 260
found a program called who crahsed that gave me this info
On Thu 2/10/2011 6:16:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021011-26114-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xFCC0)
Bugcheck code: 0xC5 (0x2CA8, 0x2, 0x0, 0xFFFFFFFF82B24795)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 2/10/2011 6:16:05 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xFCC0)
Bugcheck code: 0xC5 (0x2CA8, 0x2, 0x0, 0xFFFFFFFF82B24795)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Mon 2/7/2011 12:38:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020711-22339-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xC5 (0x93D8, 0x2, 0x0, 0xFFFFFFFF82B70795)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 1/28/2011 8:40:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012811-23275-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xFCC0)
Bugcheck code: 0xC5 (0xEBC8, 0x2, 0x0, 0xFFFFFFFF82B6E795)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
any help is apreciated.