New
#21
Sorry, question. The point of the driver verifier is to get more information in a BSOD right? So should I just run it and get 3-5 BSOD and report back? Thanks.
Sorry, question. The point of the driver verifier is to get more information in a BSOD right? So should I just run it and get 3-5 BSOD and report back? Thanks.
Yes run the verifier and it should throw up a few BSOD's and hopefully find a buggy driver.
Then post back and hopefully we can help further.
Cheers
Dave
Thanks. Well this was fast. :) I got 4 BSODs when trying to boot, so now I'm in safe mode but I want to confirm, in driver verifier I can delete existing settings, correct? I want to confirm this won't lose the data that we're trying to get.
No dont select delete existing settings, select Create custom settings (for code developers)
Also Post the new dump files, for ease navigate to:
C:\windows\minidumps
cheers
Dave
What I mean is that i followed the driver verifier instructions (created custom setting, for code developers, enabled Standard settings, Force pending I/O requests, and IRP Logging, etc.) Those setting resulted in BSODs when I attempted to boot.
So now I'm in safe mode and want to turn off driver verifier. As per the instructions I should delete existing settings, but I don't know if there are data logs or anything that I need to export before I delete local settings.
Ahhh sorry, i understand now :)
Run the SF Tool again and post the new logs, then go back into Safe Mode and
carry on as per instructions. Im not sure what settings Verifier deletes tbh, (maybe just its own settings)
so probably best to upload the logs first (then you can tell me if the logs have been deleted
after you disabled verifier - for future reference :))
cheers
Dave
Ah sorry, didn't follow instructions exactly. I did delete local settings from driver verifier before running SF Tool again. Before I deleted it though, I looked at the minidump log, and noticed that only 1 of the 4 BSOD was recorded. I do remember though that all 4 BSOD listed bugcheck C9 as the culprit. Perhaps if it is the same error it is only recorded as a minidump file once?
Either way, attached is the new SF log. If this doesn't give good info, I can run driver verifier again and upload SF log before deleting local settings. Thanks!
From the latest crash dump:
Driver verifier caught HIDCLASS.SYS as the offending driver.*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {23b, fffff88004568710, fffff98005f1ccf0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
fffff880`04566000 fffff880`0457f000 HIDCLASS HIDCLASS.SYS Sat Nov 20 10:43:49 2010 (4CE7A665)
fffff880`0457f000 fffff880`04587080 HIDPARSE HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9)
(usually a USB driver, possibly Bluetooth)
Run SFC again to check the integrity of all Windows 7 system files:
Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt
(Note: there is a space between SFC and /scannow)
https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Please look to update all Plug and Play/USB device drivers and Bluetooth drivers associated with your computer.HidBatt HID UPS Battery Driver Kernel 7/13/2009 7:31:06 PM
HidBth Microsoft Bluetooth HI Kernel 7/13/2009 8:06:52 PM
HidIr Microsoft Infrared HID Kernel 7/13/2009 8:06:23 PM
HidUsb Microsoft HID Class Dr Kernel 11/20/2010 5:43:49 AM
BTHMODEM Bluetooth Serial Commu Kernel 7/13/2009
Please navigate to Start>Computer>System properties
Select Device Manager in left pane
Expand Human Interface Devices.
Post a snapshot of the expanded devices.
Check windows updates (optional also) for any Bluetooth / USB related updates.
Also try unplugging all USB devices not needed and see if your issue exsists?
https://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
Post back any results / observations.
Cheers
Dave
Also please update driver Razor BlackWidow:
Image name: RzSynapse.sys Relates to: Razer Synapse Engine/Razer Naga
Timestamp: Wed Apr 06 14:59:13 2011 (4D9C3269)
http://www.razersupport.com/index.php?_m=downloads&_a=view
cheers
Dave
My UBS devices are a R.A.T. 7 mouse and a Razor Black Widow keyboard. Both were out of date, which is a good sign haha. I downloaded and installed the most recent drivers for both. I then ran a game which had been consistently crashing on me (starcraft 2) and I got through a game fine. So hopefully this is the answer! I will keep you posted.
Edit: I also ran SFC again with no issues.