BSOD from win32k.sys

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by natewin7user, Jul 23, 2011.

  1. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    I've been wrestling with this error now for a few days. I've had multiple crashes for the last few days and I can't seem to figure out what else to do. I just clean installed windows 7 pro x64 and since then I have been having issues. I have clean installed my nForce drivers for ethernet and also my graphics drivers (using a driver cleaner). At this point I just don't have the knowledge to really pull more info from the dump files so here are my dump files. Any assistance or ideas would be helpful at this point.
     

    Attached Files:

  2. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    Hi natewin7user,

    Can you please upload the actual .dmp in a zipped file.

    STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
    Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

    STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
    Usual causes: System service, Device driver, graphics driver, ?memory.
     
    #2 Elmer, Jul 23, 2011
    Last edited: Jul 23, 2011
  3. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    Your request has been attached. :)
     

    Attached Files:

  4. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    Ok, first thing to do is update this driver:

    ASACPI.sys Mon Mar 28 03:30:36 2005 This driver is notorious for causing BSOD's. You have two options:
    • You can disable the ATK0110 ACPI Utility in the DeviceManager (under System Devices) with no apparent issues. OR (and if the above does cause issues)
    • There is an update here: Asus ATK0110 driver. Look under the sub-heading: Utilities. Approx. 12th one down.
    Driver Install - Manual method

    1. Download the driver and extract it to a folder.
    2. Open the Device Manager.
    3. Right click the device you wish to change the drivers for. You can select Properties > Driver > Driver Details to check you have the right device. In this case System Devices >> ATK0110 ACPI Utility
    4. Choose Update Driver Software.
    5. Select Browse My Computer For Driver Software.
    6. Select Let me pick from a list of device drivers on my computer.
    7. Select Have disk...
    8. Select Browse..
    9. Navigate to the extracted folder and double click on the .inf file
    10. Hit OK, then Next and the driver(s) will then begin to install.
    11. After it has installed, GoTo C:\Windows\System32\Drivers. Locate the Asacpi.sys driver, right click it and check the dates under its properties. You're looking for a "Modified" date of 2009 or 2010. Occasionally it can be a bit stubborn to change.



    I'll update this post after I've been through your dump files.

    HTH
     
    #4 Elmer, Jul 23, 2011
    Last edited: Jul 23, 2011
  5. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    Thanks for that I forgot about the issue with that file. I have updated it and it's now labeled as today's date 7/23/2011. I will await your further analysis of the dump files.
     
  6. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
    usual causes:
    System service, Device driver, graphics driver, ?memory.

    Your latest dump file lists win32k.sys as the probable cause. This is a Windows System file and for it to be the cause of your crash is highly unlikely.

    As a Priority:

    Turn off Driver Verifier.

    To turn off Driver Verifier when finished, Open a Command Prompt or Run... window and type verifier /reset and press Enter/OK.
    or
    GoTo Start and in the Search or a Run... Window type verifier. Select Delete existing settings and press Finish.

    Drivers with Updates:

    nvmf6264.sys Wed Nov 11 23:16:48 2009 nVidia nForce network driver

    Just check the modified date and/or the created date of the ASACPI.SYS driver. If it's 2005 it hasn't changed. If 2009 or 2010 it has and ignore this!!

    Everything else looking pretty good. If you are into a bit of self analysis Here's a link to a BSOD Codes Index. And here's a Driver Reference list.

    I'd also suggest updating to SP1 which will update some of your system drivers.

    Bugcheck Analysis:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff96000168094, fffff88003466c90, 0}
    
    Probably caused by : win32k.sys ( win32k!ProcessMouseInput+f8 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: fffff96000168094, Address of the instruction which caused the bugcheck
    Arg3: fffff88003466c90, 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: 
    win32k!ProcessMouseInput+f8
    fffff960`00168094 f6430204        test    byte ptr [rbx+2],4
    
    CONTEXT:  fffff88003466c90 -- (.cxr 0xfffff88003466c90)
    rax=0000000000000018 rbx=0000000000000000 rcx=fffff900c01f9154
    rdx=0000000000000018 rsi=fffff900c01f90b0 rdi=0000000000000018
    rip=fffff96000168094 rsp=fffff88003467660 rbp=00000000002f8b1f
     r8=000000000000000d  r9=000000000000000e r10=fffff80002c02000
    r11=fffff88003467560 r12=0200000000000000 r13=0000000000000000
    r14=fffffa8006affb30 r15=fffff88003467c20
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    win32k!ProcessMouseInput+0xf8:
    fffff960`00168094 f6430204        test    byte ptr [rbx+2],4 ds:002b:00000000`00000002=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000168094
    
    STACK_TEXT:  
    fffff880`03467660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!ProcessMouseInput+0xf8
    
    
    FOLLOWUP_IP: 
    win32k!ProcessMouseInput+f8
    fffff960`00168094 f6430204        test    byte ptr [rbx+2],4
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  win32k!ProcessMouseInput+f8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4df2d94e
    
    STACK_COMMAND:  .cxr 0xfffff88003466c90 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_VRF_win32k!ProcessMouseInput+f8
    
    BUCKET_ID:  X64_0x3B_VRF_win32k!ProcessMouseInput+f8
    
    Followup: MachineOwner
    Drivers:
    Code:
    fffff880`00f22000 fffff880`00f79000   ACPI     ACPI.sys     Tue Jul 14 00:19:34 2009 (4A5BC106)
    fffff880`03cf8000 fffff880`03d81000   afd      afd.sys      Mon Apr 25 03:43:58 2011 (4DB4DFEE)
    fffff880`0425e000 fffff880`04274000   AgileVpn AgileVpn.sys Tue Jul 14 01:10:24 2009 (4A5BCCF0)
    fffff880`03f15000 fffff880`03f2c000   amdk8    amdk8.sys    Tue Jul 14 00:19:25 2009 (4A5BC0FD)
    fffff880`010d7000 fffff880`010e2000   amdxata  amdxata.sys  Fri Mar 19 16:18:18 2010 (4BA3A3CA)
    fffff880`04246000 fffff880`0424e000   ASACPI   ASACPI.sys   Mon Mar 28 03:30:36 2005 (42476C4C)
    fffff880`05bea000 fffff880`05bf5000   asyncmac asyncmac.sys Tue Jul 14 01:10:13 2009 (4A5BCCE5)
    fffff880`00e63000 fffff880`00e6c000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`00dbf000 fffff880`00de9000   ataport  ataport.SYS  Tue Jul 14 00:19:52 2009 (4A5BC118)
    fffff880`01833000 fffff880`0183a000   Beep     Beep.SYS     Tue Jul 14 01:00:13 2009 (4A5BCA8D)
    fffff880`03ede000 fffff880`03eef000   blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF)
    fffff880`050ca000 fffff880`050e8000   bowser   bowser.sys   Wed Feb 23 05:15:06 2011 (4D6497DA)
    fffff880`04aba000 fffff880`04aca000   BthEnum  BthEnum.sys  Tue Jul 14 01:06:52 2009 (4A5BCC1C)
    fffff880`04aca000 fffff880`04aea000   bthpan   bthpan.sys   Tue Jul 14 01:07:00 2009 (4A5BCC24)
    fffff880`04a02000 fffff880`04a8e000   bthport  bthport.sys  Thu Apr 28 04:58:42 2011 (4DB8E5F2)
    fffff880`04865000 fffff880`0487d000   BTHUSB   BTHUSB.sys   Thu Apr 28 04:58:34 2011 (4DB8E5EA)
    fffff880`04852000 fffff880`04863000   btusbflt btusbflt.sys Fri Apr 09 02:11:36 2010 (4BBE7EC8)
    fffff960`006b0000 fffff960`006d7000   cdd      cdd.dll      Wed Jan 26 06:31:34 2011 (4D3FBFC6)
    fffff880`01800000 fffff880`0182a000   cdrom    cdrom.sys    Tue Jul 14 00:19:54 2009 (4A5BC11A)
    fffff880`00cd5000 fffff880`00d95000   CI       CI.dll       Tue Jul 14 02:32:13 2009 (4A5BE01D)
    fffff880`01966000 fffff880`01996000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E)
    fffff880`00c77000 fffff880`00cd5000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`0115c000 fffff880`011cf000   cng      cng.sys      Tue Jul 14 00:49:40 2009 (4A5BC814)
    fffff880`0424e000 fffff880`0425e000   CompositeBus CompositeBus.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1)
    fffff880`049aa000 fffff880`049b8000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
    fffff880`03e3d000 fffff880`03ec0000   csc      csc.sys      Tue Jul 14 00:24:26 2009 (4A5BC22A)
    fffff880`03ec0000 fffff880`03ede000   dfsc     dfsc.sys     Wed Apr 27 03:57:39 2011 (4DB78623)
    fffff880`03ca6000 fffff880`03cb5000   discache discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E)
    fffff880`01950000 fffff880`01966000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`04955000 fffff880`04977000   drmk     drmk.sys     Tue Jul 14 02:01:25 2009 (4A5BD8E5)
    fffff880`049b8000 fffff880`049c2000   dump_diskdump dump_diskdump.sys Fri Apr 22 19:11:55 2011 (4DB1C4EB)
    fffff880`0483f000 fffff880`04852000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
    fffff880`04800000 fffff880`0483f000   dump_nvstor64 dump_nvstor64.sys Fri Apr 09 10:22:41 2010 (4BBEF1E1)
    fffff880`04b54000 fffff880`04b60000   Dxapi    Dxapi.sys    Tue Jul 14 00:38:28 2009 (4A5BC574)
    fffff880`042f7000 fffff880`043eb000   dxgkrnl  dxgkrnl.sys  Wed Jan 26 04:22:56 2011 (4D3FA1A0)
    fffff880`04200000 fffff880`04246000   dxgmms1  dxgmms1.sys  Wed Jan 26 04:22:12 2011 (4D3FA174)
    fffff880`03f2c000 fffff880`03f39000   fdc      fdc.sys      Tue Jul 14 01:00:54 2009 (4A5BCAB6)
    fffff880`0112e000 fffff880`01142000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
    fffff880`0fe55000 fffff880`0fe60000   flpydisk flpydisk.sys Tue Jul 14 01:00:54 2009 (4A5BCAB6)
    fffff880`010e2000 fffff880`0112e000   fltmgr   fltmgr.sys   Tue Jul 14 00:19:59 2009 (4A5BC11F)
    fffff880`011e0000 fffff880`011ea000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
    fffff880`01916000 fffff880`01950000   fvevol   fvevol.sys   Sat Sep 26 03:34:26 2009 (4ABD7DB2)
    fffff880`0158a000 fffff880`015d4000   fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164)
    fffff800`031de000 fffff800`03227000   hal      hal.dll      Tue Jul 14 02:27:36 2009 (4A5BDF08)
    fffff880`03e00000 fffff880`03e24000   HDAudBus HDAudBus.sys Tue Jul 14 01:06:13 2009 (4A5BCBF5)
    fffff880`048bc000 fffff880`04918000   HdAudio  HdAudio.sys  Tue Jul 14 01:06:59 2009 (4A5BCC23)
    fffff880`04b32000 fffff880`04b4b000   HIDCLASS HIDCLASS.SYS Tue Jul 14 01:06:21 2009 (4A5BCBFD)
    fffff880`04b4b000 fffff880`04b53080   HIDPARSE HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9)
    fffff880`04b24000 fffff880`04b32000   hidusb   hidusb.sys   Tue Jul 14 01:06:22 2009 (4A5BCBFE)
    fffff880`05002000 fffff880`050ca000   HTTP     HTTP.sys     Tue Jul 14 00:22:16 2009 (4A5BC1A8)
    fffff880`0190d000 fffff880`01916000   hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA)
    fffff880`10bac000 fffff880`10bbb000   kbdclass kbdclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
    fffff880`04b60000 fffff880`04b6e000   kbdhid   kbdhid.sys   Tue Jul 14 01:00:20 2009 (4A5BCA94)
    fffff800`00b9b000 fffff800`00ba5000   kdcom    kdcom.dll    Sat Feb 05 12:21:45 2011 (4D4D40D9)
    fffff880`0fe00000 fffff880`0fe43000   ks       ks.sys       Thu Mar 04 04:32:25 2010 (4B8F37D9)
    fffff880`01142000 fffff880`0115c000   ksecdd   ksecdd.sys   Tue Jul 14 00:20:54 2009 (4A5BC156)
    fffff880`0155f000 fffff880`0158a000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:03:32 2009 (4B21E0B4)
    fffff880`04977000 fffff880`0497c200   ksthunk  ksthunk.sys  Tue Jul 14 01:00:19 2009 (4A5BCA93)
    fffff880`04bac000 fffff880`04bc1000   lltdio   lltdio.sys   Tue Jul 14 01:08:50 2009 (4A5BCC92)
    fffff880`04b89000 fffff880`04bac000   luafv    luafv.sys    Tue Jul 14 00:26:13 2009 (4A5BC295)
    fffff880`00c56000 fffff880`00c63000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 02:29:09 2009 (4A5BDF65)
    fffff880`04b7b000 fffff880`04b89000   monitor  monitor.sys  Tue Jul 14 00:38:52 2009 (4A5BC58C)
    fffff880`10bbb000 fffff880`10bca000   mouclass mouclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
    fffff880`04b6e000 fffff880`04b7b000   mouhid   mouhid.sys   Tue Jul 14 01:00:20 2009 (4A5BCA94)
    fffff880`00da5000 fffff880`00dbf000   mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A)
    fffff880`050e8000 fffff880`05100000   mpsdrv   mpsdrv.sys   Tue Jul 14 01:08:25 2009 (4A5BCC79)
    fffff880`05100000 fffff880`0512d000   mrxsmb   mrxsmb.sys   Wed May 04 03:51:06 2011 (4DC0BF1A)
    fffff880`0512d000 fffff880`0517b000   mrxsmb10 mrxsmb10.sys Wed May 04 03:51:08 2011 (4DC0BF1C)
    fffff880`0517b000 fffff880`0519e000   mrxsmb20 mrxsmb20.sys Wed May 04 03:51:05 2011 (4DC0BF19)
    fffff880`011f3000 fffff880`011fe000   Msfs     Msfs.SYS     Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`00f82000 fffff880`00f8c000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
    fffff880`01200000 fffff880`0125e000   msrpc    msrpc.sys    Tue Jul 14 00:21:32 2009 (4A5BC17C)
    fffff880`03c9b000 fffff880`03ca6000   mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE)
    fffff880`018fb000 fffff880`0190d000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
    fffff880`0140d000 fffff880`014ff000   ndis     ndis.sys     Tue Jul 14 00:21:40 2009 (4A5BC184)
    fffff880`04298000 fffff880`042a4000   ndistapi ndistapi.sys Tue Jul 14 01:10:00 2009 (4A5BCCD8)
    fffff880`042a4000 fffff880`042d3000   ndiswan  ndiswan.sys  Tue Jul 14 01:10:11 2009 (4A5BCCE3)
    fffff880`10bca000 fffff880`10bdf000   NDProxy  NDProxy.SYS  Tue Jul 14 01:10:05 2009 (4A5BCCDD)
    fffff880`03c00000 fffff880`03c0f000   netbios  netbios.sys  Tue Jul 14 01:09:26 2009 (4A5BCCB6)
    fffff880`03d81000 fffff880`03dc6000   netbt    netbt.sys    Tue Jul 14 00:21:28 2009 (4A5BC178)
    fffff880`014ff000 fffff880`0155f000   NETIO    NETIO.SYS    Tue Jul 14 00:21:46 2009 (4A5BC18A)
    fffff880`01000000 fffff880`01011000   Npfs     Npfs.SYS     Tue Jul 14 00:19:48 2009 (4A5BC114)
    fffff880`03c8f000 fffff880`03c9b000   nsiproxy nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E)
    fffff800`02c02000 fffff800`031de000   nt       ntkrnlmp.exe Sat Apr 09 05:14:44 2011 (4D9FDD34)
    fffff880`0125e000 fffff880`01400000   Ntfs     Ntfs.sys     Fri Mar 11 03:39:25 2011 (4D79996D)
    fffff880`0182a000 fffff880`01833000   Null     Null.SYS     Tue Jul 14 00:19:37 2009 (4A5BC109)
    fffff880`10b6c000 fffff880`10b71000   nvBridge nvBridge.kmd Sat May 21 04:58:23 2011 (4DD7385F)
    fffff880`0497d000 fffff880`049aa000   nvhda64v nvhda64v.sys Tue May 10 10:41:18 2011 (4DC9083E)
    fffff880`0febe000 fffff880`10b6c000   nvlddmkm nvlddmkm.sys Sat May 21 05:07:04 2011 (4DD73A68)
    fffff880`05b25000 fffff880`05b78600   nvmf6264 nvmf6264.sys Wed Nov 11 23:16:48 2009 (4AFB45E0)
    fffff880`00c00000 fffff880`00c2b000   nvstor   nvstor.sys   Fri Mar 19 20:45:11 2010 (4BA3E257)
    fffff880`01098000 fffff880`010d7000   nvstor64 nvstor64.sys Fri Apr 09 10:22:41 2010 (4BBEF1E1)
    fffff880`03dcf000 fffff880`03df5000   pacer    pacer.sys    Tue Jul 14 01:09:41 2009 (4A5BCCC5)
    fffff880`03f62000 fffff880`03f7f000   parport  parport.sys  Tue Jul 14 01:00:40 2009 (4A5BCAA8)
    fffff880`00fcc000 fffff880`00fe1000   partmgr  partmgr.sys  Tue Jul 14 00:19:58 2009 (4A5BC11E)
    fffff880`00f8c000 fffff880`00fbf000   pci      pci.sys      Tue Jul 14 00:19:51 2009 (4A5BC117)
    fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
    fffff880`00d95000 fffff880`00da5000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
    fffff880`011cf000 fffff880`011e0000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
    fffff880`0566f000 fffff880`05715000   peauth   peauth.sys   Tue Jul 14 02:01:19 2009 (4A5BD8DF)
    fffff880`04918000 fffff880`04955000   portcls  portcls.sys  Tue Jul 14 01:06:27 2009 (4A5BCC03)
    fffff880`00c63000 fffff880`00c77000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
    fffff880`04274000 fffff880`04298000   rasl2tp  rasl2tp.sys  Tue Jul 14 01:10:11 2009 (4A5BCCE3)
    fffff880`042d3000 fffff880`042ee000   raspppoe raspppoe.sys Tue Jul 14 01:10:17 2009 (4A5BCCE9)
    fffff880`10b71000 fffff880`10b92000   raspptp  raspptp.sys  Tue Jul 14 01:10:18 2009 (4A5BCCEA)
    fffff880`10b92000 fffff880`10bac000   rassstp  rassstp.sys  Tue Jul 14 01:10:25 2009 (4A5BCCF1)
    fffff880`03c3e000 fffff880`03c8f000   rdbss    rdbss.sys    Tue Jul 14 00:24:09 2009 (4A5BC219)
    fffff880`043eb000 fffff880`043f6000   rdpbus   rdpbus.sys   Tue Jul 14 01:17:46 2009 (4A5BCEAA)
    fffff880`015f4000 fffff880`015fd000   RDPCDD   RDPCDD.sys   Tue Jul 14 01:16:34 2009 (4A5BCE62)
    fffff880`01400000 fffff880`01409000   rdpencdd rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62)
    fffff880`011ea000 fffff880`011f3000   rdprefmp rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63)
    fffff880`018c1000 fffff880`018fb000   rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A)
    fffff880`04a8e000 fffff880`04aba000   rfcomm   rfcomm.sys   Tue Jul 14 01:06:56 2009 (4A5BCC20)
    fffff880`04bc1000 fffff880`04bd9000   rspndr   rspndr.sys   Tue Jul 14 01:08:50 2009 (4A5BCC92)
    fffff880`05715000 fffff880`05720000   secdrv   secdrv.SYS   Wed Sep 13 14:18:38 2006 (4508052E)
    fffff880`03f56000 fffff880`03f62000   serenum  serenum.sys  Tue Jul 14 01:00:33 2009 (4A5BCAA1)
    fffff880`03f39000 fffff880`03f56000   serial   serial.sys   Tue Jul 14 01:00:40 2009 (4A5BCAA8)
    fffff880`018b9000 fffff880`018c1000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
    fffff880`05a2c000 fffff880`05ac1000   srv      srv.sys      Fri Apr 29 04:13:05 2011 (4DBA2CC1)
    fffff880`0575f000 fffff880`057c6000   srv2     srv2.sys     Fri Apr 29 04:12:51 2011 (4DBA2CB3)
    fffff880`05720000 fffff880`0574d000   srvnet   srvnet.sys   Fri Apr 29 04:12:35 2011 (4DBA2CA3)
    fffff880`01036000 fffff880`01098000   storport storport.sys Fri Mar 11 04:24:35 2011 (4D79A403)
    fffff880`043f6000 fffff880`043f7480   swenum   swenum.sys   Tue Jul 14 01:00:18 2009 (4A5BCA92)
    fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Mon Apr 25 03:47:33 2011 (4DB4E0C5)
    fffff880`0574d000 fffff880`0575f000   tcpipreg tcpipreg.sys Tue Jul 14 01:09:49 2009 (4A5BCCCD)
    fffff880`00c2b000 fffff880`00c38000   TDI      TDI.SYS      Tue Jul 14 00:21:18 2009 (4A5BC16E)
    fffff880`01011000 fffff880`0102f000   tdx      tdx.sys      Tue Jul 14 00:21:15 2009 (4A5BC16B)
    fffff880`03c2a000 fffff880`03c3e000   termdd   termdd.sys   Tue Jul 14 01:16:36 2009 (4A5BCE64)
    fffff960`005c0000 fffff960`005ca000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff880`03eef000 fffff880`03f15000   tunnel   tunnel.sys   Tue Jul 14 01:09:37 2009 (4A5BCCC1)
    fffff880`0fe43000 fffff880`0fe55000   umbus    umbus.sys    Tue Jul 14 01:06:56 2009 (4A5BCC20)
    fffff880`04aea000 fffff880`04b07000   usbccgp  usbccgp.sys  Fri Mar 25 03:23:03 2011 (4D8C0A97)
    fffff880`04863000 fffff880`04864f00   USBD     USBD.SYS     Fri Mar 25 03:22:51 2011 (4D8C0A8B)
    fffff880`03fe0000 fffff880`03ff1000   usbehci  usbehci.sys  Fri Mar 25 03:22:57 2011 (4D8C0A91)
    fffff880`0fe60000 fffff880`0feba000   usbhub   usbhub.sys   Fri Mar 25 03:23:22 2011 (4D8C0AAA)
    fffff880`03f7f000 fffff880`03f8a000   usbohci  usbohci.sys  Fri Mar 25 03:22:56 2011 (4D8C0A90)
    fffff880`03f8a000 fffff880`03fe0000   USBPORT  USBPORT.SYS  Fri Mar 25 03:23:03 2011 (4D8C0A97)
    fffff880`04b18000 fffff880`04b24000   usbprint usbprint.sys Tue Jul 14 01:38:18 2009 (4A5BD37A)
    fffff880`04b07000 fffff880`04b18000   usbscan  usbscan.sys  Tue Jul 14 01:35:32 2009 (4A5BD2D4)
    fffff880`00fbf000 fffff880`00fcc000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
    fffff880`0183a000 fffff880`01848000   vga      vga.sys      Tue Jul 14 00:38:47 2009 (4A5BC587)
    fffff880`01848000 fffff880`0186d000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B)
    fffff880`015d4000 fffff880`015e4000   vmstorfl vmstorfl.sys Tue Jul 14 00:42:54 2009 (4A5BC67E)
    fffff880`00fe1000 fffff880`00ff6000   volmgr   volmgr.sys   Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Tue Jul 14 00:20:33 2009 (4A5BC141)
    fffff880`0186d000 fffff880`018b9000   volsnap  volsnap.sys  Tue Jul 14 00:20:08 2009 (4A5BC128)
    fffff880`03c0f000 fffff880`03c2a000   wanarp   wanarp.sys   Tue Jul 14 01:10:21 2009 (4A5BCCED)
    fffff880`015e4000 fffff880`015f4000   watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F)
    fffff880`00e6f000 fffff880`00f13000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
    fffff880`00f13000 fffff880`00f22000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
    fffff880`03dc6000 fffff880`03dcf000   wfplwf   wfplwf.sys   Tue Jul 14 01:09:26 2009 (4A5BCCB6)
    fffff960`00070000 fffff960`00382000   win32k   win32k.sys   Sat Jun 11 03:56:14 2011 (4DF2D94E)
    fffff880`00f79000 fffff880`00f82000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)
    
    Unloaded modules:
    fffff880`05b79000 fffff880`05bea000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00071000
    fffff880`05ac1000 fffff880`05b25000   nvm62x64.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00064000
    fffff880`01996000 fffff880`019a4000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`019a4000 fffff880`019ae000   dump_storpor
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000A000
    fffff880`019ae000 fffff880`019ed000   dump_nvstor6
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0003F000
    fffff880`019ed000 fffff880`01a00000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.


    HTH.
     
  7. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    I have clean installed the network driver and apparently the latest update is 2009 for that file (from the very latest update nforce has given me). I'm not sure if that file is really the culprit in that case because it said it couldn't really give a file and deferred to that one. I will make sure I keep an eye out for further BSoD and if I have anymore I'll post the dump files. I have had issues with this computer with this before while playing the game Perfect World. Doing anything else it has been completely stable. I'm starting to get to the point of troubleshooting hardware (switched out hard drive already and soon going to be looking at the RAM).
     
  8. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    Just had another one while playing Perfect World. Dump file attached.
     

    Attached Files:

  9. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
    Usual causes:
    Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

    Your latest dump file lists dxgmms1.sys as the probable cause. This is the Windows System DirectX Graphics file and for it to be the cause of your crash is highly unlikely.

    Your drivers are looking pretty good. The ASACPI.SYS is now dated 2009. As we're talking graphics you could try re-setting your graphics drivers again, although I have my doubts this will cure your problem.

    nVidia Graphics Drivers.

    • Download and install Driver Sweeper.
    • Uninstall your current Graphics setup through Programs and Features
    • Boot to Safe Mode
    • Run Driver Sweeper to clean up the remnants of your current Graphics set up.
    • Reboot to Normal Mode.
    • Install your new Graphics set up.


    Logically, this is saying to me it's a problem with Perfect World, especially as the machine runs fine at all other times. Do you know if there are any issues with Win 7 64bit and Perfect World?

    Bugcheck Analysis:
    Code:
    Loading Dump File [D:\DOWNLOADS\ DUMPS\natewin7user.dmp]
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88004197d90, fffff880044f26a8, fffff880044f1f10}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004197d90, The address that the exception occurred at
    Arg3: fffff880044f26a8, Exception Record Address
    Arg4: fffff880044f1f10, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
    fffff880`04197d90 8b4810          mov     ecx,dword ptr [rax+10h]
    
    EXCEPTION_RECORD:  fffff880044f26a8 -- (.exr 0xfffff880044f26a8)
    ExceptionAddress: fffff88004197d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff880044f1f10 -- (.cxr 0xfffff880044f1f10)
    rax=0200000000000000 rbx=fffff8a0077f84c0 rcx=fffffa8005f54ad0
    rdx=fffffa80061b82a0 rsi=fffffa8005f45000 rdi=fffffa8005f45000
    rip=fffff88004197d90 rsp=fffff880044f28e0 rbp=fffffa8004d3f110
     r8=fffffa80061e9f00  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000096 r12=fffffa80061b82a0 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
    fffff880`04197d90 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:02000000`00000010=????????
    Resetting default scope
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_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 fffff80002f000e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
    fffff880`04197d90 8b4810          mov     ecx,dword ptr [rax+10h]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff88004194ed3 to fffff88004197d90
    
    STACK_TEXT:  
    fffff880`044f28e0 fffff880`04194ed3 : 00000000`00000000 fffffa80`04a27058 00000000`0000008b 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
    fffff880`044f2910 fffff880`041af65d : 00000000`00000000 fffff8a0`0259d2d0 fffffa80`00000000 fffffa80`061e9f10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
    fffff880`044f2ae0 fffff880`041af398 : fffff880`009eaec0 fffff880`041aed00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`044f2cd0 fffff880`041aee96 : 00000000`00000000 fffffa80`049b3010 00000000`00000080 fffffa80`05da3010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`044f2d00 fffff800`02f6bbc6 : 00000000`176d060c fffffa80`05f33060 fffffa80`03cce040 fffffa80`05f33060 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`044f2d40 fffff800`02ca6bc6 : fffff880`009e6180 fffffa80`05f33060 fffff880`009f0f40 fffff880`0120e2b4 : nt!PspSystemThreadStartup+0x5a
    fffff880`044f2d80 00000000`00000000 : fffff880`044f3000 fffff880`044ed000 fffff880`044f2690 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174
    
    STACK_COMMAND:  .cxr 0xfffff880044f1f10 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
    
    BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
    
    Followup: MachineOwner  
     
  10. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    The frustrating thing with playing perfect world for over 2 years now is the fact that I just ran perfectly fine for 3 months straight. Then out of no where I started to crash from the game more often, and THEN I started to get graphics flicker out of no way (where the game would literally flicker different colors). I have had this happen before and simply taking out the graphics card and putting it back in the computer fixed it for a solid 3 months. Well this time I did it and instantly I started to crash. I then re-installed windows fresh and still blue screens came up even before I put in the game (1 happened while I was doing windows update). Since then it's been a bit of a mess. This setup is really no different hardware wise so it's frustrating when this stuff comes up. I've checked out what's going on with the game and plenty of people are running it fine on windows 7 64bit, but I'll be honest I'm very close to giving 32bit a try and seeing how that goes.
     
  11. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    The frustrating thing with playing perfect world for over 2 years now is the fact that I just ran perfectly fine for 3 months straight. Then out of no where I started to crash from the game more often, and THEN I started to get graphics flicker out of no way (where the game would literally flicker different colors). I have had this happen before and simply taking out the graphics card and putting it back in the computer fixed it for a solid 3 months. Well this time I did it and instantly I started to crash. I then re-installed windows fresh and still blue screens came up even before I put in the game (1 happened while I was doing windows update). Since then it's been a bit of a mess. This setup is really no different hardware wise so it's frustrating when this stuff comes up. I've checked out what's going on with the game and plenty of people are running it fine on windows 7 64bit, but I'll be honest I'm very close to giving 32bit a try and seeing how that goes.
     
  12. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    I'm afraid I'm still having issues with this computer. I will attach dump reports of the last two crashes from last few days. I'm about 99% sure it's bad memory, but I wanted to bring these dump files here just to make sure it isn't anything else. :(
     

    Attached Files:

  13. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    bump anyone need some help here :(
     
  14. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115

    Since you updated the asacpi.sys the last crash was blamed on your video subsystem. I would re-install the driver using the method below.

    If you suspect memory you can run these two tests to be certain.




    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


    Phyxion.net - Driver Sweeper

    When it is removed then download and install the fresh copy.




    1-Memtest


    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

    Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.



    2-Driver verifier


     
    2 people like this.
  15. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    Another 3 blue screens today after being fine for the last week.
     

    Attached Files:

  16. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115
    Have you run memtest and verifier?
     
    1 person likes this.
  17. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    I couldn't seem to get any errors with memtest or driver verifier so I eventually took driver verifier off. I can tell you the last few before today were win32k.sys and today lead off with system service exception and the latest one was one I have never seen before: video memory manager fatal error.

    I'm really getting nervous about this system. One day I really feel that it's my memory and then the next day it really seems like my power supply just isn't good enough. I've gotten at least 7 different types of blue screens with the system in the last few months. I'm really not sure what to make of the errors because they are so random. For all I know it could be the motherboard that's just causing all sorts of hell between all of them (memory / processor / graphics card) and the parts themselves are perfectly fine.
     
    #17 natewin7user, Aug 20, 2011
    Last edited: Aug 20, 2011
  18. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Joined:
    Jun 2, 2009
    Messages:
    812
    Likes Received:
    115

    How long did you run memtest (how many passes)?

    How long did you run verifier?
     
  19. natewin7user

    natewin7user New Member

    Joined:
    Mar 12, 2011
    Messages:
    48
    Likes Received:
    0
    I ran memtest 8 times and 0 errors

    I ran verifier for 2 1/2 days with nothing, but I can put that back up since I'm starting to have issues again and see what happens

    EDIT1: I put verifier on and almost as soon as I got into the game I crashed, let me get the dump file and upload it to this post.
    EDIT2: Another crash afk'ing in game for 5 minutes (second time), but now i'm just going to browse web and be on desktop for an hour or so and see if I get any crashes (doubt it though).
    EDIT3: Not sure what happened on this one seems I lost my feed to the graphics card (went black trying to find signal then restarted) but it was a BSoD apparently
    EDIT4: Same as edit 3 (I removed verifier for now) it was losing video with me just trying to view this thread so....
     

    Attached Files:

    #19 natewin7user, Aug 20, 2011
    Last edited: Aug 20, 2011
  20. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,694
    Likes Received:
    194
    Your bsod's are being caused by nvlddmkm.sys which is the nvidia display driver. Can you update to the latest from Nvidia

    These drivers are also a little on the old side nvmf6264 Nvidia Network driver also available from Nvidia. This is a must do update your windows to sp1 which will fix numerous issues and will make troubleshooting this problem a whole lot easier.
     

Share This Page

Loading...