Random BSOD occured with different error

Hi,

You need to run MemTest86+ for a minimum of 8 passes. Do that, then report back on the results.

RAM - Test with Memtest86+

Regards,
Golden

Code:

Start Menu\Programs\Trend Micro Titanium Internet Security	USER-PC\User:Start Menu\Programs\Trend Micro Titanium Internet Security	USER-PC\User

Security App

For testing purpose please remove Trend Micro Titanium Internet Security and replace with Security Essentials. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free

   Information

DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

Make full scans with both separately.

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Troubleshoot Application Conflicts by Performing a Clean Startup
Startup Programs - Change

Disk Check

Disk Check for errors on your Hard drive(s): Disk Check

How many passes did you run memtest for? It may take more than 20 passes to show the errors.

1. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
2. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
3. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
4. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup

-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

Temperature

For monitoring heat of the system, use Speccy or HWMonitor:
Speccy System Information
HWMonitor

This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

ASMMAP64.sys Thu Jul 2 15:13:26 2009 (4A4C7A36)
LENOVO ATK Hotkey ATK0101 ACPI UTILITY
http://www.carrona.org/drivers/driver.php?id=ASMMAP64.sys

The below is for information purposes only. Contains relevant information from the blue screen analysis:

Code:

Debug session time: Mon Apr 29 22:18:01.524 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\043013-66440-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 14:10:13.378
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
BugCheck 1A, {41287, 30, 0, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
	Parameter 2 contains the referenced virtual address.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+454f5
MaxSpeed:     2200
CurrentSpeed: 2195
BiosVersion = K43SM.401
BiosReleaseDate = 01/04/2012
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K43SM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Apr 25 16:58:56.261 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042513-26192-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 9:51:02.299
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+6aec99 )
BugCheck 3B, {c0000094, fffff8800f702c99, fffff8800516f2f0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000094, Exception code that caused the bugcheck
Arg2: fffff8800f702c99, Address of the instruction which caused the bugcheck
Arg3: fffff8800516f2f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+6aec99
MaxSpeed:     2200
CurrentSpeed: 2195
BiosVersion = K43SM.401
BiosReleaseDate = 01/04/2012
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K43SM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Apr 16 14:48:28.972 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\041613-64225-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 7:01:17.877
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
BugCheck 1A, {41287, 30, 0, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
	Parameter 2 contains the referenced virtual address.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+454f5
MaxSpeed:     2200
CurrentSpeed: 2195
BiosVersion = K43SM.401
BiosReleaseDate = 01/04/2012
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K43SM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr  8 09:38:42.236 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\040813-18766-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 3:04:47.143
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BugCheck 4E, {99, 440db, 3, a6b6}
BugCheck Info: PFN_LIST_CORRUPT (4e)
Bugcheck code 0000004E
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000440db, page frame number
Arg3: 0000000000000003, current page state
Arg4: 000000000000a6b6, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
MaxSpeed:     2200
CurrentSpeed: 2195
BiosVersion = K43SM.401
BiosReleaseDate = 01/04/2012
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K43SM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Apr  6 12:52:28.272 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\040613-66768-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 4:56:23.178
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
BugCheck 24, {c08a5, 0, 0, 0}
BugCheck Info: NTFS_FILE_SYSTEM (24)
Bugcheck code 00000024
Arguments: 
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155
MaxSpeed:     2200
CurrentSpeed: 2195
BiosVersion = K43SM.401
BiosReleaseDate = 01/04/2012
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = K43SM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Code:

**************************Mon Apr 29 22:18:01.524 2013 (UTC + 6:00)**************************
amdxata.sys                 Fri Mar 19 22:18:18 2010 (4BA3A3CA)
ASMMAP64.sys                Thu Jul  2 15:13:26 2009 (4A4C7A36)
asmthub3.sys                Thu Jun  2 08:27:58 2011 (4DE6F52E)
asmtxhci.sys                Thu Jun  2 08:27:46 2011 (4DE6F522)
athrx.sys                   Thu Jul  8 15:03:45 2010 (4C359471)
atkwmiacpi64.sys            Wed Sep  7 07:44:52 2011 (4E66CC94)
btath_bus.sys               Thu Jun 24 12:17:43 2010 (4C22F887)
GEARAspiWDM.sys             Fri May  4 01:56:17 2012 (4FA2E2E1)
HECIx64.sys                 Tue Sep 21 22:59:04 2010 (4C98E458)
iaStor.sys                  Tue Sep 14 07:23:32 2010 (4C8ECE94)
intelppm.sys                Tue Jul 14 05:19:25 2009 (4A5BC0FD)
kbfiltr.sys                 Mon Jul 20 15:21:42 2009 (4A643726)
nvhda64v.sys                Thu Jul  7 22:21:14 2011 (4E15DCFA)
nvlddmkm.sys                Tue Nov  8 20:10:55 2011 (4EB9386F)
PassGuard_x64.sys           Wed Jul 27 13:10:44 2011 (4E2FB9F4)
Rt64win7.sys                Thu Jan 13 17:57:19 2011 (4D2EE89F)
RTKVHD64.sys                Tue Aug 16 16:44:43 2011 (4E4A4A1B)
RtsUVStor.sys               Tue Mar 15 15:59:04 2011 (4D7F3868)
rzdaendpt.sys               Mon Mar  4 12:48:41 2013 (513443C9)
rzudd.sys                   Mon Mar  4 12:48:31 2013 (513443BF)
rzvkeyboard.sys             Mon Mar  4 12:48:38 2013 (513443C6)
Sftfslh.sys                 Fri Sep 30 22:43:06 2011 (4E85F19A)
Sftplaylh.sys               Fri Sep 30 22:43:05 2011 (4E85F199)
Sftredirlh.sys              Fri Sep 30 22:43:14 2011 (4E85F1A2)
Sftvollh.sys                Fri Sep 30 22:42:46 2011 (4E85F186)
SynTP.sys                   Fri May  6 08:28:49 2011 (4DC35CE1)
tmactmon.sys                Wed Jul 21 13:31:24 2010 (4C46A24C)
tmcomm.sys                  Wed Jul 21 13:31:15 2010 (4C46A243)
tmevtmgr.sys                Wed Jul 21 13:31:15 2010 (4C46A243)
tmtdi.sys                   Tue Jul 20 14:58:07 2010 (4C45651F)
TurboB.sys                  Sat Apr 17 05:07:26 2010 (4BC8EDAE)
VKbms.sys                   Thu Sep 30 22:16:33 2010 (4CA4B7E1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Apr 25 16:58:56.261 2013 (UTC + 6:00)**************************
cnnctfy2.sys                Fri Jun 24 21:29:01 2011 (4E04AD3D)

These are some links you could peruse:

Thermal Paste and How To Use It | techPowerUp
Avoid Static Damage to Your PC | PCWorld
Power Supply Information and Selection - Tech Support Forum
Basic computer troubleshooting
How To Clear CMOS
How to clean your PC of dust and dirt
How to clean a computer

TVeblen said:

What you are experiencing is a TDR event (Timeout Detection & Recovery). There are many causes of these events, mostly hardware related. Please read my checklist below and see if you can diagnose your particular cause.

A couple of things jump out immediately. Your specs say you have 5GB of RAM, an odd number. That suggests that you added some RAM at some point. Mismatched or failing RAM modules can cause TDRs. You might want to test those sticks one at a time in Slot 1 before anything else. RAM problems can explain some of your other issues too.

Looking at some of your other posts I see you are running dual monitors also. This could be exposing a defect in your 9500GT that is triggering the TDRs. You should test with only one monitor attached to see if this is the case.

You are running lots of stuff on that box, so I would be as deliberate as possible in doing the diagnostic work.

*******
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

The order you do the diagnostics is not all that important. My personal strategy is to do the cheap & easy stuff first, the cheap & harder stuff next, and then the stuff that costs last. But whatever order you do it in you need to check or confirm the following:

SOFTWARE
Poorly written software and games will cause TDRs. But if this were the case it would affect lots of people, not just a few. Check the game's website & forums for patches and tips.
See if other people in the forums are having the same problem and if they were able to solve it and how.
You could also be asking too much of your video card. Check to see if your video card is tested and recommended for the game/program. Test the game at reduced settings.

WHAT ACTIONS CAUSE THE PROBLEM
It helps if you can isolate the actions that trigger the TDR. Most often it will be an application using 3D graphics. But if the incidents occur constantly it would point more towards defective hardware. If it happens more specifically (just when running Game X) it points towards overheating, settings, software, or driver issues.

GENERAL SYSTEM PERFORMANCE
You need to eliminate the possibility that your computer has a global problem. You can use a program like Prime95 to stress test your system. Free Software - GIMPS
You can run the "Stress Test" for a few hours or overnight. This will not tell you what the problem is, but it is helpful to uncover any issues your system has with instability and cooling.

OVERHEATING
Running a video intensive game for hours can generate some serious heat and overheating will cause video errors. You can check your temps by looking at your BIOS readings or use a free program like Speedfan SpeedFan - Access temperature sensor in your computer .
A real easy test is to just pull the side panel(s) off your case (You can also blow a house fan directly into the open case) and see if the problem goes away or gets better. If it does then the issue is definitely overheating. If you are overheating you need to look at installing some cooling upgrades. You want to look at ventilating the case (more or bigger fans), Upgrade your case to a larger gaming case (lots of fans, water-cooling), etc.
There are free utilities like BurninTest PassMark BurnInTest software - PC Reliability and Load Testing that you can use to test your system's cooling capability. Caution is recommended using these types of programs.

VIDEO DRIVERS
Bad drivers happen and they can get corrupted. Before installing or reinstalling any video drivers first completely uninstall all video software and the drivers. (Some people say to run a cleaner program from safe mode, some say this is unnecessary). Never rely on the driver package to overwrite the old drivers. Also: Delete the video driver folder (ex: C:\NVIDIA) in Windows Explorer (or windows may install the same drivers again!).
After uninstalling the old drivers and rebooting Windows 7 will install it's own WDDM 1.1 driver. Check for the video problem while using the generic Windows driver.
You can then install the latest drivers for your card (or try older drivers).
See This Tutorial: Installing and updating drivers in 7

DEVICE MANAGER
Look in Device Manager and make sure there are no problem devices (yellow ! icon). Correct these by loading the correct drivers or disable the problem device and see if the video problem goes away.

POOR CONNECTIONS
Reseat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

CHECK YOUR MOTHERBOARD VOLTAGES
In BIOS, check the listed voltages against the manufacturer recommended specs. Reset the voltages to factory defaults and see if the video problems disappear.

MEMORY
Memory errors can cause video problems. Run a program like Memtest86+ for at least 3 passes to see if there are any memory errors. Memtest86+ - Advanced Memory Diagnostic Tool .
You can also test for a bad memory module by installing one stick and testing, and then switch it out for the next stick, etc.

OVERCLOCKING
Overclocking can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

UNDERCLOCKING
Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the TDRs. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor perforning card in the W7 enviroment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

BIOS
Check for and install an updated BIOS, particularly if it says the newer BIOS corrects memory errors or bug fixes. You could also try loading the BIOS defaults.
While you are there, check the motherboard manufacturers forums to see if others are having issues with the same board.

WINDOWS POWER MANAGEMENT
Eliminate Power Management settings as a possible cause, especially if you are working with a laptop. These settings could be particularly important if the issue is in playing games.
Go to Control Panel > Hardware & Sound > Power Options. Under "Select a Power Plan" you will find that "Balanced" is the default setting.
At the bottom you will see a Down arrow next to "Show Additional Plans". Click that and select "High Performance". See if the TDR issue is affected.
Alternately, you can click "Change Plan Settings" next to the "Balanced" plan and change the setting to "Never" put the computer to sleep (This is the default on a desktop) and/or change when the display is turned off as a test.

POWER SUPPLY
You need to know that your power supply is delivering sufficient power. Power supply problems are the most common cause of video problems, especially using high end cards.
Check the power supply's amperage ratings. Be sure it has the ample amperage for your video card and the rest of the system.
Test the supply with multimeter to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I tested my power supply by hooking up my multimeter to the PCI-E connectors that I was using to power my video card (I used a spare pair from the power supply to run the card while I was testing). I then observed the meter while I used the computer, first watching the voltage, then the amps, to see if there was any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

VIDEO CARD
I suspect that a video card must perform flawlessly to operate in a Windows 7 environment and run the most recent games. If you tried all the above diagnostics and no problems were found then that leaves you with only one possibility: a defective video card. Some brands have the problem more consistently than others. You could check their forums for clues.
You could try your card in another computer running W7 to see if the problem goes along with the card.
You could try a different card in your computer. I bought an inexpensive card to use. My TDR's disappeared using a "lesser" card. Or borrow a card from another computer.
Otherwise RMA or replace the card.

TDR complaints have come from PC owners running virtually every PC configuration. They occur regardless of which video engine, manufacturer, driver, or system used. They are too numerous to write off as a random problem, but at the same time if people are getting their systems to run correctly using the same hardware and software that you are then it follows that your problem must be solvable.

More Info Here:
Timeout Detection and Recovery of GPUs through WDDM
NVIDIA Statement on TDR Errors - NVIDIA Forums
27116: ATIKMDAG has stopped responding error message

Jounouchi said:

Sorry but may I know what is the real problem that my PC faced for blue screen?

As my PC is always having computing therefore it is maintain around 80C.

Is it become the possible for overheating and blue screen?

Finding the exact cause of a blue screen is not easy.
I am calling my hardware friends to have a look at your thread.

Heat can and does cause BSODs, maybe not in your case. Please follow the directions KoolKat linked to about cleaning dust and dirt and how to clean, OK?
Since it is a laptop I don't recommend you try replacing thermal paste unless you are an experienced technician.
What part is 80C? That is very hot.