hi again macboatmaster yes this is another post on basically the same problem, i honestly completely forgot about the other post. ok i downloaded that whocrashed it program and it says crash dumps are disabled for my computer and it came up with 10 crash dumps all seem to be kernel data inpage errors.they also say that the system configuration may be incorrect and that the problem is possibly caused by another driver but that it cant be identified.
Crash dump directory: C:\windows\Minidump
Crash dumps are disabled for your computer.
On Mon 2/28/2011 3:26:54 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022811-32417-01.dmp
This was probably caused by the following module: discache.sys (discache+0x3867)
Bugcheck code: 0x7A (0xFFFFFFFFC052C8B0, 0xFFFFFFFFC0000185, 0x22143820, 0xFFFFFFFFA5916F10)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\discache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Indexer/Cache Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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/28/2011 3:26:54 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: discache.sys (discache+0x3867)
Bugcheck code: 0x7A (0xFFFFFFFFC052C8B0, 0xFFFFFFFFC0000185, 0x22143820, 0xFFFFFFFFA5916F10)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\discache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Indexer/Cache Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 2/27/2011 8:35:01 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022711-20311-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x7A (0xFFFFFFFFC04F1018, 0xFFFFFFFFC0000185, 0x696B38C0, 0xFFFFFFFF9E203B46)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 2/26/2011 11:03:56 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022611-21699-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x7A (0xFFFFFFFFC04EB070, 0xFFFFFFFFC0000185, 0x78FD8C0, 0xFFFFFFFF9D60E008)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 2/25/2011 9:37:46 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022511-25147-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x7A (0xFFFFFFFFC04C1018, 0xFFFFFFFFC0000185, 0x3D1358C0, 0xFFFFFFFF98203000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2/24/2011 3:07:23 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022411-21902-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDFC)
Bugcheck code: 0x7A (0xFFFFFFFFC0496360, 0xFFFFFFFFC0000185, 0x3FE48C0, 0xFFFFFFFF92C6C4F8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 2/23/2011 12:49:45 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022311-28672-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x85A06)
Bugcheck code: 0x7A (0xFFFFFFFFC0530640, 0xFFFFFFFFC0000185, 0x1E9248C0, 0xFFFFFFFFA60C8000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Wed 2/23/2011 2:22:37 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022211-26301-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x139E8)
Bugcheck code: 0x7A (0xFFFFFFFFC041B9E0, 0xFFFFFFFFC0000185, 0x11187860, 0xFFFFFFFF8373C9E8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Tue 2/22/2011 11:09:35 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022211-26722-01.dmp
This was probably caused by the following module: discache.sys (discache+0x3867)
Bugcheck code: 0x7A (0xFFFFFFFFC04F2728, 0xFFFFFFFFC0000185, 0x6A10820, 0xFFFFFFFF9E4E56EE)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\discache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Indexer/Cache Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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/17/2011 2:41:28 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\021611-36707-01.dmp
This was probably caused by the following module: pcw.sys (pcw+0x5A98)
Bugcheck code: 0x7A (0xFFFFFFFFC0440438, 0xFFFFFFFFC0000185, 0x5FAC5860, 0xFFFFFFFF88087A98)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\pcw.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Performance Counters for Windows Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
should crash dumps be enabled on my computer, if so how would i go about doing that?
Sign In
Create Account
