BSOD IRQL/Memory Management/everything else part 1

LukeCai

I've been getting lots of BSODs, mostly IQRLs, but a few Memory Management and writing to ROM errors too. This system is a retail installation of Windows 7 32 bit, and all my parts are still under warranty.

BSOD appears under any level of stress - it can be while I'm actually stressing the system, playing video games, or when I'm idling the system. I've had the computer restart on me, and return to the desktop with a recovery from unexpected shutdown window at times.

The memory looks to be good from the windows memory diagnostic. I've installed and reinstalled every driver that came with the system.

ttran

I can't see any minidump files in the one you uploaded. Please following this instruction instead to post your minidump, and also make sure you have set your system to create minidump:

upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Quote:

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

If you are using any program such as CCleaner, they may clean out your minidump folder, please double check that

LukeCai

Minidumps are attached to this post.

EDIT: Should probably mention that this was an upgrade version of Win7, purchased from a school. It shows as OEM.

CarlTR6

Luke, five of the six dumps report the same stop error, A. One reports a stop error of 9F.

Quote:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE

Usual causes: Device driver

These point to hardware/hardware related problems.

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_minidump.zip\062910-24148-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available  DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82932ad4? Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is:  Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x8280c000 PsLoadedModuleList = 0x82954810 Debug session time: Tue Jun 29 05:14:21.382 2010 (GMT-4) System Uptime: 0 days 13:38:22.631 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ........ 0: kd> !Analyze ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 9F, {3, 85a6bb60, 82932ae0, 87097008}  *** WARNING: Unable to verify timestamp for L1C62x86.sys *** ERROR: Module load completed but symbols could not be loaded for L1C62x86.sys Probably caused by : L1C62x86.sys  Followup: MachineOwner ---------  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 00000003, A device object has been blocking an Irp for too long a time Arg2: 85a6bb60, Physical Device Object of the stack Arg3: 82932ae0, Functional Device Object of the stack Arg4: 87097008, The blocked IRP  Debugging Details: ------------------   DRVPOWERSTATE_SUBCODE:  3  IRP_ADDRESS:  87097008  DEVICE_OBJECT: 86556028  DRIVER_OBJECT: 864fe418  IMAGE_NAME:  L1C62x86.sys  DEBUG_FLR_IMAGE_TIMESTAMP:  49d2f6a2  MODULE_NAME: L1C62x86  FAULTING_MODULE: 9070f000 L1C62x86  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT  BUGCHECK_STR:  0x9F  PROCESS_NAME:  System  CURRENT_IRQL:  2  LAST_CONTROL_TRANSFER:  from 82848054 to 828e8d10  STACK_TEXT:   82932a94 82848054 0000009f 00000003 85a6bb60 nt!KeBugCheckEx+0x1e 82932b00 828478e8 82932ba0 00000000 8293f280 nt!PopCheckIrpWatchdog+0x1f5 82932b38 8287604d 8294da20 00000000 75b3662e nt!PopCheckForIdleness+0x73 82932b7c 82875ff1 82935d20 82932ca8 00000001 nt!KiProcessTimerDpcTable+0x50 82932c68 82875eae 82935d20 82932ca8 00000000 nt!KiProcessExpiredTimerList+0x101 82932cdc 8287420e 00300740 8551ac90 8293f280 nt!KiTimerExpiration+0x25c 82932d20 82874038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 82932d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38   STACK_COMMAND:  kb  FOLLOWUP_NAME:  MachineOwner  FAILURE_BUCKET_ID:  0x9F_IMAGE_L1C62x86.sys  BUCKET_ID:  0x9F_IMAGE_L1C62x86.sys  Followup: MachineOwner ---------  0: kd> lmtsmn start    end        module name 82fa2000 82fea000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F) 8ec1d000 8ec77000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62) 908b7000 908c9000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954) 8b5eb000 8b5fc000   amdppm   amdppm.sys   Mon Jul 13 19:11:03 2009 (4A5BBF07) 8b523000 8b52c000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F) 8b4f7000 8b500000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13) 8b500000 8b523000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16) 8b9f0000 8b9f7000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC) 8b5dd000 8b5eb000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8) 82e2e000 82e36000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2) 98c89000 98ca2000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD) 96ad0000 96aee000   cdd      cdd.dll      unavailable (00000000) 8b9ca000 8b9e9000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C) 82e78000 82f23000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8) 8b980000 8b9a5000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18) 82e36000 82e78000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E) 8b79f000 8b7fc000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427) 908aa000 908b7000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716) 95275000 95282000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E) 8ed9a000 8edfe000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC) 8ec00000 8ec18000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8) 8ed8e000 8ed9a000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214) 8bbef000 8bc00000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20) 95252000 9526b000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5) 9528d000 95296000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 95282000 9528d000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 95296000 952a7000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 9526b000 95275000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265) 9061f000 906d6000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 19:26:15 2009 (4A5BC297) 906d6000 9070f000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265) 8b560000 8b571000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) 8b52c000 8b560000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11) 8b60e000 8b617000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12) 8b94e000 8b980000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D) 8bb56000 8bb87000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43) 82c1c000 82c53000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07) 90783000 907a2000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F) 9158b000 915db000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892) 98d7f000 98d88000   hiber_atapi hiber_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 98d74000 98d7f000   hiber_dumpata hiber_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 98d88000 98d99000   hiber_dumpfve hiber_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 952eb000 952fe000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865) 8c800000 8c806480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863) 8c9f4000 8c9ff000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868) 98c04000 98c89000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75) 8bbe7000 8bbef000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05) 9095e000 9096b000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 95309000 95315000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705) 80bc4000 80bcc000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA) 9097a000 909ae000   ks       ks.sys       Mon Jul 13 19:45:13 2009 (4A5BC709) 8b78c000 8b79f000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C) 8b8fc000 8b921000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468) 9070f000 9071f000   L1C62x86 L1C62x86.sys Wed Apr 01 01:07:46 2009 (49D2F6A2) 95355000 95365000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE) 95320000 9533b000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020) 82e12000 82e1d000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89) 95315000 95320000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286) 9096b000 90978000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 952fe000 95309000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704) 8b4e1000 8b4f7000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F) 98ca2000 98cb4000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4) 98cf4000 98d17000   mrxsmb   mrxsmb.sys   Mon Jul 13 19:14:24 2009 (4A5BBFD0) 98d17000 98d52000   mrxsmb10 mrxsmb10.sys Mon Jul 13 19:14:34 2009 (4A5BBFDA) 98d52000 98d6d000   mrxsmb20 mrxsmb20.sys Mon Jul 13 19:14:29 2009 (4A5BBFD5) 8b5a2000 8b5ad000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E) 82ff3000 82ffb000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D) 8b761000 8b78c000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F) 8ed84000 8ed8e000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) 8bbd7000 8bbe7000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6) 8b807000 8b8be000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58) 908e1000 908ec000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930) 953ab000 953bb000   ndisuio  ndisuio.sys  Mon Jul 13 19:53:51 2009 (4A5BC90F) 908ec000 9090e000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A) 907c4000 907d5000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933) 8ece0000 8ecee000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912) 8ec77000 8eca9000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52) 8b8be000 8b8fc000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63) 9080e000 90897000   netr28   netr28.sys   Wed Feb 25 21:56:57 2009 (49A604F9) 8b5ad000 8b5bb000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23) 8ed7a000 8ed84000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48) 8280c000 82c1c000   nt       ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007) 8b632000 8b761000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45) 8b9e9000 8b9f0000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10) 90c25000 9158a940   nvlddmkm nvlddmkm.sys Thu May 14 16:32:27 2009 (4A0C7FDB) 95365000 953ab000   nwifi    nwifi.sys    Mon Jul 13 19:51:59 2009 (4A5BC89F) 8ecb0000 8eccf000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916) 907a2000 907ba000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E) 8b460000 8b471000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27) 98d6d000 98d74000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719) 8b42b000 8b455000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14) 8b4cc000 8b4d3000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17) 8b4d3000 8b4e1000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13) 8b600000 8b60e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E) 9e802000 9e899000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0) 95223000 95252000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864) 82e1d000 82e2e000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0) 908c9000 908e1000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939) 9090e000 90926000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D) 90926000 9093d000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947) 9093d000 90954000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951) 8ed39000 8ed7a000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2) 90954000 9095e000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20) 8b9f7000 8b9ff000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4) 8b592000 8b59a000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3) 8b59a000 8b5a2000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5) 8b921000 8b94e000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A) 953bb000 953ce000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0) 8ed2b000 8ed38a60   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:44:34 2010 (4BC2DD72) 9e899000 9e8a3000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528) 907ba000 907c4000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717) 8ecee000 8ed08000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D) 8bbcf000 8bbd7000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB) 9e996000 9ea00000   spsys    spsys.sys    Mon May 11 12:37:10 2009 (4A085436) 9e920000 9e971000   srv      srv.sys      Mon Jul 13 19:15:10 2009 (4A5BBFFE) 9e8d1000 9e920000   srv2     srv2.sys     Mon Jul 13 19:14:52 2009 (4A5BBFEC) 9e8a3000 9e8c4000   srvnet   srvnet.sys   Mon Jul 13 19:14:45 2009 (4A5BBFE5) 8c9e6000 8c9f3180   STREAM   STREAM.SYS   Mon Jul 13 19:50:57 2009 (4A5BC861) 90978000 90979380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704) 8ba0d000 8bb56000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E) 9e8c4000 9e8d1000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926) 8b5d2000 8b5dd000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C) 8b5bb000 8b5d2000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A) 8ed1b000 8ed2b000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF) 96aa0000 96aa9000   TSDDD    TSDDD.dll    unavailable (00000000) 8b400000 8b421000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B) 98cb4000 98cf4000   udfs     udfs.sys     Mon Jul 13 19:14:09 2009 (4A5BBFC1) 909ae000 909bc000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A) 952c0000 952d3b00   usbaudio usbaudio.sys Mon Jul 13 19:51:23 2009 (4A5BC87B) 952a7000 952be000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883) 952be000 952bf700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869) 90774000 90783000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872) 909bc000 90a00000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6) 9071f000 90729000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872) 90729000 90774000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871) 952d4000 952eb000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877) 8b455000 8b460000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B) 8b617000 8b623000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E) 8b571000 8b592000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D) 8bb87000 8bb8f380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C) 8b471000 8b481000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8b481000 8b4cc000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D) 8bb90000 8bbcf000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26) 90897000 908a1000   vwifibus vwifibus.sys Mon Jul 13 19:52:02 2009 (4A5BC8A2) 8eccf000 8ece0000   vwififlt vwififlt.sys Mon Jul 13 19:52:03 2009 (4A5BC8A3) 8c808000 8c9e5600   VX3000   VX3000.sys   Tue Oct 06 21:48:19 2009 (4ACBF363) 8ed08000 8ed1b000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956) 8b623000 8b630000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A) 82f23000 82f94000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28) 82f94000 82fa2000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8eca9000 8ecb0000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F) 96840000 96a8a000   win32k   win32k.sys   unavailable (00000000) 908a1000 908aa000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:19:16 2009 (4A5BC0F4) 82fea000 82ff3000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A) 9533b000 95355000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835) 9e971000 9e991480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)  Unloaded modules: 9e992000 9e994000   MSPCLOCK.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 9e800000 9e802000   MSPQM.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 9e994000 9e996000   MSPCLOCK.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 9e992000 9e994000   MSPQM.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 8ba00000 8ba0d000   crashdmp.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 8b9a5000 8b9b0000   dump_ataport     Timestamp: unavailable (00000000)     Checksum:  00000000 8b9b0000 8b9b9000   dump_atapi.s     Timestamp: unavailable (00000000)     Checksum:  00000000 8b9b9000 8b9ca000   dump_dumpfve     Timestamp: unavailable (00000000)     Checksum:  00000000   Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_minidump.zip\072910-35739-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available  Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is:  Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x8280c000 PsLoadedModuleList = 0x82954810 Debug session time: Thu Jul 29 18:54:24.908 2010 (GMT-4) System Uptime: 0 days 0:46:58.547 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .............. ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck A, {0, 2, 1, 82874f9c}  Probably caused by : ntkrpamp.exe ( nt!KiSignalSynchronizationObject+1c )  Followup: MachineOwner ---------  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.  This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield :     bit 0 : value 0 = read operation, 1 = write operation     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82874f9c, address which referenced memory  Debugging Details: ------------------   WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82974718 Unable to read MiSystemVaType memory at 82954160  00000000   CURRENT_IRQL:  2  FAULTING_IP:  nt!KiSignalSynchronizationObject+1c 82874f9c 8901            mov     dword ptr [ecx],eax  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT  BUGCHECK_STR:  0xA  PROCESS_NAME:  System  TRAP_FRAME:  82932ab4 -- (.trap 0xffffffff82932ab4) ErrCode = 00000002 eax=00000000 ebx=8bb1eac8 ecx=00000000 edx=8bb1eac0 esi=00000000 edi=8bb1cac8 eip=82874f9c esp=82932b28 ebp=82932b38 iopl=0         nv up ei ng nz na pe cy cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287 nt!KiSignalSynchronizationObject+0x1c: 82874f9c 8901            mov     dword ptr [ecx],eax  ds:0023:00000000=???????? Resetting default scope  LAST_CONTROL_TRANSFER:  from 82874f9c to 828527eb  STACK_TEXT:   82932ab4 82874f9c badb0d00 8bb1eac0 00000000 nt!KiTrap0E+0x2cf 82932b38 82876276 82935d20 8bb1eac0 82932ba4 nt!KiSignalSynchronizationObject+0x1c 82932b80 82875f7b 82935d20 00000000 82937680 nt!KiTimerWaitTest+0x1cf 82932c68 82875eae 82935d20 82932ca8 00000000 nt!KiProcessExpiredTimerList+0x8b 82932cdc 8287420e 0002c1c2 856a2168 8293f280 nt!KiTimerExpiration+0x25c 82932d20 82874038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 82932d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38   STACK_COMMAND:  kb  FOLLOWUP_IP:  nt!KiSignalSynchronizationObject+1c 82874f9c 8901            mov     dword ptr [ecx],eax  SYMBOL_STACK_INDEX:  1  SYMBOL_NAME:  nt!KiSignalSynchronizationObject+1c  FOLLOWUP_NAME:  MachineOwner  MODULE_NAME: nt  IMAGE_NAME:  ntkrpamp.exe  DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007  FAILURE_BUCKET_ID:  0xA_nt!KiSignalSynchronizationObject+1c  BUCKET_ID:  0xA_nt!KiSignalSynchronizationObject+1c  Followup: MachineOwner ---------  0: kd> lmtsmn start    end        module name 82fa5000 82fed000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F) 91624000 9167e000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62) 990be000 990d0000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954) 91aec000 91afd000   amdppm   amdppm.sys   Mon Jul 13 19:11:03 2009 (4A5BBF07) 8b534000 8b53d000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F) 91ac9000 91aca440   AsIO     AsIO.sys     Mon Dec 17 04:10:20 2007 (47663CFC) 8b508000 8b511000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13) 8b511000 8b534000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16) 8ba19000 8ba21000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:16 2009 (4A005480) 90d16000 90d1d000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC) 91abb000 91ac9000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8) 82e31000 82e39000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2) a2f1a000 a2f33000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD) 825d0000 825ee000   cdd      cdd.dll      unavailable (00000000) 991d4000 991ea000   cdfs     cdfs.sys     Mon Jul 13 19:11:14 2009 (4A5BBF12) 8b811000 8b830000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C) 82e7b000 82f26000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8) 8b9ad000 8b9d2000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18) 82e39000 82e7b000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E) 8b76d000 8b7ca000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427) 990b1000 990be000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716) 91a2d000 91a3a000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E) 91a3f000 91aa3000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC) 91aa3000 91abb000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8) 91795000 917a1000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214) 8ba08000 8ba19000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20) 98fbd000 98fd6000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5) 9900b000 99014000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 917e5000 917f0000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 91600000 91611000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 98fd6000 98fe0000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265) 91afd000 91bb4000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 19:26:15 2009 (4A5BC297) 9f166000 9f19f000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265) 8b571000 8b582000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) 8b53d000 8b571000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11) 8b7d8000 8b7e1000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12) 8b97b000 8b9ad000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D) 8bb6d000 8bb9e000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43) 82c1c000 82c53000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07) 9f1c8000 9f1e7000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F) 991ea000 991fd000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865) 98e0b000 98e11480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863) 98e00000 98e0b000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868) a2e95000 a2f1a000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75) 8ba00000 8ba08000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05) 99165000 99172000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 91a21000 91a2d000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705) 80bab000 80bb3000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA) 99181000 991b5000   ks       ks.sys       Mon Jul 13 19:45:13 2009 (4A5BC709) 8b75a000 8b76d000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C) 8b929000 8b94e000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468) 9f19f000 9f1af000   L1C62x86 L1C62x86.sys Mon Jul 27 03:06:45 2009 (4A6D5205) 917f0000 91800000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE) 90daa000 90dc5000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020) 82e15000 82e20000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89) a87bf000 a87ca000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286) 99172000 9917f000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 99000000 9900b000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704) 8b4f2000 8b508000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F) a2f33000 a2f45000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4) a2f45000 a2f68000   mrxsmb   mrxsmb.sys   Mon Jul 13 19:14:24 2009 (4A5BBFD0) a2f68000 a2fa3000   mrxsmb10 mrxsmb10.sys Mon Jul 13 19:14:34 2009 (4A5BBFDA) a2fa3000 a2fbe000   mrxsmb20 mrxsmb20.sys Mon Jul 13 19:14:29 2009 (4A5BBFD5) 90d6f000 90d7a000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E) 82ff6000 82ffe000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D) 8b72f000 8b75a000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F) 9178b000 91795000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) 8bbee000 8bbfe000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6) 90cf0000 90d041e0   NAVENG   NAVENG.SYS   Mon Jun 29 15:54:25 2009 (4A491BF1) 90c1b000 90cef760   NAVEX15  NAVEX15.SYS  Mon Jun 29 15:54:22 2009 (4A491BEE) 8b834000 8b8eb000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58) 990e8000 990f3000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930) a2e72000 a2e82000   ndisuio  ndisuio.sys  Mon Jul 13 19:53:51 2009 (4A5BC90F) 990f3000 99115000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A) 991c3000 991d4000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933) 916e7000 916f5000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912) 9167e000 916b0000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52) 8b8eb000 8b929000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63) b9411000 b94b2000   netr28   netr28.sys   Fri Sep 11 01:20:24 2009 (4AA9DE18) 90d7a000 90d88000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23) 91781000 9178b000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48) 8280c000 82c1c000   nt       ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007) 8b600000 8b72f000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45) 90d0f000 90d16000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10) a87bd000 a87be080   nvBridge nvBridge.kmd Sun Sep 27 19:56:53 2009 (4ABFFBC5) 9e800000 9f110160   nvlddmkm nvlddmkm.sys Sun Sep 27 20:13:17 2009 (4ABFFF9D) a2e2c000 a2e72000   nwifi    nwifi.sys    Mon Jul 13 19:51:59 2009 (4A5BC89F) 916b7000 916d6000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916) 9f1e7000 9f1ff000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E) 8b471000 8b482000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27) a2fbe000 a2fc5000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719) 8b43c000 8b466000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14) 8b4dd000 8b4e4000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17) 8b4e4000 8b4f2000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13) 8b7ca000 8b7d8000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E) a862d000 a86c4000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0) 98f8e000 98fbd000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864) 82e20000 82e31000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0) 990d0000 990e8000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939) 99115000 9912d000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D) 9912d000 99144000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947) 99144000 9915b000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951) 91740000 91781000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2) 9915b000 99165000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20) 90d57000 90d5f000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4) 90d5f000 90d67000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3) 90d67000 90d6f000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5) 8b94e000 8b97b000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A) a2e82000 a2e95000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0) 91732000 9173fa60   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:44:34 2010 (4BC2DD72) a86c4000 a86ce000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528) 91a00000 91a0a000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717) 916f5000 9170f000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D) 8bbe6000 8bbee000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB) 8b582000 8b5d5000   SRTSP    SRTSP.SYS    Mon Jun 22 22:12:04 2009 (4A4039F4) 90d05000 90d0e080   SRTSPX   SRTSPX.SYS   Mon Jun 22 22:15:26 2009 (4A403ABE) a874b000 a879c000   srv      srv.sys      Mon Jul 13 19:15:10 2009 (4A5BBFFE) a86fc000 a874b000   srv2     srv2.sys     Mon Jul 13 19:14:52 2009 (4A5BBFEC) a86ce000 a86ef000   srvnet   srvnet.sys   Mon Jul 13 19:14:45 2009 (4A5BBFE5) 9917f000 99180380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704) 8ba24000 8bb6d000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E) a86ef000 a86fc000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926) 90d9f000 90daa000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C) 90d88000 90d9f000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A) 91722000 91732000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF) 824e0000 824e9000   TSDDD    TSDDD.dll    unavailable (00000000) 91acb000 91aec000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B) 991b5000 991c3000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A) 91a0a000 91a21000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883) 98ff7000 98ff8700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869) 9f1b9000 9f1c8000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872) 917a1000 917e5000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6) 9f1af000 9f1b9000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872) 91bb4000 91bff000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871) 98fe0000 98ff7000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877) 8b466000 8b471000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B) 90d1d000 90d29000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E) 98e12000 98f8e000   viahduaa viahduaa.sys Tue Oct 20 23:27:39 2009 (4ADE7FAB) 90d29000 90d4a000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D) 8bb9e000 8bba6380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C) 8b482000 8b492000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8b492000 8b4dd000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D) 8bba7000 8bbe6000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26) b94b2000 b94bc000   vwifibus vwifibus.sys Mon Jul 13 19:52:02 2009 (4A5BC8A2) 916d6000 916e7000   vwififlt vwififlt.sys Mon Jul 13 19:52:03 2009 (4A5BC8A3) 9170f000 91722000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956) 90d4a000 90d57000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A) 82f26000 82f97000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28) 82f97000 82fa5000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D) 916b0000 916b7000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F) 82280000 824ca000   win32k   win32k.sys   unavailable (00000000) 990a8000 990b1000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:19:16 2009 (4A5BC0F4) 82fed000 82ff6000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A) 90dc5000 90ddf000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835) a879c000 a87bc480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)  Unloaded modules: b94bc000 b9526000   spsys.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 b94bc000 b94c6000   vwifibus.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 b941b000 b94bc000   netr28.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 b94b5000 b94bf000   vwifibus.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 b9414000 b94b5000   netr28.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 9909e000 990a8000   vwifibus.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 99015000 9909e000   netr28.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 9e800000 9f166000   nvlddmkm.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 91611000 9161c000   monitor.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 ae23b000 ae2a5000   spsys.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 8b9d2000 8b9df000   crashdmp.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 8b9df000 8b9ea000   dump_ataport     Timestamp: unavailable (00000000)     Checksum:  00000000 8b9ea000 8b9f3000   dump_atapi.s     Timestamp: unavailable (00000000)     Checksum:  00000000 8b800000 8b811000   dump_dumpfve     Timestamp: unavailable (00000000)     Checksum:  00000000

