Problem Event Name: BlueScreen! Help!

[opsori]

I'm frequently getting this Bluescreen problem and PC restarts

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA800103F4A0
BCP3: 000000000000FFFF

BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\033112-15100-01.dmp
C:\Users\User\AppData\Local\Temp\WER-26364-0.sysdata.xml

Already read the previously submitted threads on this topic but that didn't solved my problem. PLEASE! HELP ME !

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, 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.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under 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 (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[opsori]

Here is the recent .dmp file for this problem

 

[zigzag3143]

Here is the recent .dmp file for this problem

Memory management caused by a driver (probably your Kaspersky)

Kaspersky is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.
http://support.kaspersky.com/downloads/utils/kavremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows

 

[opsori]

I removed Kaspersky But still having problem !
here is the last dmp file

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\opsori\040312-15054-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50
Debug session time: Mon Apr  2 13:48:16.985 2012 (UTC - 6:00)
System Uptime: 0 days 0:26:23.701
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 0, 0, 0}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000000000, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d4932c to fffff80002cbaf00

STACK_TEXT:  
fffff880`05f45f48 fffff800`02d4932c : 00000000`0000004e 00000000`00000099 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f45f50 fffff800`02c70557 : 00000000`00000000 fffff680`0006ae60 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`05f45f90 fffff800`02c8f493 : fffffa80`0209c060 fffff700`0000a037 0000007f`fffffff8 fffff8a0`03127a50 : nt! ?? ::FNODOBFM::`string'+0x322be
fffff880`05f46020 fffff800`02c8deee : fffffa80`0209c060 fffffa80`00000026 fffff8a0`00006f1e fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`05f468d0 fffff800`02f9d7af : fffff8a0`081dd060 fffff880`05f46be0 00000000`00000000 fffffa80`020bbb60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`05f46920 fffff800`02f77b3d : 00000000`00000001 00000000`00000001 00000000`fff98000 fffffa80`01b63660 : nt!PspExitThread+0x47f
fffff880`05f469f0 fffff800`02c97a43 : 00000000`00000100 fffffa80`020bbc20 00000000`00000001 fffff800`02cc225d : nt!PsExitSpecialApc+0x1d
fffff880`05f46a20 fffff800`02c97e80 : 00000000`00000000 fffff880`05f46aa0 fffff800`02f78710 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`05f46aa0 fffff800`02cba1f7 : fffffa80`020bbb60 00000000`00000284 00000000`00000000 fffffa80`033cd9a0 : nt!KiInitiateUserApc+0x70
fffff880`05f46be0 00000000`73d52dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0137ee88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73d52dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d4932c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

Your Ethernet network driver is out of date. I suspect it was partially to blame for Kaspersky causing problems. Please fill in your system specs so we can help you find an update for your driver: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

Also, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html so we can determine what network adapter you have.


You may also have RAM problems.

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.