BSOD Physical MemoryDump

[llerrej]

Hello, I've recently started experiencing BSOD talking about memory dumping.
I was just browsing the internet and playing pokemon on an emulator when it crashed.
I've read about how to troubleshoot it but earlier after installing updates for the drivers it crashed again..

I'm running Windows 7 ultimate 32 bit

MOBO:
CPU: AMD Athlon II X2 245 2.91Ghz
Vid Card: Nvidia Geforce 9500 GT

 

[zigzag3143]

Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

 

[llerrej]

I updated all my drivers and replaced Avast with the antivirus you gave but it still crashes..
attached is the latest dump file. thanks!

 

[writhziden]

Possible out of date drivers:

AsIO	8e102000	8e103440	Wed Dec 21 01:55:21 2005 (43a91879)	000045df		AsIO.sys
nvstor	88907000	8892c000	Wed May 20 00:44:09 2009 (4a13a6b9)	00023198		nvstor.sys

AsIO.sys
nvstor.sys

Loading Dump File [D:\Kingston\BSODDmpFiles\llerrej\032212-28563-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82a04000 PsLoadedModuleList = 0x82b4c810
Debug session time: Thu Mar 22 07:03:44.757 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:30.395
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00001097, (reserved)
Arg3: 0074006f, Memory contents of the pool block
Arg4: 8997fb08, Address of the block of pool being deallocated

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 82b6c718
Unable to read MiSystemVaType memory at 82b4c160

These are typically due to Drivers...

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 203956
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.