BSOD - STOP 0x0000001e (While Doing Anything it Seems)

[Phyralis]

Getting this BSOD error while doing pretty much anything.

Attached is the required information/files.

Specifications
- x64 (64 bit)(Ultimate)- Windows 7 is the original OS
- Full retail copy
- hardware ranging from about 3/4 years to a few days
- OS installed a few days ago
- Radeon 4850 HD
- Ripjaw 8GB DDR3 1600 MHz Dual Channel
- AMD Athlon II x4 2.9 GHz

 

[usasma]

Perfmon reports that drivers for your coprocessor haven't been installed. Please visit the PC Manufacturer's website and download and install the chipset drivers for your system ( http://www.nvidia.com/object/nforce-vista-win7-64bit-15.56-driver.html ). Then run another perfmon /report to ensure that the update has succeeded.

You only have 55 updates after SP1, most systems have 70 or more. Please visit Windows Update and get all available updates (language packs aren't necessary).

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.
Please uninstall the AMD OverDrive program as it can cause BSOD's on your system.
If it's the stand-alone app, uninstall it via Control Panel...Programs...Uninstall a program
If it's in the AMD VISION Engine Control Center, you can uninstall it using the AMD uninstall tool (or uninstall the entire AMD VISION Engine Control Center application through Control Panel

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Western Digital software dates from 2008, please uninstall it.
Your nVidia Ethernet Networking Driver dates from 2008 also. You can download the latest chipset drivers (which include the ethernet driver) from here: NVIDIA DRIVERS 15.56 WHQL

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012812-26234-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 02:04:51.596 2012 (UTC - 5:00)
System Uptime: 0 days 7:46:30.943
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = V1.7
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012812-35625-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Jan 28 16:38:14.048 2012 (UTC - 5:00)
System Uptime: 0 days 13:08:24.470
Probably caused by : ntkrnlmp.exe ( nt!IopXxxControlFile+2fb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  launcher.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!IopXxxControlFile+2fb
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`033e028b fffff880`07a9e040 00000000`00000000
BiosVersion = V1.7
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012712-45812-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan 27 23:56:38.316 2012 (UTC - 5:00)
System Uptime: 0 days 0:10:58.738
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+45 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFullDeleteLcb+45
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06d97408 fffff880`06d96c70 fffff800`02e9fd27
BiosVersion = V1.7
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012712-38718-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 27 17:18:27.587 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:57.962
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+2b9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiCommitThreadWait+2b9
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ee0139 fffff880`091940a0 00000000`00000000
BiosVersion = V1.7
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012712-42015-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 27 17:15:12.968 2012 (UTC - 5:00)
System Uptime: 0 days 0:05:17.296
*** WARNING: Unable to verify timestamp for nvm62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x64.sys
Probably caused by : nvm62x64.sys ( nvm62x64+4974 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nvm62x64+4974
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`07d31b40 00000000`00000000 00000000`00000000
BiosVersion = V1.7
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012712-31000-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 27 16:30:16.697 2012 (UTC - 5:00)
System Uptime: 0 days 0:14:09.150
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = V1.7
BiosReleaseDate = 03/03/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[Phyralis]

Hello Usasma,

Thank you for the fast and in-depth response.

After checking with perfmon, it seems I have successfully installed my coprocessor drivers. A little side question; what is a coprocessor?

I have also disabled AMD OverDrive, but not uninstalled. On this, I am a bit lost. I can uninstall the whole AMD Vision Engine Control Center, but I cannot find how to uninstall just the Overdrive aspect. When I use the AMD uninstall tool, it does not allow me to uninstall that specifically, unless it is called something else.

As for the Western Digital software, I cannot find this anywhere. Not in control panel, search, or program files. I do, however, remember windows update installing software for me, but it claims to be an update from January 2011 (not 2008). I can copy the details from the windows update for you:

Western Digital Technologies - Other hardware - WD SES Device
Installation date: ‎1/‎28/‎2012 12:36 PM
Installation status: Successful
Update type: Recommended
Western Digital Technologies Other hardware software update released in January, 2011
More information:
Winqual Help
Help and Support:
Select a Product Solution Center

Lastly, I believe the first link you gave me for the coprocessor drivers solved the outdated nVidia Ethernet Networking Driver being outdated, correct? Both links lead to the same driver package.

Thank you for your help.

 

[usasma]

Yes, both links were the same. I do the analysis in a certain order, and it's not uncommon for the results of one part to need the same "fix" as the results of another part (and that usually means that it's the source of the issues you're having).

Leave AMD OverDrive as is (disabled). It's a fairly new implementation of an old program - and it's causing me a lot of headaches here on the forums. I installed the stand-alone beta version on my system and was immediately greeted by a BSOD - and I couldn't boot the system until I went into Safe Mode and fixed it there.

Microsoft accepts drivers from manufacturer's (for Windows Update) under the presumption that they are going to work. After all, who knows the device better than those who designed/built it. There is a certification program, but it's not the easiest thing to accomplish (the Microsoft WHQL certification) - so most manufacturer's skip it.

At times, this'll result in problems. My system received a 2005 driver (ASACPI.sys) from Windows Update - and this is a know BSOD issue. Some Sony systems would receive a 2007 version of SFEP.sys - which is also known to cause BSOD's. But overall, it's a good system and it works well.

That being said, I never rely on Windows Update for driver updates when I'm having problems. I always visit the website of the folks who manufactured the device.

So, just keep an eye on the Western Digital drivers for now. No need to remove them unless you're having problems.

Good luck!