1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

BSOD with Whocrashed report

Discussion in 'Windows 7' started by leneopen, Dec 5, 2011.

Thread Status:
Not open for further replies.
Advertisement
  1. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    Hi,
    its been weeks now i have daily crashes at any time without any reason, even when i'm not touching the computer, and it really got on my nerves of course, i tried memory tests with memtest, i tried remove 1 ram than the other one, i updated all my drivers, checked for viruses but nothing works and i cant figure it out, it started a month ago so here's my whocrashed reports, im crossing fingers will be able to help me to find the solution, thanks in advance,
    cheers,
    niko



    System Information (local)
    --------------------------------------------------------------------------------

    computer name: NEOPEN-STATION
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 8588353536 total
    VM: 2147352576, free: 1891512320



    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Mon 05-Dec-11 10:26:25 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120511-21964-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88008E310F0, 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.


    On Mon 05-Dec-11 10:22:18 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120511-21902-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFC9, 0x0, 0x1, 0xFFFFF800034D7530)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 Fri 02-Dec-11 11:28:27 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120211-22635-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 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.


    On Fri 02-Dec-11 11:28:27 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 Thu 01-Dec-11 0:13:32 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120111-24913-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1 (0x77CB141A, 0x0, 0xFFFF, 0xFFFFF88008EDDC60)
    Error: APC_INDEX_MISMATCH
    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 there has been a mismatch in the APC state index.
    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 30-Nov-11 22:57:27 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120111-25069-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFF5000F03C680, 0x2, 0x1, 0xFFFFF800034E3C1F)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 Wed 30-Nov-11 1:02:33 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\113011-21762-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80003516BD0)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 29-Nov-11 22:25:20 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112911-20155-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800037BB564, 0xFFFFF88003AFCE70, 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 Mon 28-Nov-11 2:00:07 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112811-21044-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800034D9B65, 0x0, 0xFFFFFFFFFFFFFFFF)
    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.


    On Sun 27-Nov-11 21:07:59 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112711-23150-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000349FA4C, 0xFFFFF88008931860, 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 Sat 26-Nov-11 21:30:03 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112611-20529-01.dmp
    This was probably caused by the following module: fltmgr.sys (fltmgr+0x2904)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800100D904, 0xFFFFF88009376E00, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Système d’exploitation Microsoft® Windows®
    company: Microsoft Corporation
    description: Gestionnaire de filtres de système de fichiers Microsoft
    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 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 25-Nov-11 22:06:51 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112511-21122-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFF88003015188, 0x0, 0xFFFFF8000376F567, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    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 Fri 25-Nov-11 18:30:28 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112511-19219-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFFFFFC084078D, 0x2, 0x1, 0xFFFFF8000349356E)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 24-Nov-11 17:40:31 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112411-22713-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2105B)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800431905B, 0xFFFFF88003C10658, 0xFFFFF88003C0FEB0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: This indicates that a system thread 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 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 24-Nov-11 6:16:07 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112411-19390-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFF3000DDFC021, 0x2, 0x1, 0xFFFFF8000350B57B)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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.



    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    33 crash dumps have been found and analyzed. Only 15 are included in this report.
    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.
     
  2. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    really ? nobody ?!
     
  3. Megabite

    Megabite

    Joined:
    Apr 5, 2008
    Messages:
    11,761
    Howdy,

    Do you have a dual boot on that system?

    Did you add anything just before the crashes?

    How old is the hard Drive?
     
  4. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    Hi,
    i dont have a dual boot, just win7, the hard drives arent very old, a year, i changed my ram around a month and a half ago so a lil before the problems started, but i did tests and checked the ram in a shop and they work well ... it could be a compatibility problem between my motherboard and the ram but i couldnt say actually:
    my motherboard is a gigabyte G41MT-D3 (chipset intel G41) and for the ram i have 2 Mushkin DD3 (8192Mb total) @533.3Mz ... max bandwith PC3-10700(667Mhz), i just wrote what i can see on CPU-Z freeware

    any idea ?! thx
     
  5. Megabite

    Megabite

    Joined:
    Apr 5, 2008
    Messages:
    11,761
    take a look and see if any minidumps have been created

    you will find them here They are located in C:\WINDOWS\Minidump

    Copy the last 3 to another location put them in a folder and compress the folder zip or Rar and Go Advanced in your post then Manage Attachments and post them

    Note Do not try to compress them until you have copied them to somewhere else.
     
  6. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    here's the last minidumps ...
     

    Attached Files:

  7. Megabite

    Megabite

    Joined:
    Apr 5, 2008
    Messages:
    11,761
    All those minidumps say Probably caused by : ntoskrnl.exe

    When you say "i changed my ram around a month and a half ago " did you just changed slots or add new memory?
     
  8. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    i had 2x2Go and i upgraded to 2x4Go actually
     
  9. Megabite

    Megabite

    Joined:
    Apr 5, 2008
    Messages:
    11,761
    was the ram speed the same?

    as a test I would put the old memory back and see if you have the same problem.
     
  10. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    yeah the ram speed the same, but i cant put the old memory back as i dont have it anymore but i'll try to find on the motherboard manufacturer if my model of ram is compatible, thanks a lot
     
  11. leneopen

    leneopen Thread Starter

    Joined:
    Dec 5, 2011
    Messages:
    7
    well it wasnt the ram, i changed it and still ahve the same problem,
    dont know if it helps but after it crash, on reboot, i usually ahve to turn it off few seconds first or at least wait the 30sec when windows ask me if i wanna start windows normally cause if i dont it crashed again before to arrive on the desktop ?!?
    it's not the alimentation cause it's a new one i bought around 5 months ago, a strong one, so i have no idea ?!
     
  12. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1029764

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice