BSOD Win XP 64 Bit Random Crashing "Multi Bugcheck Codes"


  1. Posts : 10
    Windows 7 Pro 64bit
       #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
      My Computer


  2. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #2

    Hi talas9 welcome to SevenForums

    Try to update your SSD firmware .

       Tip
    You do NOT want to Defrag an SSD drive . No need to.


       Tip
    I'd personally upgrade to Windows 7 . So you could really get the speed of the SSD drive
      My Computer


  3. Posts : 10
    Windows 7 Pro 64bit
    Thread Starter
       #3

    Actually I already know that it doesn't make sense to defrag a SSD, But when you stuck with some issue you will try everything even if it's useless,

    Can i know how to update SSD Firmware if it's attached to JMicron Raid Controller?
      My Computer


  4. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #4

    What is the manufacture and model of the SSD drive ?
      My Computer


  5. Posts : 10
    Windows 7 Pro 64bit
    Thread Starter
       #5

    It's Patriot Pyro (Screenshot Attached)
      My Computer


  6. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #6

    Patriot Pyro SSD update Software


    Download



    Patriot Pyro SSD 60GB firmware


    Download



       Note

    Release Date : 05/02/2012
    Rev. 5.0.2
    Fixes:
    - Added Nand Support
    - Updated SMART and Log Support
    - Improved hardware handling
    - Improved internal read buffering
    - Improved block count management
    - Improved Power Management
      My Computer


  7. Posts : 10
    Windows 7 Pro 64bit
    Thread Starter
       #7

    I found the Software to upgrade Patriot Pyro SSD 60GB here:
    http://www.patriotmemory.com/softwar...SD_Updater.zip


    And the latest firmware is here:
    05/02/2012 5.0.2 Release Notes
    http://www.patriotmemory.com/softwar..._PSE_5_0_2.zip

    I'll try to upgrade the firmware

    Thank you for really fast response
      My Computer


  8. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #8

    You're welcome
      My Computer


  9. Posts : 10
    Windows 7 Pro 64bit
    Thread Starter
       #9

    Actually i was unable to update the firmware because of some silly error message in the update application, and after searching the web i found that most of the users of this model facing the same issue with updating the firmware, and the support team of this brand are not reponding,

    Sorry just wanted to ask if you are pretty sure that upgrading the firmware will solve the issue.


    thanks in advance.
      My Computer


  10. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #10

    It's a start . Some of the BSODs on an SSD is due to outdated firmware .
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:31.
Find Us