BSOD has returned

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7
       #1

    BSOD has returned


    Hi all.

    I have had several problems with my new rig, and now they are back. I am getting random BSOD's with various error codes. I have tried changing my gfx board, tried changing ram, triedf changing sounboards. I have also tried reinstalling and tried removing/changing mouse and keyboard. The only things remaining that I have not vhanged, are the CPU, PSU, mobo and HD.

    Have run memtest86 without problems overnight, chkdisk, and also have run prime95 (and a gfx intensive test program at the same time) for several hours without problems. Also updated BIOS and all drivers.

    So I thought that my problems dissapeared when I reinstalled Win7 some weeks ago, but now they seem to have returned.

    Attaching dump files, I have no idea how to analyze them myself, so hopefully you can make something out of it.

    EDIT: I am running a win7 proffessional 64bit OS
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    hardkjerne said:
    Hi all.

    I have had several problems with my new rig, and now they are back. I am getting random BSOD's with various error codes. I have tried changing my gfx board, tried changing ram, triedf changing sounboards. I have also tried reinstalling and tried removing/changing mouse and keyboard. The only things remaining that I have not vhanged, are the CPU, PSU, mobo and HD.

    Have run memtest86 without problems overnight, chkdisk, and also have run prime95 (and a gfx intensive test program at the same time) for several hours without problems. Also updated BIOS and all drivers.

    So I thought that my problems dissapeared when I reinstalled Win7 some weeks ago, but now they seem to have returned.

    Attaching dump files, I have no idea how to analyze them myself, so hopefully you can make something out of it.

    EDIT: I am running a win7 proffessional 64bit OS

    I hate to tell you but the DMP I analyzed was caused by pool corruption and had a 24 bugcheck. The
    Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

    I see you have run memtest but wonder for how many passes and if it was one stick at a time. did you also test eash mobo slot with known good ram?

    I would also run a chkdsk
    CHKDSK /R /F:
    Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

    Elevated Command Prompt:
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

    CHKDSK LogFile:
    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post.

    Remove your AV and replace with Microsoft security essentials

    Run a system file check to verify and repair your system files.
    To do this type cmd in search, then right click to run as administrator, then
    SFC /SCANNOW

    Let us know the results from the report at the end.

    Ken




    Analysis
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\New folder\081910-25334-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03016000 PsLoadedModuleList = 0xfffff800`03253e50
    Debug session time: Wed Aug 18 18:58:35.316 2010 (GMT-4)
    System Uptime: 3 days 13:09:02.875
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff88009658c28, fffff88009658490, fffff800031b9f8c}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
    
    Followup: Pool_corruption
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff88009658c28
    Arg3: fffff88009658490
    Arg4: fffff800031b9f8c
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff88009658c28 -- (.exr 0xfffff88009658c28)
    ExceptionAddress: fffff800031b9f8c (nt!ExDeferredFreePool+0x0000000000000100)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff88009658490 -- (.cxr 0xfffff88009658490)
    rax=fffffa800fbcc620 rbx=0000000000000000 rcx=fffff80003215a00
    rdx=ff00fa800fbcc4d0 rsi=0000000000000000 rdi=fffffa800e70f010
    rip=fffff800031b9f8c rsp=fffff88009658e60 rbp=0000000000000000
     r8=ff00fa800fbcc4d0  r9=0000000000000000 r10=fffff80003215888
    r11=0000000000000000 r12=fffff80003215880 r13=0000000000000000
    r14=0000000000000002 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!ExDeferredFreePool+0x100:
    fffff800`031b9f8c 4c8b02          mov     r8,qword ptr [rdx] ds:002b:ff00fa80`0fbcc4d0=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  WerFault.exe
    
    CURRENT_IRQL:  2
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032be0e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+100
    fffff800`031b9f8c 4c8b02          mov     r8,qword ptr [rdx]
    
    FAULTING_IP: 
    nt!ExDeferredFreePool+100
    fffff800`031b9f8c 4c8b02          mov     r8,qword ptr [rdx]
    
    BUGCHECK_STR:  0x24
    
    LAST_CONTROL_TRANSFER:  from fffff800031bb4c1 to fffff800031b9f8c
    
    STACK_TEXT:  
    fffff880`09658e60 fffff800`031bb4c1 : 00000000`00000100 fffffa80`0fbcc660 00000000`00000000 fffff800`03212d40 : nt!ExDeferredFreePool+0x100
    fffff880`09658ef0 fffff800`032e63fb : fffffa80`09d42b10 fffffa80`0fbcc6b8 fffffa80`6c526d4d 00000000`000007ff : nt!ExFreePoolWithTag+0x411
    fffff880`09658fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x3896e
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExDeferredFreePool+100
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: Pool_Corruption
    
    STACK_COMMAND:  .cxr 0xfffff88009658490 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x24_nt!ExDeferredFreePool+100
    
    BUCKET_ID:  X64_0x24_nt!ExDeferredFreePool+100
    
    Followup: Pool_corruption
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff88009658c28
    Arg3: fffff88009658490
    Arg4: fffff800031b9f8c
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff88009658c28 -- (.exr 0xfffff88009658c28)
    ExceptionAddress: fffff800031b9f8c (nt!ExDeferredFreePool+0x0000000000000100)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff88009658490 -- (.cxr 0xfffff88009658490)
    rax=fffffa800fbcc620 rbx=0000000000000000 rcx=fffff80003215a00
    rdx=ff00fa800fbcc4d0 rsi=0000000000000000 rdi=fffffa800e70f010
    rip=fffff800031b9f8c rsp=fffff88009658e60 rbp=0000000000000000
     r8=ff00fa800fbcc4d0  r9=0000000000000000 r10=fffff80003215888
    r11=0000000000000000 r12=fffff80003215880 r13=0000000000000000
    r14=0000000000000002 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!ExDeferredFreePool+0x100:
    fffff800`031b9f8c 4c8b02          mov     r8,qword ptr [rdx] ds:002b:ff00fa80`0fbcc4d0=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  WerFault.exe
    
    CURRENT_IRQL:  2
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS:  ffffffffffffffff 
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+100
    fffff800`031b9f8c 4c8b02          mov     r8,qword ptr [rdx]
    
    FAULTING_IP: 
    nt!ExDeferredFreePool+100
    fffff800`031b9f8c 4c8b02          mov     r8,qword ptr [rdx]
    
    BUGCHECK_STR:  0x24
    
    LAST_CONTROL_TRANSFER:  from fffff800031bb4c1 to fffff800031b9f8c
    
    STACK_TEXT:  
    fffff880`09658e60 fffff800`031bb4c1 : 00000000`00000100 fffffa80`0fbcc660 00000000`00000000 fffff800`03212d40 : nt!ExDeferredFreePool+0x100
    fffff880`09658ef0 fffff800`032e63fb : fffffa80`09d42b10 fffffa80`0fbcc6b8 fffffa80`6c526d4d 00000000`000007ff : nt!ExFreePoolWithTag+0x411
    fffff880`09658fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x3896e
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExDeferredFreePool+100
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: Pool_Corruption
    
    STACK_COMMAND:  .cxr 0xfffff88009658490 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x24_nt!ExDeferredFreePool+100
    
    BUCKET_ID:  X64_0x24_nt!ExDeferredFreePool+100
    
    Followup: Pool_corruption
    ---------

    Old drivers needing update
    Code:
    GVTDrv64.sys        fffff880`057db000    fffff880`057e5000    0x0000a000    0x44fd22ca    9/5/2006 03:10:02                        
    Rt64win7.sys        fffff880`13e00000    fffff880`13e32000    0x00032000    0x49a65b0d    2/26/2009 05:04:13                        
    gdrv.sys        fffff880`05bf7000    fffff880`05c00000    0x00009000    0x49b9d175    3/12/2009 23:22:29                        
    AtiPcie.sys        fffff880`01840000    fffff880`01848000    0x00008000    0x4a005486    5/5/2009 11:00:22                        
    spldr.sys        fffff880`015f0000    fffff880`015f8000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
    spsys.sys        fffff880`04570000    fffff880`045e1000    0x00071000    0x4a085e7a    5/11/2009 13:20:58                        
    amdxata.sys        fffff880`00e33000    fffff880`00e3e000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      My Computer


  3. Posts : 17,796
    Windows 10, Home Clean Install
       #3

    I found information for some drivers

    Rt64win7.sys file description
    Productname: Realtek 8136/8168/8169 PCI/PCIe Adapters
    Description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
    Company: Realtek


    Gdrv.sys file description
    Productname: Windows (R) Server 2003 DDK driver
    Description: GIGABYTE Tools
    Company: Windows (R) Server 2003 DDK provider


    Atipcie.sys file description
    Productname: AMD PCIE Filter Driver
    Description: AMD PCIE Filter Driver for ATI PCIE chipset
    Company: Advanced Micro Devices Inc.


    Amdxata.sys file description
    Productname: Stor Filter Driver
    Description: Stor Filter Driver
    Company: Advanced Micro D

    SPLDR is a driver from Microsoft, I would ignore that one for now.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Rich just some generic finding driver info Im sure you have but just in case

    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      My Computer


  5. Posts : 8
    Windows 7
    Thread Starter
       #5

    Thanks for the reply's. Will test this when I get back from work.

    About the memory, I have tested running single chip (switched around). I also bought a second set of 2 x 2gb sticks (from a different manufacturer (already had Mushkin, bought OCZ) and ran them alone as well without any difference in BSOD frequency. The memtest86 was running at least for 8-9 hours (had it on overnight).

    Also, one thing I forgot to mention is that sometimes when the "BSOD hell" has started, it seems to pick up in frequency. Sometimes this might result in many successive BSOD's and sometimes even culminating in 3 long beeps when rebooting (from my mobo manual this seems to be GFX related, somting like: GFX board not properly installed). The 3 long beeps has been experienced at some point with 3 different GFX boards, so I don't expect that to be the reason.

    I am suspecting that it might be a faulty PSU since the BSOD frequency sometimes peaks without any (as far as I can see) actions that seem to bee triggering it. Also, when it comes to heat inside my computer this is (according to speedfan) not a problem. Also tried with a open cabinet door without any difference.
      My Computer


  6. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #6

    Can you borrow another PSU to try?

    Do keep in mind that outdated drivers can and do cause crashes - especially that 2006 driver. That one is way obsolete for Win 7.
      My Computer


  7. Posts : 8
    Windows 7
    Thread Starter
       #7

    Tested with a new PSU and got a new BSOD after it ran stable through the night. The BSOD came actually when I tried to stream a video from my machine (using the PS3 media server software). This leads mer to beleave that it might either be a disk related problem (thoug the disk containing the video is brand new and has been introduced after the BSOD's started) or something with my NIC (using wired, not wireless). This sound plausible? THis made me at least look for a new driver version of Rt64win7.sys as I understand this is my NIC driver. Updated it to a brand new one dl'ed here: Realtek


    Also, I uninstalled Easytune trying to get rid of GVTDrv64.sys as well.

    Hope this will help me get rid of the BSOD's. Will update the thread.
      My Computer


  8. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #8

    Yes, it does sound plausible. Good detective work and good job of following through. I hope this cures your problems. Thanks for the update.
      My Computer


  9. Posts : 8
    Windows 7
    Thread Starter
       #9

    So, got some new BSOD today

    Anything new in the dumps?
      My Computer


  10. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #10

    All three dumps show c0000005 which is memory corruption. You have two dumps with an error code of 3B and one with 1E.

    Error code 3B - BSOD Index

    Error code 1E- BSOD Index

    Code:
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff8000308d905, fffff88008b6fb10, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8000308d905, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88008b6fb10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!ExpInterlockedPopEntrySListFault16+0
    fffff800`0308d905 498b08          mov     rcx,qword ptr [r8]
    
    CONTEXT:  fffff88008b6fb10 -- (.cxr 0xfffff88008b6fb10)
    rax=0000001bd7970000 rbx=0000000000000000 rcx=fffffa8006bbeb70
    rdx=00ff000000000001 rsi=000000000000000b rdi=0000000000000000
    rip=fffff8000308d905 rsp=fffff88008b704e0 rbp=00000000000003e8
     r8=00ff000000000000  r9=fffffa800c6816a0 r10=fffffa8006bbeb70
    r11=fffffa800c312e90 r12=fffffa8006bbeb70 r13=00000000000003e8
    r14=0000000000000002 r15=fffffa800c681604
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210206
    nt!ExpInterlockedPopEntrySListFault16:
    fffff800`0308d905 498b08          mov     rcx,qword ptr [r8] ds:002b:00ff0000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  mencoder_mt.ex
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8000308d905
    
    STACK_TEXT:  
    fffff880`08b704e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
    
    
    FOLLOWUP_IP: 
    nt!ExpInterlockedPopEntrySListFault16+0
    fffff800`0308d905 498b08          mov     rcx,qword ptr [r8]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    STACK_COMMAND:  .cxr 0xfffff88008b6fb10 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
    
    BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
    
    Followup: MachineOwner
    ---------
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff800030cf9cd, 0, ffffffffffffffff}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+20d )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800030cf9cd, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!KiCommitThreadWait+20d
    fffff800`030cf9cd c3              ret
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033000e0
     ffffffffffffffff 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  WMIADAP.exe
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff8800983f938 -- (.exr 0xfffff8800983f938)
    ExceptionAddress: fffff800030cf9cd (nt!KiCommitThreadWait+0x000000000000020d)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000008
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff8800983f9e0 -- (.trap 0xfffff8800983f9e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000102 rbx=0000000000000000 rcx=0000000000000000
    rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030cf9cd rsp=fffff8800983fb78 rbp=fffffa800b14b588
     r8=fffffa8006dbbb28  r9=0000000000000000 r10=fffffffffffffffb
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!KiCommitThreadWait+0x20d:
    fffff800`030cf9cd c3              ret
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003102a39 to fffff800030c8740
    
    STACK_TEXT:  
    fffff880`0983f168 fffff800`03102a39 : 00000000`0000001e ffffffff`c0000005 fffff800`030cf9cd 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0983f170 fffff800`030c7d82 : fffff880`0983f938 00000000`dc549b18 fffff880`0983f9e0 00000000`00000000 : nt!KiDispatchException+0x1b9
    fffff880`0983f800 fffff800`030c668a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    fffff880`0983f9e0 fffff800`030cf9cd : effff800`030d197a 00000000`00000000 00000000`00000170 00000000`0000008f : nt!KiGeneralProtectionFault+0x10a
    fffff880`0983fb78 effff800`030d197a : 00000000`00000000 00000000`00000170 00000000`0000008f 00000000`000fef00 : nt!KiCommitThreadWait+0x20d
    fffff880`0983fb80 00000000`00000000 : 00000000`00000170 00000000`0000008f 00000000`000fef00 ffffd30b`1db07e0a : 0xeffff800`030d197a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiCommitThreadWait+20d
    fffff800`030cf9cd c3              ret
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!KiCommitThreadWait+20d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0x1E_nt!KiCommitThreadWait+20d
    
    BUCKET_ID:  X64_0x1E_nt!KiCommitThreadWait+20d
    
    Followup: MachineOwner
    ---------
    Something is causing memory corruption. Usually this is a driver issue; but it could be bad RAM, incompatible software or or hardware, etc. All three of your dumps shows ctac32k.sys as an unloaded module. I cannot find the date of this driver; but related drivers on your system are out of date.

    ctac32k.sys - Creative AC3 SW Decoder Device Driver (WDM) belongs to the software Creative AC3 Software Decoder or Creative Audio Product by Creative Technology Ltd (www.creative.com).

    CT20XUT.DLL Wed Jun 17 01:00:53 2009 - is related to Creative Audio Product. Manufacturer: Creative Technology

    ctaud2k.sys - Creative WDM Audio Device Driver belongs to the software Creative Audio Driver (WDM) by Creative Technology Ltd (www.creative.com).

    CTHWIUT.DLL - is related to Creative Utility effects. Manufacturer: Creative Technology Ltd.

    ctoss2k.sys Wed Jun 17 00:57:34 2009 - Creative OS Services Driver (WDM) belongs to the software Creative OS Services Driver or Creative Audio Product by Creative Technology Ltd (www.creative.com).

    ctprxy2k.sys Wed Jun 17 00:59:38 2009 - Creative Proxy Device Driver (WDM) belongs to the software Creative Audio Product or Creative Proxy Driver by Creative Technology Ltd (www.creative.com).

    ctsfm2k.sys Wed Jun 17 00:57:21 2009 - SoundFont(R) Manager (WDM) belongs to the software Creative SoundFont Management Device Driver by Creative Technology Ltd (www.creative.com).

    I recommend you update these drivers or consider upgrading your sound card.

    To cover all possibilities, are you overclocking anything? If so please return to default values. Please run Memtest86+: RAM - Test with Memtest86+. Post back with your results.

    The following drivers, in addition to your Creative sound drivers, are out of date. Out of date drivers can and do cause conflicts and memory corruption. The 2007 driver is way out of date.
    emupia2k.sys Wed Jun 17 00:57:13 2009
    ha20x2k.sys Wed Jun 17 00:58:58 2009
    lmimirr.sys Tue Apr 10 18:32:45 2007

    If you need help finding these, drivers please post.

      My Computer


 
Page 1 of 2 12 LastLast

  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 08:32.
Find Us