Many dump files help!


  1. Posts : 37
    Windows 7 Utimate 64bit edition
       #1

    Many dump files help!


    Hi everyone,

    I have no idea whats going on but my computer seems to like to crash. I did do a memory scan for a few hours (memtest v4.0) an no errors were found.

    I have a vast collection of dump files to look at. I would appreciate you to look at thm and tell me what you think.

    I thought it was my nvidea driver so i unistalled it and used driver cleaner and re-installed the newest diver but the problem still persists. I don't think it's ram but, it could be...

    If you could look at the newer dump files I would appreciate it alot.

    Thanks

    There are about 8 dump files I saved so maybe have a better chance understanding the issue.
      My Computer


  2. Posts : 1,083
    Windows 7 Enterprise 64-bit
       #2

    These are all memory-related issues. I would highly recommend running Memtest86 to test for faulty RAM.

    On Tue 3/23/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xA (0xFFFFFB8008E8687B, 0x2, 0x0, 0xFFFFF8000328B363)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\032310-25303-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Tue 3/23/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1A (0x41284, 0xFFFFF900C28A8001, 0x2CDF, 0xFFFFF90000812000)
    Error: MEMORY_MANAGEMENT
    Dump file: C:\Windows\Minidump\032310-25038-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Tue 3/23/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000149F72, 0xFFFFF88007450E20, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    Dump file: C:\Windows\Minidump\032310-23649-01.dmp
    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 the culprit is in another driver on your system which cannot be identified at this time.
    On Sun 3/21/2010 11:04:14 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003318E89, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\032110-27799-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Sun 3/21/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002F8ADB0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    Dump file: C:\Windows\Minidump\032110-23431-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Sat 3/20/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x19 (0x22, 0xFFFFFA8006DD4000, 0x0, 0x0)
    Error: BAD_POOL_HEADER
    Dump file: C:\Windows\Minidump\032010-21715-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Sat 3/20/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xA (0x200000000000, 0x2, 0x1, 0xFFFFF800032FDC22)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\032010-24788-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Sat 3/20/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x50 (0xFFFFF6D00003DCB8, 0x0, 0xFFFFF80003392275, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\032010-30264-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
    On Wed 3/17/2010 11:04:13 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xA (0xFFFFFB80106F99C8, 0x2, 0x1, 0xFFFFF8000328D632)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\031710-25609-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
      My Computer


  3. Posts : 37
    Windows 7 Utimate 64bit edition
    Thread Starter
       #3

    just ran windows 7 mem test and no errors were found.

    Going to try memtest86 v4.0 agian...how long should I let it run for last time I ran it for 2 hours.. no errors were found.

    Could this be a chipset issue?
      My Computer


  4. Posts : 1,083
    Windows 7 Enterprise 64-bit
       #4
      My Computer


  5. Posts : 37
    Windows 7 Utimate 64bit edition
    Thread Starter
       #5

    I use malewarebytes + spybot s&d + avg free 9 + super anti spyware + CW shredder weekly. so I'm positive it is not spyware or maleware, I keep my computer free of that.

    I did though have sound problems and other little things that i kind of messed with when i installed windows 7. And no I refuse to do another clean sweep(i already did about 4 of them), because after I re-install there are to many little problems that I need to fix...and when I fix one anouther seems to pop up.

    examples of things I have fixed after installing windows:


    hyperthreading was not reconzided by windows..it was windows not bois.
    no volume on any flash video(youtube ect.)
    the 4g usable of 6 gigs of ram issue
    windows sfc /scannow not repairing files.
    windows not booting
    chkdsk unable to read hard drive..

    just to name a few... so I will not go through all that crap agian.


    I'm currently re-running memtest86 v4.0 and so far no memory issues. Is it possible that maybe my chipset driver is incorrect? or maybe one of the sound drivers?
      My Computer


  6. Posts : 1,083
    Windows 7 Enterprise 64-bit
       #6

    A driver is most likely at fault here. I'd definitely take a look at your chipset drivers if sound is an issue in addition to everything you've mentioned.
      My Computer


  7. Posts : 37
    Windows 7 Utimate 64bit edition
    Thread Starter
       #7

    4.5 hours straight 4.5 full passes on memtest86 v4.0 with zero errors.

    Anyone else that can read these dump files have an idea?
      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 14:34.
Find Us