I suspect this may be a driver problem. Start by enabling Driver Verifier.

Using Driver Verifier to identify issues with Drivers

Quote:

Please follow these instructions in order to run it:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

CarlTR6

I found some older drivers. Win 7 generally does like older drivers. These all belong to Norton/Symantec. Norton is a known cause of BSOD crashes on some Win 7 systems. Please uninstall Norton using the uninstall tool >Info > Tool

NAVENG.SYS Mon Jun 29 15:54:25 2009
NAVEX15.SYS Mon Jun 29 15:54:22 2009
SRTSP.SYS Mon Jun 22 22:12:04 2009
SRTSPX.SYS Mon Jun 22 22:15:26 2009

After you uninstall Norton completely, reboot and run your system. Lets see if you have any more BSOD's.

LukeCai

Could my problems be caused by having driver verifier on all the time? I wasn't sure how it worked, so I turned it on probably and never shut it off.

dxgmms1.sys and usbport.sys were two drivers that bluescreened me, that I have written down on a napkin.

CarlTR6

If you are having driver problems, it will definitely cause BSOD's. But these dumps do not show that verifier is enabled.

I just edited my post above with information about Norton. You need to uninstall it and replace with Microsoft Security Essentials and make sure Windows Firewall is turned on. You the tool to uninstall it. Norton may well be the cause of your crashes.

LukeCai

Norton is a fairly recent installation - it came bundled with a bunch of driver updates that I had to install anyway.

Jonathan_King

Go ahead and uninstall it...we need to eliminate as many factors as possible.

If the problem is resolved, go ahead and install Norton again, but if it returns, you know what to do.

I suspect you will like MSE though; it is faster and lighter-weight.

CarlTR6

Since it is known to be a problem on some Win 7 systems, I recommend you uninstall it, at least while you are trouble shooting. The
idea is to eliminate the possible causes of crashes since the dumps do not point to anything specifically. Look at the usual causes of error code A and you will see virus scanner mentioned. After you get your system running smoothly, you can install the updated version of Norton, 2010; but I do not recommend that you do so. I suggest you use MSE or Avast and both are free. There are some valid reasons for this suggestion.

Edited to add: Jonathan was posting as I was typing. Thanks, Jonathan; I appreciate the assistance.

LukeCai

Attached is another minidump - it indicated a driver on the crash screen, but I didn't have time to read what it was.

Jonathan_King

This one looks pretty straightforward. It appears your nVidia graphics drivers are the cause.

I see they are dated September 2009, and there is a July 2010 update. Please install it: Drivers - Download NVIDIA Drivers

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_073010-15787-01 - Copy.zip\073010-15787-01 - Copy.dmp] Mini Kernel Dump File: Only registers and stack trace are available  Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is:  Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82a48000 PsLoadedModuleList = 0x82b90810 Debug session time: Fri Jul 30 18:00:13.926 2010 (UTC - 4:00) System Uptime: 0 days 0:03:10.565 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list .... 2: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: 87421008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: 91cce1a0, The pointer into responsible device driver module (e.g. owner tag). Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 00000002, Optional internal context dependent data.  Debugging Details: ------------------  Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys  FAULTING_IP:  nvlddmkm+bf1a0 91cce1a0 55              push    ebp  DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT  BUGCHECK_STR:  0x116  PROCESS_NAME:  System  CURRENT_IRQL:  0  STACK_TEXT:   96276b74 925ae92c 00000116 87421008 91cce1a0 nt!KeBugCheckEx+0x1e 96276b98 925af74b 91cce1a0 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d 96276bbc 910cb92c 00000000 00000102 8745d008 dxgkrnl!TdrIsRecoveryRequired+0xb8 96276c34 910f5a32 fffffcfb 00002ee1 00000000 dxgmms1!VidSchiReportHwHang+0x3c0 96276c5c 910f6153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68 96276c98 910d28f0 96276c90 874b97d0 879d6978 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1 96276d28 910f74b7 8745d008 82a843f1 8745d008 dxgmms1!VidSchiScheduleCommandToRun+0xaa 96276d3c 910f7573 8745d008 00000000 87472a48 dxgmms1!VidSchiRun_PriorityTable+0xf 96276d50 82c5666d 8745d008 b85d5c42 00000000 dxgmms1!VidSchiWorkerThread+0x7f 96276d90 82b080d9 910f74f4 8745d008 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19   STACK_COMMAND:  .bugcheck ; kb  FOLLOWUP_IP:  nvlddmkm+bf1a0 91cce1a0 55              push    ebp  SYMBOL_NAME:  nvlddmkm+bf1a0  FOLLOWUP_NAME:  MachineOwner  MODULE_NAME: nvlddmkm  IMAGE_NAME:  nvlddmkm.sys  DEBUG_FLR_IMAGE_TIMESTAMP:  4abfff9d  FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys  BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys  Followup: MachineOwner ---------  2: kd> lmvm nvlddmkm start    end        module name 91c0f000 9251f160   nvlddmkm T (no symbols)                Loaded symbol image file: nvlddmkm.sys     Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys     Image name: nvlddmkm.sys     Timestamp:        Sun Sep 27 20:13:17 2009 (4ABFFF9D)     CheckSum:         0091A611     ImageSize:        00910160     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

LukeCai

I installed new drivers, but the bluescreens aren't stopping. The latest bluescreen showed dxgmms1.sys as the culprit.

CarlTR6

dxgmms1.sys points to your video card. Both of these dumps have an error code of 7E - Memory corruption.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

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,
BSOD Index

Please recap for us what steps of those suggested you have completed so far.

I find these two of date drivers on your system.

AtiPcie.sys Tue May 05 11:00:16 2009 - ATI PCIE Driver for ATI PCIE chipsethttp://www.ati.com/ Update this driver

wdcsam.sys Wed Apr 16 04:27:02 2008 - WD SCSI Architecture Model (SAM) driver - WD External Storage - Western Digital Technologies. Western Digital External Drive RAID Manager http://support.wdc.com/product/download.asp Update this driver.

LukeCai

I've uninstalled Norton software and updated the video card driver, from the nVidia website. Since my last post, there has been another Driver IRQL error, showing usbohci.sys as the offending driver.

CarlTR6

usbohci.sys is a Microsft driver and most likely not the cause. It just got blamed.

Since the error code of the last two dumps you uploaded are 7E, lets check your RAM. Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes. Post back with the results.

Quote:

If Memtest checks back clean after 7+ passes, follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers

Quote:

Please follow these instructions in order to run it:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

ttran

In addtion to Carl great advise, USBOHCI.sys is a Windows core driver and it has to do with USB miniport, I would recommend to update your motherboard driver

LukeCai

I didn't record any problem with the RAM, but I'm still getting IQRL errors. With driver verifier on, I was not able to boot the OS - it would hang at the windows 7 screen.

The memory dumps taken in the morning were without driver verifier on, and should not show it. I activated verifier.exe a few minutes ago, and attached that memory dump separately. It showed a different error than before - something with a D at the end.

ttran

There are different stop codes with different things were blamed. Personally, I suspect this is graphic card issue as I can see a stop code 8E with dxgkrnl.sys was blamed. Do you have another graphic card that you can test?

Also with exception code c0000005, which is memory access violation, I would follow Carl advise to test the Ram using memtestx86. 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.

Update this driver please:

Code:

AsIO     AsIO.sys     Mon Dec 17 16:10:20 2007 (47663CFC)

It is Asus PCProbe Utility, ASUSTeK Computer Inc.-Support-

BUGCHECK SUMMARY:

Code:

BugCheck 5, {1, 85d17858, 0, 0}  Probably caused by : ndis.sys ( ndis!ndisPassIrpDownTheStack+3d )  Followup: MachineOwner --------- BugCheck C5, {80b47dcc, 2, 0, 82b3204d}  Probably caused by : ntkrpamp.exe ( nt!ExAllocatePoolWithTag+49d )  Followup: MachineOwner BugCheck 1A, {41284, 213e001, 964, c0802000}  Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )  Followup: MachineOwner --------- BugCheck 7F, {0, 0, 0, 0}  Probably caused by : ntkrpamp.exe ( nt!KiTrap00+8b )  Followup: MachineOwner --------- BugCheck 1000008E, {c0000005, 82a97f3d, 9ed17b64, 0}  Probably caused by : dxgkrnl.sys ( dxgkrnl+1512 )  Followup: MachineOwner ---------

Regard,

Tuan
---------

LukeCai

The machine only comes with two slots for DIMMs, and the ram comes as a set. Would it make sense to just test both sticks at the same time? There isn't much recourse I can take if one of them turns out to be bad.

EDIT: I'm afraid there is no other graphics card I can test.

ttran

Yep, test both of them first to see if it return error. I don't say that it is really your Ram issue. It really can be memory issue or driver that cause the memory issue. So let's do the memtestx86 first to eliminate one.

Jonathan_King

What anti-virus are you using?

