FridgidDreams
New Member
- Joined
- Oct 4, 2014
- Messages
- 16
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {5e0fbbc, f, 1, fffff801dbfadb57}
*** WARNING: Unable to verify timestamp for cpuz137_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz137_x64.sys
Probably caused by : cpuz137_x64.sys ( cpuz137_x64+1ff2 )
Followup: MachineOwner
Hi,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {5e0fbbc, f, 1, fffff801dbfadb57} *** WARNING: Unable to verify timestamp for cpuz137_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz137_x64.sys Probably caused by : cpuz137_x64.sys ( cpuz137_x64+1ff2 ) Followup: MachineOwner
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. As you can see the probable cause is CPU-Z:
cpuz137_x64.sys Mon Feb 17 14:22:16 2014: Latest version of CPU-Z stands at 1.70 and can be obtained here:
http://www.cpuid.com/softwares/cpu-z.html
Most of your drivers look absolutely fine apart from:
dfx11_1x64.sys Tue Aug 28 20:10:34 2012: Power Technology's DFX Audio Enhancer. Try here for a later driver:
Link Removed
usbglcs1100301.sys Fri Mar 09 08:31:24 2012: I'm not exactly sure what this is as information seems scant. Googling gave me this:
http://systemexplorer.net/file-database/file/usbglcs1100301-sys Does it ring any bells for you?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {7fffefc, f, 0, fffff8027e62bbb0}
*** WARNING: Unable to verify timestamp for cpuz137_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz137_x64.sys
Probably caused by : cpuz137_x64.sys ( cpuz137_x64+2073 )
Followup: MachineOwner
Same as before... Have you at least tried removing GPU-Z? If not I'd try as it isn't unknown for it to cause the odd issue. (I'm also a little puzzled by the cpu-z being displayed instead of gpu-z. I even searched and the info came back as cpu-z.)Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {7fffefc, f, 0, fffff8027e62bbb0} *** WARNING: Unable to verify timestamp for cpuz137_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz137_x64.sys Probably caused by : cpuz137_x64.sys ( cpuz137_x64+2073 ) Followup: MachineOwner
I did a little more searching on the mystery usbglcs1100301.sys and it does look like it's to do with your mouse. Your mouses website is here:
Link Removed
I'm unsure whether the driver found on the web site is a later version than yours but might be worth trying anyway.
Just in case any corruption has crept in try running the system file checker. Open an admin command prompt and type:
sfc /scannow
Press enter and await results.
If the SFC comes back with files it couldn't repair then again in an admin command prompt run this command:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results. This can sometimes take a while to run through so please be patient.
If removing GPU-Z or replacing the above driver doesn't stop the BSOD then it's probably worth trying the driver verifier but let's see how you get on with the above first as running the verifier under win 8 is slightly different than win 7.
I doubt it will remove the CPU-Z but do run it anyway.
So I did a sfcscan and got "windows resource protection did not find any integrity violations." so I guess that's at least good haha, and by removing it you mean deleting the cpu-z stuff from the registry right? as deleting the so called location it's being called from isn't possible as it doesn't exist >..<Hmm...I'm not so sure and I'd try removing it as a test anyway. It did appear in the dump file after all and not just once.
Your computer thinks it does..
Hmm... no don't mess with the registry as that may cause other issues. Try removing that application I mentioned above Frigid and see if it helps any.Well I know that lol, so should deleting the registry file for it possibly fix it? didn't really give me a yes/no on that.
Hmm... no don't mess with the registry as that may cause other issues. Try removing that application I mentioned above Frigid and see if it helps any.
Ok understood... Well I guess it's now a wait and see. If it does bsod again I'll be interested to see the cause this time around.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {55ffba0, f, 0, fffff801265aabb0}
*** WARNING: Unable to verify timestamp for cpuz137_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz137_x64.sys
Probably caused by : cpuz137_x64.sys ( cpuz137_x64+2073 )
Followup: MachineOwner