New
#1
BSOD Win XP 64 Bit Random Crashing "Multi Bugcheck Codes"
Hi,
This is my first post in this forum, actually i found that this is the most helpful forum all over the net,
Anyway I need a little help solving this BSOD issue please,
My PC is crashing randomly when I'm away and getting BSOD, with the following errors,
I tried to run "Disk Defragmenter", "Disk Scan" and "sfc /scannow" with no results,
My Hard Drive is an SSD with the capacity of 60GB and I have four Additional hard drives each two create a "RAID 1", I'm getting the BSOD randomly and with out running any application, I tried to update all Intel drivers in my machine and "Jmicron Raid" as well with no hope ,
and here is "Who crashed" Log:
====================================================================
System Information (local)
--------------------------------------------------------------------------------
computer name: USER-
windows version: Windows XP x64 Service Pack 2, 5.2, build: 3790
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12875243520 total
VM: 2147352576, free: 2000760832
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 3/26/2013 7:08:01 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032713-01.dmp
uptime: 06:46:14
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800011A9B28, 0xFFFFFADEBC1C1070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 3/24/2013 6:56:52 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032513-01.dmp
uptime: 12:21:52
This was probably caused by the following module: ntfs.sys (Ntfs+0xF87B)
Bugcheck code: 0x24 (0x19033D, 0xFFFFFADEC2E8C360, 0xFFFFFADEC2E8BD70, 0xFFFFFADEC202C9ED)
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.
Google query: ntfs.sys Microsoft Corporation NTFS_FILE_SYSTEM
On Tue 3/19/2013 1:31:33 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032413-01.dmp
uptime: 12:18:46
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x4E (0x2, 0x2F1960, 0x33FFFF, 0x1)
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 Thu 3/7/2013 9:01:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030713-05.dmp
uptime: 01:07:29
This was probably caused by the following module: ntfs.sys (Ntfs+0xF87B)
Bugcheck code: 0x24 (0x19033D, 0xFFFFFADEF0719090, 0xFFFFFADEF0718AA0, 0xFFFFF800010449FB)
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.
Google query: ntfs.sys Microsoft Corporation NTFS_FILE_SYSTEM
On Thu 3/7/2013 7:48:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030713-04.dmp
uptime: 00:40:23
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800011A9B28, 0xFFFFFADEF0757250, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 3/7/2013 5:02:59 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030713-03.dmp
uptime: 00:03:07
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0xC2 (0x44, 0x80000000000000, 0xFFFF080000000000, 0x0)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Thu 3/7/2013 4:58:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030713-02.dmp
uptime: 00:31:01
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x1E (0xFFFFFFFFC000009A, 0xFFFFF80001055209, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini030713-01.dmp
=====================================================================
And the SF Debug Logfile is attached,
Thank you.
Last edited by talas9; 31 Mar 2013 at 05:12. Reason: Enhancing the Title