BSOD IRQL/Memory Management/everything else

[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-

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]

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]

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]

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.

 

[cluberti]

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.

 

[LukeCai]

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

 

[Dave76]

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.