The problem I see now is with your outdated AsIO.sys file. Please install the latest PC Probe utility from this site: ASUSTeK Computer Inc.-Support-

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_073110-16489-01 - Copy.zip\073110-16489-01 - Copy.dmp] Mini Kernel Dump File: Only registers and stack trace are available  Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is:  Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.x86fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0x82a06000 PsLoadedModuleList = 0x82b4e810 Debug session time: Sat Jul 31 23:34:07.016 2010 (UTC - 4:00) System Uptime: 0 days 0:00:10.654 Loading Kernel Symbols ............................................................... ........................ Loading User Symbols 2: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  INVALID_PROCESS_ATTACH_ATTEMPT (5) Arguments: Arg1: 00000001 Arg2: 85d17858 Arg3: 00000000 Arg4: 00000000  Debugging Details: ------------------   DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP  BUGCHECK_STR:  0x5  PROCESS_NAME:  System  CURRENT_IRQL:  1  LOCK_ADDRESS:  82b6bf60 -- (!locks 82b6bf60)  Resource @ nt!PiEngineLock (0x82b6bf60)    Available  WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.   WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.  1 total locks  PNP_TRIAGE:      Lock address  : 0x82b6bf60     Thread Count  : 0     Thread address: 0x00000000     Thread wait   : 0x0  LAST_CONTROL_TRANSFER:  from 82e1b90f to 82aae18b  STACK_TEXT:   87d994ec 82e1b90f 00000000 00000000 87d99540 nt!KiDeliverApc+0x2e3 87d9950c 82e1bb29 87d00001 87d99540 c9430789 hal!HalpDispatchSoftwareInterrupt+0x49 87d99524 82e1bcc3 196e4565 87d99540 82e30af0 hal!HalpCheckForSoftwareInterrupt+0x83 87d99530 82e30af0 00000000 000000e1 87d995c4 hal!HalEndSystemInterrupt+0x67 87d99530 82a44e44 00000000 000000e1 87d995c4 hal!HalpIpiHandler+0x198 87d995b0 82d3a886 8b41dd28 00000000 0000006c nt!memset+0x4 87d995c4 82d35533 8ed2af00 87d995e0 00000000 nt!VfIrpAllocateCallDriverData+0x33 87d995e8 82a42473 85829ab1 8ed2af00 8b502e38 nt!IovCallDriver+0xcc 87d995fc 85829ab1 8ed2af00 8ed2afdc 00040000 nt!IofCallDriver+0x1b 87d9961c 8589b8cd 8ed2af00 8b502e38 8b5270e0 ndis!ndisPassIrpDownTheStack+0x3d 87d99680 858655d0 8b5270e0 00000000 8b527f8c ndis!ndisQueryBusInterface+0x125 87d9977c 8589aa20 8ed1cfb8 8b5270e0 8b527fe8 ndis!ndisInitializeConfiguration+0x498 87d99858 85865028 8b501718 87d99898 850fb690 ndis!ndisAddDevice+0x6e4 87d99960 82a1a793 8b501718 850fb690 850fa6e8 ndis!ndisPnPAddDevice+0x5db 87d9997c 82bb57b3 850fb690 85864a4d 00000004 nt!PpvUtilCallAddDevice+0x45 87d999c4 82bae2ea 8b501718 85864a4d 00000002 nt!PnpCallAddDevice+0xb9 87d99a98 82bad876 850fa6e8 87d99cc8 00000000 nt!PipCallDriverAddDevice+0x565 87d99c94 82b91a2a 85dade78 8b3d64a0 87d99cc8 nt!PipProcessDevNodeTree+0x15d 87d99cd4 82a19f9c 8b3d64a0 82b69e80 85da04c0 nt!PiProcessStartSystemDevices+0x6d 87d99d00 82a73f3b 00000000 00000000 85da04c0 nt!PnpDeviceActionWorker+0x241 87d99d50 82c146bb 00000001 b75d327a 00000000 nt!ExpWorkerThread+0x10d 87d99d90 82ac60f9 82a73e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19   STACK_COMMAND:  kb  FOLLOWUP_IP:  ndis!ndisPassIrpDownTheStack+3d 85829ab1 3d03010000      cmp     eax,103h  SYMBOL_STACK_INDEX:  9  SYMBOL_NAME:  ndis!ndisPassIrpDownTheStack+3d  FOLLOWUP_NAME:  MachineOwner  MODULE_NAME: ndis  IMAGE_NAME:  ndis.sys  DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf58  FAILURE_BUCKET_ID:  0x5_VRF_ndis!ndisPassIrpDownTheStack+3d  BUCKET_ID:  0x5_VRF_ndis!ndisPassIrpDownTheStack+3d  Followup: MachineOwner ---------  2: kd> lmntsm start    end        module name 853a2000 853ea000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F) 8b610000 8b66a000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62) 85421000 85432000   amdppm   amdppm.sys   Mon Jul 13 19:11:03 2009 (4A5BBF07) 85531000 8553a000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F) 8b60e000 8b60f440   AsIO     AsIO.sys     Mon Dec 17 04:10:20 2007 (47663CFC) 85505000 8550e000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13) 8550e000 85531000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16) 859b5000 859bd000   AtiPcie  AtiPcie.sys  Tue May 05 11:00:16 2009 (4A005480) 859f6000 859fd000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC) 8b600000 8b60e000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8) 8522e000 85236000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2) 8557f000 8559e000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C) 85278000 85323000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8) 85990000 859b5000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18) 85236000 85278000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E) 85779000 857d6000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427) 859bd000 859ca000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E) 8b77f000 8b7e3000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC) 8b7e3000 8b7fb000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8) 8b773000 8b77f000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214) 8597f000 85990000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20) 859d5000 859de000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 859ca000 859d5000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 859de000 859ef000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 902ab000 90362000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1) 90362000 9039b000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265) 8556e000 8557f000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) 8553a000 8556e000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11) 857e4000 857ed000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12) 8594d000 8597f000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55) 85b4e000 85b7f000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43) 82e16000 82e4d000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07) 85945000 8594d000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05) 80bc8000 80bd0000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA) 85766000 85779000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C) 85910000 85935000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6) 9039b000 903ab000   L1C62x86 L1C62x86.sys Mon Jul 27 03:06:45 2009 (4A6D5205) 85212000 8521d000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89) 854ef000 85505000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F) 855bf000 855ca000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E) 853f3000 853fb000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D) 8573b000 85766000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F) 8b769000 8b773000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) 85935000 85945000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6) 8581b000 858d2000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58) 8b6d3000 8b6e1000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912) 8b66a000 8b69c000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52) 858d2000 85910000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63) 855ca000 855d8000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23) 8b75f000 8b769000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48) 82a06000 82e16000   nt       ntkrpamp.exe Sat Feb 27 02:33:35 2010 (4B88CACF) 8560c000 8573b000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45) 859ef000 859f6000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10) 902a9000 902aa040   nvBridge nvBridge.kmd Fri Jul 09 17:10:11 2010 (4C379033) 8f82b000 902a8dc0   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162) 8b6a3000 8b6c2000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916) 8546e000 8547f000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27) 85439000 85463000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14) 854da000 854e1000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17) 854e1000 854ef000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13) 857d6000 857e4000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E) 8521d000 8522e000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0) 8b71e000 8b75f000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2) 857ed000 857f5000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4) 857f5000 857fd000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3) 85600000 85608000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5) 85bcf000 85bfc000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A) 8b6e1000 8b6fb000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D) 85bc7000 85bcf000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB) 85a05000 85b4e000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E) 855ef000 855fa000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C) 855d8000 855ef000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A) 8b70e000 8b71e000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF) 85400000 85421000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B) 85463000 8546e000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B) 85800000 8580c000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E) 8559e000 855bf000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D) 85b7f000 85b87380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C) 8547f000 8548f000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8548f000 854da000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D) 85b88000 85bc7000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26) 8b6c2000 8b6d3000   vwififlt vwififlt.sys Mon Jul 13 19:52:03 2009 (4A5BC8A3) 8b6fb000 8b70e000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956) 8580c000 85819000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A) 85323000 85394000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28) 85394000 853a2000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8b69c000 8b6a3000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F) 853ea000 853f3000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)

LukeCai

Memtest is running now. Should probably leave it running all night...

As of recently, there is no antivirus installed - at least, there shouldn't be. Could rule that out as a possible culprit.

EDIT: It's been one pass completed so far, and no errors detected.

CarlTR6

