*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
*** WARNING: Unable to verify timestamp for VVBackd5.sys
*** ERROR: Module load completed but symbols could not be loaded for VVBackd5.sys
*** WARNING: Unable to verify timestamp for ambakdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ambakdrv.sys
*** WARNING: Unable to verify timestamp for hotcore3.sys
*** ERROR: Module load completed but symbols could not be loaded for hotcore3.sys
*** WARNING: Unable to verify timestamp for oodisr.sys
*** ERROR: Module load completed but symbols could not be loaded for oodisr.sys
*** WARNING: Unable to verify timestamp for oodivd.sys
*** ERROR: Module load completed but symbols could not be loaded for oodivd.sys
*** WARNING: Unable to verify timestamp for EUBKMON.sys
*** ERROR: Module load completed but symbols could not be loaded for EUBKMON.sys
*** WARNING: Unable to verify timestamp for cumon.sys
*** ERROR: Module load completed but symbols could not be loaded for cumon.sys
Probably caused by : usbehci.sys ( usbehci!EHCI_PollAsyncEndpoint+8 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {e180c5f0, 2, 0, 804dc25d}
Unable to load image WRkrn.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WRkrn.sys
*** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys
Probably caused by : GUBootStartup.sys ( GUBootStartup+c54 )
Followup: MachineOwner
Hmm.. to be honest it is always more desirable to have the latest drivers. Admittedly some older hardware may run better on a particular driver compared to another but that's usually quite rare. Also apps that update the drivers automatically are fine if they are something like the Intel auto updater or the official Dell updater but those third party apps one can download are to be avoided. You'd be better off finding each driver yourself. You get to know the system better and your system will be happier overall. Personally I back my drivers up by keeping a copy on a different drive just in case I need to reformat or something get's corrupted then I always have a copy.the consensus of techies seems to be don't do it unless you have to, that you can make a terrible mess.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {fffffffb, 0, 8054b732, 0}
Unable to load image ialmnt5.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ialmnt5.sys
*** ERROR: Module load completed but symbols could not be loaded for ialmnt5.sys
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for ialmdev5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL
Probably caused by : ialmnt5.sys ( ialmnt5+9dd1 )
Followup: MachineOwner
Ref:Cause
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
XPlite Professional can completely uninstall Clear the File Protection DllCache and reinstall to repair Clear the File Protection DllCache on:
- Windows XP Professional: orig, SP1, SP2
Looking at the Intel driver update result you posted it seems it couldn't update the graphics driver because of the generic driver already installed.
Do you remember where you got the driver from?
You'd be better off finding each driver yourself. You get to know the system better and your system will be happier overall.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
*** WARNING: Unable to verify timestamp for VVBackd5.sys
*** ERROR: Module load completed but symbols could not be loaded for VVBackd5.sys
*** WARNING: Unable to verify timestamp for ambakdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ambakdrv.sys
*** WARNING: Unable to verify timestamp for hotcore3.sys
*** ERROR: Module load completed but symbols could not be loaded for hotcore3.sys
*** WARNING: Unable to verify timestamp for oodisr.sys
*** ERROR: Module load completed but symbols could not be loaded for oodisr.sys
*** WARNING: Unable to verify timestamp for oodivd.sys
*** ERROR: Module load completed but symbols could not be loaded for oodivd.sys
*** WARNING: Unable to verify timestamp for EUBKMON.sys
*** ERROR: Module load completed but symbols could not be loaded for EUBKMON.sys
*** WARNING: Unable to verify timestamp for cumon.sys
*** ERROR: Module load completed but symbols could not be loaded for cumon.sys
Probably caused by : usbehci.sys ( usbehci!EHCI_AllocNpPool+1b )
Followup: MachineOwner
Use the same instructions for other drives. Simply right click on the drive you want to test and go from there.The instructions at that page on using command prompt are good, but they don't tell how to do it for a drive other than C.
This is a folder created by windows on installation and contains files needed to repair or upgrade the system:Have you heard of the I386 file?
Use the same instructions for other drives. Simply right click on the drive you want to test and go from there.
Note: chkdsk c: /r presumes that the disk upon which you wish to run Error Checking is your C: Drive (most often)
I'm going to ask a friend to give your thread a look over for a second opinion because I would hate to give you the wrong advice.