Edited by Macboatmaster, 27 March 2012 - 09:35 AM.
edited to remove OTL text. Not used in this forum
Computer reboots frequently
Started by
Klown1969
, Mar 27 2012 09:04 AM
#1
Posted 27 March 2012 - 09:04 AM
Klown1969
-
- Member
-
- 33 posts
Member
#2
Posted 27 March 2012 - 09:39 AM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
Welcome to GeekstoGo
I have as shown edited your post to remove the OTL text. It is not used in the general forums, only in our malware forum.
Would you please download this and post me the results as a copy and paste of those, not as an attached file
Thank you
http://www.resplendence.com/whocrashed
Please click the analyse tab and then scroll for the results
Could you also please go start, run and type
msinfo32
when that opens would you please click the edit tab, select all, then edit copy
then paste that as well please
I have as shown edited your post to remove the OTL text. It is not used in the general forums, only in our malware forum.
Would you please download this and post me the results as a copy and paste of those, not as an attached file
Thank you
http://www.resplendence.com/whocrashed
Please click the analyse tab and then scroll for the results
Could you also please go start, run and type
msinfo32
when that opens would you please click the edit tab, select all, then edit copy
then paste that as well please
#3
Posted 27 March 2012 - 10:15 AM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
System Information (local)
--------------------------------------------------------------------------------
computer name: KELLY-C8D55886B
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Pentium® Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488002048 total
VM: 2147352576, free: 2038509568
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 3/27/2012 1:37:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032712-01.dmp
This was probably caused by the following module: hdaudbus.sys (HDAudBus+0x2021D)
Bugcheck code: 0x1000000A (0xFFFFFFFF8D589AAC, 0x2, 0x0, 0xFFFFFFFF80522620)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Windows ® Server 2003 DDK provider
description: High Definition Audio Bus Driver v1.0a
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hdaudbus.sys (High Definition Audio Bus Driver v1.0a, Windows ® Server 2003 DDK provider).
Google query: hdaudbus.sys Windows ® Server 2003 DDK provider CUSTOM_ERROR
On Tue 3/27/2012 4:35:53 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-04.dmp
This was probably caused by the following module: rdbss.sys (rdbss+0x469)
Bugcheck code: 0x1000000A (0xF5C8, 0x1C, 0x1, 0xFFFFFFFF80503824)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
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 3/27/2012 2:59:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5F84C)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFEC, 0x0, 0xFFFFFFFF8053684C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 3/26/2012 8:39:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x77C93, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Mon 3/26/2012 6:34:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x500101, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Sun 3/25/2012 12:58:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x8F, 0x28F5C, 0xBAFDC, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Sat 3/24/2012 5:56:26 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2EF37)
Bugcheck code: 0x10000050 (0xFFFFFFFFF13FB0BC, 0x0, 0xFFFFFFFF80505F37, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 3/24/2012 5:45:18 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-02.dmp
This was probably caused by the following module: rdbss.sys (rdbss+0x7747)
Bugcheck code: 0x27 (0xFFFFFFFFBAAD00A3, 0xFFFFFFFFB77E6574, 0xFFFFFFFFB77E6270, 0x96)
Error: RDR_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
Bug check description: This indicates that a problem occurred in the SMB redirector file system.
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 Sat 3/24/2012 5:09:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x171B)
Bugcheck code: 0x1000000A (0xF9403, 0x1C, 0x0, 0xFFFFFFFF804FA257)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 Fri 3/23/2012 4:51:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032312-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x27BF)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFFBA348D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 3/22/2012 9:57:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032212-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B73B)
Bugcheck code: 0x1000000A (0x42537D74, 0x2, 0x1, 0xFFFFFFFF8052273B)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 3/20/2012 8:49:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032012-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9628)
Bugcheck code: 0x10000050 (0xFFFFFFFF9F8BC92F, 0x0, 0xFFFFFFFF805B947E, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 3/20/2012 2:19:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032012-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2A82E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8050182E, 0x7FFDAC74, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 3/20/2012 2:14:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031912-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x8F, 0x5A3A4, 0x5A4E4, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Tue 3/20/2012 2:13:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031912-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB770E5B0, 0xFFFFFFFFB770E2AC, 0xFFFFFFFFB9E37B54)
Error: NTFS_FILE_SYSTEM
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 indicates a problem occurred in the NTFS file system.
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini032212-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 40 crash dumps have been found. Only 39 could be analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
hdaudbus.sys (High Definition Audio Bus Driver v1.0a, Windows ® Server 2003 DDK provider)
--------------------------------------------------------------------------------
computer name: KELLY-C8D55886B
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Pentium® Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488002048 total
VM: 2147352576, free: 2038509568
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 3/27/2012 1:37:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032712-01.dmp
This was probably caused by the following module: hdaudbus.sys (HDAudBus+0x2021D)
Bugcheck code: 0x1000000A (0xFFFFFFFF8D589AAC, 0x2, 0x0, 0xFFFFFFFF80522620)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Windows ® Server 2003 DDK provider
description: High Definition Audio Bus Driver v1.0a
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hdaudbus.sys (High Definition Audio Bus Driver v1.0a, Windows ® Server 2003 DDK provider).
Google query: hdaudbus.sys Windows ® Server 2003 DDK provider CUSTOM_ERROR
On Tue 3/27/2012 4:35:53 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-04.dmp
This was probably caused by the following module: rdbss.sys (rdbss+0x469)
Bugcheck code: 0x1000000A (0xF5C8, 0x1C, 0x1, 0xFFFFFFFF80503824)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
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 3/27/2012 2:59:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5F84C)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFEC, 0x0, 0xFFFFFFFF8053684C, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 3/26/2012 8:39:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x77C93, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Mon 3/26/2012 6:34:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x500101, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Sun 3/25/2012 12:58:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x8F, 0x28F5C, 0xBAFDC, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Sat 3/24/2012 5:56:26 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2EF37)
Bugcheck code: 0x10000050 (0xFFFFFFFFF13FB0BC, 0x0, 0xFFFFFFFF80505F37, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 3/24/2012 5:45:18 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-02.dmp
This was probably caused by the following module: rdbss.sys (rdbss+0x7747)
Bugcheck code: 0x27 (0xFFFFFFFFBAAD00A3, 0xFFFFFFFFB77E6574, 0xFFFFFFFFB77E6270, 0x96)
Error: RDR_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
Bug check description: This indicates that a problem occurred in the SMB redirector file system.
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 Sat 3/24/2012 5:09:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x171B)
Bugcheck code: 0x1000000A (0xF9403, 0x1C, 0x0, 0xFFFFFFFF804FA257)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 Fri 3/23/2012 4:51:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032312-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x27BF)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFFBA348D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 3/22/2012 9:57:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032212-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B73B)
Bugcheck code: 0x1000000A (0x42537D74, 0x2, 0x1, 0xFFFFFFFF8052273B)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 3/20/2012 8:49:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032012-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9628)
Bugcheck code: 0x10000050 (0xFFFFFFFF9F8BC92F, 0x0, 0xFFFFFFFF805B947E, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 3/20/2012 2:19:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032012-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2A82E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8050182E, 0x7FFDAC74, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 3/20/2012 2:14:58 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031912-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x8F, 0x5A3A4, 0x5A4E4, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Tue 3/20/2012 2:13:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031912-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB770E5B0, 0xFFFFFFFFB770E2AC, 0xFFFFFFFFB9E37B54)
Error: NTFS_FILE_SYSTEM
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 indicates a problem occurred in the NTFS file system.
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini032212-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 40 crash dumps have been found. Only 39 could be analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
hdaudbus.sys (High Definition Audio Bus Driver v1.0a, Windows ® Server 2003 DDK provider)
#4
Posted 27 March 2012 - 10:16 AM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Name KELLY-C8D55886B
System Manufacturer BIOSTAR Group
System Model P4M900-M7 FE
System Type X86-based PC
Processor x86 Family 6 Model 15 Stepping 13 GenuineIntel ~2199 Mhz
BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 6/25/2008
SMBIOS Version 2.4
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name KELLY-C8D55886B\klown
Time Zone Central Daylight Time
Total Physical Memory 4,096.00 MB
Available Physical Memory 2.67 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 5.09 GB
Page File C:\pagefile.sys
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Name KELLY-C8D55886B
System Manufacturer BIOSTAR Group
System Model P4M900-M7 FE
System Type X86-based PC
Processor x86 Family 6 Model 15 Stepping 13 GenuineIntel ~2199 Mhz
BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 6/25/2008
SMBIOS Version 2.4
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name KELLY-C8D55886B\klown
Time Zone Central Daylight Time
Total Physical Memory 4,096.00 MB
Available Physical Memory 2.67 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 5.09 GB
Page File C:\pagefile.sys
#5
Posted 27 March 2012 - 11:13 AM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
Go start, run type cmd
when that window opens type
cd \
that should take you to a C:\> prompt
type
chkdsk /r
agree the message to run on restart and so so please
after the chkdsk has completed and it is a five stage check, please do not interrupt it
Go start Control Panel
Admin tools
event viewer
click application in left pane
click the source column heading
that will sort them alphabetically
look now for the winlogon entries
open the winlogon that is the most recent
check that it is the chkdsk results for the check you have just run
click on the double page symbol below the broad up and down arrows.
On your reply right click and paste
OR paste to wordpad and then copy and paste to the message
Also please go device manager
and check for any warnings against any devices
Your audio driver is mentioned in crash dumps
On the view tan, click to shown hidden devices
Please wither post details of the warnings with the error code OR send a screenshot
OR if you have the knowledge explore the warning and error code and take the appropriate action
To send a screenshot do this please.
Press the Print Screen key
when that window opens type
cd \
that should take you to a C:\> prompt
type
chkdsk /r
agree the message to run on restart and so so please
after the chkdsk has completed and it is a five stage check, please do not interrupt it
Go start Control Panel
Admin tools
event viewer
click application in left pane
click the source column heading
that will sort them alphabetically
look now for the winlogon entries
open the winlogon that is the most recent
check that it is the chkdsk results for the check you have just run
click on the double page symbol below the broad up and down arrows.
On your reply right click and paste
OR paste to wordpad and then copy and paste to the message
Also please go device manager
and check for any warnings against any devices
Your audio driver is mentioned in crash dumps
On the view tan, click to shown hidden devices
Please wither post details of the warnings with the error code OR send a screenshot
OR if you have the knowledge explore the warning and error code and take the appropriate action
To send a screenshot do this please.
Press the Print Screen key
- It is normally the key above your number pad between the F12 key and the Scroll Lock key
- Now go to Start and then to All Programs
- Scroll to Accessories and then click on Paint
- In the Empty White Area click and hold the CTRL key and then click the V
- Go to the File option at the top and click on Save as
- Save as file type JPEG and save it to your Desktop
- Attach it to your next reply
#6
Posted 27 March 2012 - 11:39 AM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 3/27/2012
Time: 12:33:00 PM
User: N/A
Computer: KELLY-C8D55886B
Description:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 552 unused index entries from index $SII of file 0x9.
Cleaning up 552 unused index entries from index $SDH of file 0x9.
Cleaning up 552 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
488375968 KB total disk space.
9881192 KB in 36568 files.
11260 KB in 3270 indexes.
0 KB in bad sectors.
145880 KB in use by the system.
65536 KB occupied by the log file.
478337636 KB available on disk.
4096 bytes in each allocation unit.
122093992 total allocation units on disk.
119584409 allocation units available on disk.
Internal Info:
90 f4 00 00 aa 9b 00 00 1c bb 00 00 00 00 00 00 ................
56 00 00 00 00 00 00 00 34 08 00 00 00 00 00 00 V.......4.......
da 7f 2e 04 00 00 00 00 82 70 d2 12 00 00 00 00 .........p......
d0 01 30 0d 00 00 00 00 4a f1 b5 e5 00 00 00 00 ..0.....J.......
64 64 d8 0e 00 00 00 00 c6 b6 07 20 01 00 00 00 dd......... ....
00 56 21 83 00 00 00 00 10 3a 07 00 d8 8e 00 00 .V!......:......
00 00 00 00 00 a0 19 5b 02 00 00 00 c6 0c 00 00 .......[........
Windows has finished checking your disk.
Please wait while your computer restarts.
For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 3/27/2012
Time: 12:33:00 PM
User: N/A
Computer: KELLY-C8D55886B
Description:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 552 unused index entries from index $SII of file 0x9.
Cleaning up 552 unused index entries from index $SDH of file 0x9.
Cleaning up 552 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
488375968 KB total disk space.
9881192 KB in 36568 files.
11260 KB in 3270 indexes.
0 KB in bad sectors.
145880 KB in use by the system.
65536 KB occupied by the log file.
478337636 KB available on disk.
4096 bytes in each allocation unit.
122093992 total allocation units on disk.
119584409 allocation units available on disk.
Internal Info:
90 f4 00 00 aa 9b 00 00 1c bb 00 00 00 00 00 00 ................
56 00 00 00 00 00 00 00 34 08 00 00 00 00 00 00 V.......4.......
da 7f 2e 04 00 00 00 00 82 70 d2 12 00 00 00 00 .........p......
d0 01 30 0d 00 00 00 00 4a f1 b5 e5 00 00 00 00 ..0.....J.......
64 64 d8 0e 00 00 00 00 c6 b6 07 20 01 00 00 00 dd......... ....
00 56 21 83 00 00 00 00 10 3a 07 00 d8 8e 00 00 .V!......:......
00 00 00 00 00 a0 19 5b 02 00 00 00 c6 0c 00 00 .......[........
Windows has finished checking your disk.
Please wait while your computer restarts.
For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.
#7
Posted 27 March 2012 - 11:42 AM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
Well there is nothing wrong there as you will have seen please check device manager as explained
#8
Posted 27 March 2012 - 11:43 AM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
Here is the screen shot on device manager
#9
Posted 27 March 2012 - 11:48 AM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
forgot to show hidden files, here is the other view
#10
Posted 27 March 2012 - 11:49 AM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
Also please go device manager
and check for any warnings against any devices
Your audio driver is mentioned in crash dumps
On the view tab, click to shown hidden devices
Please either post details of the warnings with the error code OR send a screenshot
OR if you have the knowledge explore the warning and error code and take the appropriate action
as above please.
open the entry, please for the other device, video controller., what is shown, driver tab -
#11
Posted 27 March 2012 - 11:57 AM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
Sorry to waste your time... I have not done these types of things before. I will try to follow your instructions better.
Attached Thumbnails
#12
Posted 27 March 2012 - 12:22 PM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
NO Please you are not wasting my time.
We work on here because we enjoy it.
Does the monitor connect on the I/O plate near to the LAN USB etc or is it on a separate area lower down the case.
This will indicate if it is the integrated graphics on the board or a graphics card.
in the first instance try reinstall driver please for both.
Then if that does not put them back where they belong, rather then in other devices, as the entry for the VGA should be in display adaptor, please send me this
Please Run the PCPitstop.com OverDrive Full Tests
Here's how:
You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others).
Go to: http://www.pCPitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!" OR YOU CAN RUN THE TEST ANON. without signing up. - you will see that at the end of that screen. The results will still be saved long enough for me to look at them.
You'll need to submit a valid email address and create your own password, then click - Create Account(button)
Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.
The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed. PLEASE DO NOT TRY ANY UNTIL I HAVE HAD A LOOK
Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration.
Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.
While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.
We work on here because we enjoy it.
Does the monitor connect on the I/O plate near to the LAN USB etc or is it on a separate area lower down the case.
This will indicate if it is the integrated graphics on the board or a graphics card.
in the first instance try reinstall driver please for both.
Then if that does not put them back where they belong, rather then in other devices, as the entry for the VGA should be in display adaptor, please send me this
Please Run the PCPitstop.com OverDrive Full Tests
Here's how:
You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others).
Go to: http://www.pCPitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!" OR YOU CAN RUN THE TEST ANON. without signing up. - you will see that at the end of that screen. The results will still be saved long enough for me to look at them.
You'll need to submit a valid email address and create your own password, then click - Create Account(button)
Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.
The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed. PLEASE DO NOT TRY ANY UNTIL I HAVE HAD A LOOK
Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration.
Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.
While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.
#13
Posted 27 March 2012 - 03:26 PM
Klown1969
- Topic Starter
-
- Member
-
- 33 posts
Member
#14
Posted 27 March 2012 - 03:54 PM
Macboatmaster
-
- Member
-
- 7,237 posts
7k
While I read Pitstop
that was Pitstop so am I to presume it did not work please - if so what did it report please
Does the monitor connect on the I/O plate near to the LAN USB etc or is it on a separate area lower down the case.
This will indicate if it is the integrated graphics on the board or a graphics card.
in the first instance try reinstall driver please for both.
Then if that does not put them back where they belong, rather then in other devices, as the entry for the VGA should be in display adaptor, please send me this -
that was Pitstop so am I to presume it did not work please - if so what did it report please
#15
Posted 27 March 2012 - 04:08 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Macboatmaster the issue is she tries to install the driver from the motherboard drivers disk and the system on reboot goes into a loop. Even deleting the driver and rebooting the system cannot find the driver on the motherboard disk. Uninstalling does allow the system to boot into windows again though. As soon as you try to move the mouse though it reboots.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:
Sign In
Create Account