Let us know the results after at least seven scan cycles. Follow Jonathan's suggestion regarding the PC Probe Utility.

LukeCai

The test stopped because a child stopped it and booted the OS to run Meebo. Bah.

Running the test now. It's at 21% of the first pass, and I have over one million errors recorded, and they're not stopping. Red has flooded the bottom half of the screen.

ttran

Can you take a picture of the screen?

With that many of error, it's hard to deny that memory is not the issue.
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.
There are some good Ram expert in this forum, I will contact them to help you ok?

LukeCai

I shut the test off when it hit the three million mark.

There are only two DIMM slots on the mobo - and I only have two 2 GB sticks. Seeing as this is definitely a hardware issue, and the parts are still under warranty, is there anything I can do to improve the situation short of shipping stuff back?

I'll run memtest again, but it stopped at 21% of pass 0, at 97% of the test. Errors were found up to 64.1M.

ttran

Quote:

is there anything I can do to improve the situation short of shipping stuff back?

Sorry my english is not really good so I'm not sure what you meant by that. But if it is under warranty, If I were you, I would contact them immediately

LukeCai

Business isn't open on Sunday. I'll contact them tomorrow.

Thanks for your help in this matter. I don't think there are many more useful software based solutions.

ttran

�� Quote: Originally Posted by LukeCai

Business isn't open on Sunday. I'll contact them tomorrow.

Thanks for your help in this matter. I don't think there are many more useful software based solutions.

Because today is Sunday...so if you have time can u follow my suggestion above. 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. I know you have only 2 slot but if by chance, you can find one good stick, or might be both of your mobo slots are bad?? It might worth a try........But yes, contact them tomorrow please!

Dave76

Hi LukeCai,

Sorry to see your computer problems.

It would be best to do another couple of checks, you wouldn't want to RMA the Ram and wait for the new ones to arrive just to have the computer do the same thing.

You need to test for bad RAM cards and bad motherboard slots.

I would suggest to take out one of the RAM cards and run the Memtest86 again, pull that RAM card and put the other one in the other slot and run Memtest86 again.
If either RAM card starts getting a lot of errors, just stop the test and let us know the results.
If one of the RAM cards passes and the other one fails, put the RAM card that passed into the slot that failed and run Memtest86 again.

Let us know the results.

Edit:
Can you give us some information on your computer?
OEM or Custom built?
Laptop or desktop?
Info on the processor, motherboard, RAM, Graphics card or on-board graphics, hard drive/SSD.
BIOS version?

This will help us analyze other possible issues.

CarlTR6

Luke, Ttran and Dave are right. Follow this advice and test one stick at a time. You need to know whether your RAM is bad or the motherboard has a faulty slot.

LukeCai

OEM or Custom built?
Custom built
Laptop or desktop?
Desktop
Info on the processor, motherboard, RAM, Graphics card or on-board graphics, hard drive/SSD
CPU: AMD PHENOM II X4 925 2.8GHZ RETAIL
RAM: A-DATA GAMING SERIES 2GB DDR3 1600
MOBO: ASUS M4A78LT-M LE AM3 DDR3 ATI 3000
Graphics: PALIT GEFORCE 9500GT 1GB PCI-E
PSU: 450W POWER SUPPLY ATX
HDD: 500 GB SATA II 3.0 GB 16MB 7200RPM
And you know about my external HD, with updated drivers.
BIOS version?
BIOS was not updated. I'll look for the version when memtest is done.

LukeCai

Attached are the memtest results - this is with both sticks of RAM installed. It looks like one of the slots is failing.

I tested each individual stick on the 'good' slot for 3 passes each - no errors show up them. But errors immediately appear when I use both slots.

ttran

Based on what you just described as well as with what you described earlier about (the child stop the test and meebo etc..), it's possible that mobo slot is bad. But with only 3 pass, it's hard to conclude that way even though compared to previous test (1st pass show many error), 3 pass should be enough.
Well...at least you have some things to talk to them tomorrow right?

Good Luck

Tuan

Dave76

�� Quote: Originally Posted by LukeCai

Attached are the memtest results - this is with both sticks of RAM installed. It looks like one of the slots is failing.

I tested each individual stick on the 'good' slot for 3 passes each - no errors show up them. But errors immediately appear when I use both slots.

Looks like there might be a MOBO slot, lets confirm it.

Both RAM cards have passed in one of the slots, lets call it Slot A, If your 100% sure which RAM card failed in Slot B, then put the other RAM card in Slot B and run memtest, If not 100% sure test both RAM cards in Slot B.
If you start to get many errors you can stop the test.

If both RAM cards pass both slot tests, One RAM card in one slot at a time, total of four separate tests. Then there is a compatibility issue or they need some BIOS changes.

It is definitely possible for both RAM cards to pass memtest when individually tested in each slot, but fail when two RAM cards are tested at the same time. Which means the slots are good, the voltage and/or timings need adjusted or the RAM is not compatible with your MOBO.

Can you give us the RAM part number?
This will help in checking for compatibility with your MOBO.

LukeCai

