Random 0x0000001e KMODE_EXCEPTION_NOT_HANDLED

pabvr81 · 26 Jan 2012

Hello Everyone,

I recently purchased an Asus G53SX Notebook, and I keep getting BSOD's at least daily. Some of them refer to ndis.sys, nvlddmkm.sys, ntoskrnl.exe, tcpip.sys and Ntfs.sys. I suspect it might be some RAM modules that the store owners added to the laptop before I purchased it. So far, I upgraded the BIOS to the latest version, upgraded the graphics card drivers, checked memory for errors with the Windows utility (No errors). Most of them are KMODE_EXCEPTION_NOT_HANDLED. Please help me and let me know if you need more info.

System Specs:

ASUSTeK Computer Inc. G53SX
Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
BIOS Date: 12/20/11 09:47:09 Ver: 04.06.03
Total Memory: 16,00 GB PC3-10700
NVIDIA GeForce GTX 560M

zigzag3143 · 26 Jan 2012

pabvr81 said:

Hello Everyone,

I recently purchased an Asus G53SX Notebook, and I keep getting BSOD's at least daily. Some of them refer to ndis.sys, nvlddmkm.sys, ntoskrnl.exe, tcpip.sys and Ntfs.sys. I suspect it might be some RAM modules that the store owners added to the laptop before I purchased it. So far, I upgraded the BIOS to the latest version, upgraded the graphics card drivers, checked memory for errors with the Windows utility (No errors). Most of them are KMODE_EXCEPTION_NOT_HANDLED. Please help me and let me know if you need more info.

System Specs:

ASUSTeK Computer Inc. G53SX
Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
BIOS Date: 12/20/11 09:47:09 Ver: 04.06.03
Total Memory: 16,00 GB PC3-10700
NVIDIA GeForce GTX 560M

These crashes were caused by memory corruption (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+

2-Driver verifier

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/Win7 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 "Special Pool", "Force Pending I/O Requests" and "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:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

mgorman87 · 26 Jan 2012

Please disable driver verifier

How old is "recently purchased"? Are you still under warranty? If you are, I would look into a warranty exchange since new computers shouldn't be crashing like this

One crash blamed your Trend Micro Internet Security driver. Please uninstall and replace with MSE
Unistall tool - Antivirus Uninstallers
MSE - Microsoft Security Essentials - Free Antivirus for Windows

The other crashes are blaming your video card. I think there is a newer one then the one you have

Code:

nvlddmkm.sys Sat Oct 15 02:07:55 2011 (4E99233B)

NVIDIA DRIVERS 285.62 WHQL

Code:

Event[2868]:
  Log Name: System
  Source: Disk
  Date: 2012-01-20T20:42:25.961
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Clásico
  User: N/A
  User Name: N/A
  Computer: Usuario-PC
  Description: 
El controlador detectó un error de controladora en \Device\Harddisk1\DR2.

Please run a hard drive scan
Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 13:21:58.571 2012 (UTC - 5:00)
System Uptime: 0 days 1:27:49.524
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  coreServiceShe
FAILURE_BUCKET_ID:  X64_0x1E_0_VRF_nt!KiKernelCalloutExceptionHandler+e
BiosReleaseDate = 12/20/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G53SX
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 23 19:11:04.540 2012 (UTC - 5:00)
System Uptime: 0 days 6:25:27.493
*** 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+1168ec )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_VRF_nvlddmkm+1168ec
BiosReleaseDate = 12/20/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G53SX
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 22 22:18:47.370 2012 (UTC - 5:00)
System Uptime: 0 days 2:24:53.323
*** WARNING: Unable to verify timestamp for tmcomm.sys
*** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys
Probably caused by : tmcomm.sys ( tmcomm+672c )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_tmcomm+672c
BiosReleaseDate = 08/15/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G53SX
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 22 00:15:44.017 2012 (UTC - 5:00)
System Uptime: 0 days 0:09:43.969
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+360 )
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_VRF_dxgmms1!VidSchiProcessDpcCompletedPacket+360
BiosReleaseDate = 08/15/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G53SX
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 20 22:32:55.073 2012 (UTC - 5:00)
System Uptime: 0 days 0:53:25.914
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+1a0 )
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonClose+1a0
BiosReleaseDate = 08/15/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G53SX
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 20 16:56:48.048 2012 (UTC - 5:00)
System Uptime: 0 days 0:42:31.000
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BiosReleaseDate = 08/15/2011
SystemManufacturer = ASUSTeK Computer Inc.
SystemProductName = G53SX
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

zigzag3143 · 26 Jan 2012

In one of the DMPs coreServiceShield (trend micro) was running at the time of the crash. There is an issue you can read more about here [Hot Fix] B1181 - My computer slows down and CoreServiceShell.exe consumes high CPU usage after installing Titanium 2011

pabvr81 · 28 Jan 2012

Thank you all for your help. I uninstalled Trend Micro and replaced it with MSE as suggested. I also upgraded the Nvidia drivers (Used drive sweeper first). I also enabled the driver verifier, the PC crashed as soon as Windows started and It wouldn't let me log in. I disabled it in Safe Mode. Upon performing the memory test, it reported 6 errors on test #5. Hard drive tests with Seagate tools were passed with no errors. The Laptop is only 2 weeks old so it's still under warranty so I will exchange it, since most likely is the RAM that is causing the problem.