Or it could be a controller issue on the board or a PSU voltage issue (what's the vintage of that machine, btw?). I'd have them test a separate, known-good PSU and run the mem tests again to see if they still fail. Also worth fiddling with the voltage #s in the BIOS to make sure the memory is getting appropriate juice (and not too much, of course, as well). Dave's idea is a sound one, but I'd add the PSU to the suspect list as well, especially if both cards work fine in slot one on their own. Usually a mobo with a bad memory controller or slot on the board starts throwing 124 WHEA errors pretty quickly, although it's not a given. Just my experience with these.

LukeCai

The settings in the BIOS for memory voltage are overvoltage only (standard at 1.5V). What is a stable voltage? (450 power supply).

I've tested the individual ram sticks in the good slot, to 3 passes apiece - they had no errors. At this point, I'm running stable with only one DIMM active.

Dave76

The RAM is one of these things:

Newegg.com - A-DATA Gaming Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model AX3U1600GB2G9-2G

Guest

Did you run memtest with both RAM cards, one at a time, in the suspected bad slot (slot B)?

After testing the suspected bad slot, run with one RAM card and see if it is stable.

Good point cluberti, if the OP has access to a PSU it's a good idea to try.

LukeCai

I ran one stick in the bad slot, it showed errors after 2 passes or so. I took a photo, but the flash all but ruined the image that time.

It was the same kind of error though. Memory address failure.

Dave76

Did you run the other RAM card in the bad slot to confirm that it is bad, let us know if it has errors?

This will confirm a bad slot on the MOBO.

Let us know the results.

Edit:
I just reviewed the thread, again, you said the RAM voltage was 1.5v, this is low for an AMD board.

This RAM is listed for i5 and i7 boards and for AMD3 boards. This has been a cause of RAM issues for others.
The i5 and i7 boards generally run RAM at 1.5v to max 1.65.
The AMD boards generally run RAM at 1.65v or higher.

If your RAM is set at 1.5v, one reference states this RAM is rated at 1.55v - 1.75v.

It's worth a try to bump the voltage for the RAM.

First, D/L CPUZ, open it and post the CPU, Memory and SPD tabs.

I will review your MOBO manual and info on the RAM before we start to increase the voltage.

Let us know the CPUZ info.


Information from your Ram website:
IC Configuration: 128M x8

Information from your MOBO manual, page 1-12:
This motherboard does not support DIMMs made up of 256 megabits (Mb) chips or less.

The MOBO manual doesn't list your RAM on the compatible list.

The A-DATA RAM from the MOBO manual list for DDR3-1600MHz capability:
A-Data AD31600X002GMU 4096MB(Kit of 2) DS Heat-Sink Package 7-7-7-20 1.75-1.85V

You mentioned previously that all the parts are still under warranty, I would recommend to return the RAM and get some from the compatible list of your MOBO manual.
Even if we get this to run, you'll likely have more compatibility issues with the RAM you have now.

LukeCai

EDIT: Disregard that, you guys were right. It's a compatibility problem.

Attached is my CPU-Z.

The RAM stick that I removed reads:
DDR3-1600G
CL: 9-9-9-24
Voltage: 1.55-1.75V
AX3U1600GB...

LukeCai

The RAM seems to be 'acceptable' at least for my motherboard - I'm back to thinking that either the RAM sticks interact with each other in a way that creates memory address errors, or that the DIMM slot on the motherboard is bad.

Either way, I think I have to run those memtests again for the full 7 passes.

Dave76

Take a screen shot of the CPUZ tabs mentioned above, with the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.

Then post using this method.
How to Post a Screenshot in Seven Forums

This will give us some information needed to continue.

You should be monitoring you CPU temperatures when running Prime95 or memtest86.
D/L Core Temp and have it open when testing.

Can you confirm that your RAM voltage is set to 1.5v?

When you have RAM settings, voltages and timings, which are not adjusted and tested correctly this can cause stability issues including what your are experiencing.
This may be only part of the resolution to your issues.

We still need to confirm your BIOS settings, a good start is with the CPUZ tabs, CPU, Memory, SPD.
Please post these, the CPUZ file you attached does not have the information required to proceed.

Quote:

the RAM sticks interact with each other in a way that creates memory address errors, or that the DIMM slot on the motherboard is bad.

These two possibilities need to be addressed.
The first part, how the RAM interact with each other and with the system will depend on several things. The voltage being the one that should be looked at first. Let's get the information on the RAM before we start.

Once everything is confirmed the next step is to adjust the voltage.
If your RAM voltage is set to 1.5v, you need to manually set it to 1.55v then run memtest86, if you still get errors then increase it to 1.6v and run memtest86 again, do not exceed 1.75v.

Read your MOBO manual BIOS section, linked above, to find out where to do this.

Even if we get it to run better, it may continue to give errors and BSoDs.
This is due to the compatibility of the RAM with your MOBO, of the RAM you have.

LukeCai

Attached are the images.

SPD only for slot 2 because the computer crashes if I put anything in slot 1.

Dave76

This is the problem when the RAM manufacturer tries to make their products work on everything.

Monitor CPU temps with Core Temp, or equivalent program while testing.

Once everything is confirmed the next step is to adjust the voltage.

Start with one RAM card in the good slot, slot 2.

If your RAM voltage is set to 1.5v, you need to manually set it to 1.55v then run memtest86, if you still get errors then increase it to 1.6v and run memtest86 again, do not exceed 1.75v.

Read your MOBO manual BIOS section, linked above, to find out where to do this.

When you stop getting BSoD then run the test with RAM card in the previous bad slot, slot 1.
If that passes then run memtest86 with both RAM cards installed.

Let us know the results.

LukeCai

BIOS set to overvoltage level of 1.56 V.

DIMM slot 1 still produces errors on memtest, with both RAM sticks.

Dave76

Set the RAM voltage to 1.6v and run memtest86 again.
If your still getting errors and/or BSoDs, set the RAM voltage to 1.65v and run memtest86 again.

When testing one RAM card in slot 2, is it passing memtest86?

Be sure to monitor your temperatures.

From your RAM website:

Quote:

Suitable for: Desktop PCs
Module Type: 240Pin Unbuffered-DIMM Non-ECC
Capacity Available: 4GB Dual Channel Kit (2GBx2)?2GB Dual Channel Kit (1GBx2)?2GB Kit (2GBx1)?1GB Kit (1GBx1)
IC Configuration: 128M x8
Transmission Bandwidth: 12800MB/Sec?PC3-12800?
Cas Latency Timing: 9-9-9-24
Working Voltage: 1.65V~1.85V

Can you add your system specs to the dropdown box in the lower left corner of your posts?
This help all the members here to easily see them when giving suggestions

LukeCai

Slot 2 hasn't produced errors yet, at least not for the tests I've run - 3 passes at 1.5V with both sticks, and 3 passes at 1.56V.

I'll update my system specs and increase the voltage more.

ttran

�� Quote: Originally Posted by LukeCai

Slot 2 hasn't produced errors yet, at least not for the tests I've run - 3 passes at 1.5V with both sticks, and 3 passes at 1.56V.

I'll update my system specs and increase the voltage more.

Good to hear that you are trying Dave great advise, at least we are trying to do everything

Dave76

Good job on the specs, this will help all that view this thread.

Good information that slot 2 is working.

It's possible that the voltage bump will help slot 1.

Let us know how the testing is going.

LukeCai

When I upped the voltage above 1.6V, the bluescreens return on the 'good' DIMM slot. Memtest often hangs, and is never able to get to 7 complete passes.

Minidumps of those crashes attached.

This is probably motherboard failure - the computer company would probably be barraged with phone calls if all of their systems were sold undervoltage.

Dave76

Put the DRAM voltage back to 1.56v.

Let's bump the Chipset Over Voltage +0.1v from the current setting.

Test again.

Edit:
How far above 1.6v did you go?

LukeCai

When I got to about 1.65V, the BIOS would tell me at startup that overvoltage failed.

Whatever the case, the manufacturer is sending me a new mobo. That should resolve things, despite any voltage settings.

Dave76

The memory controller voltage bump should help with stability.

At this stage it looks like there are still four possibilities, incompatible RAM, memory controller or motherboard slot problem, graphics card, and last but still a possibility a PSU problem.

These are things to remember if the new MOBO still gives errors.
With your CPU NB VID Control bumped 0.1v, try the DRAM voltage at 1.7v.
If the new MOBO still gives errors replace the RAM with one from the MOBO compatible RAM list.

Hopefully the new MOBO will solve the problem, let us know the outcome.

CarlTR6

Luke, you have done a very good job of following suggestions. I hope the new mobo is the answer to your problems.