Good day ladies and gents,
As the title says, I think one of my USB drivers may be causing the issue. I don't recall why, but a long time ago I did go into verifier.exe and remove all information (shut it off). With this issue, I did go out to Etron and download the latest drivers, uninstalled and deleted the old drivers, rebooted, and installed the Etron USB 3.0 drivers. The reason I believed it was USB drivers is because after inserting a USB pen-drive into a port, no others will be recognized. This is the only issue I noted. When I turn on Verifier.exe with standard config, I get a BSOD within a few minutes. For purpose of data collection, I turned on mini-dumps (no overwrite), set Verifier to run standard config, and allowed the PC to BSOD three times today purposefully. Yesterday it BSOD'd twice before I decided to collect three dumps today for this post.
I can (and am) running my PC with Verifier not monitoring any drivers. However, if someone out there enjoys looking through the attached BSOD data files comes up with an idea, and/or cares to explain how they recognized it, that'd be great. My IT expertise has never delved into the realm of .dmp files.
I am fighting against the Win10 upgrade as long as possible. I can work on them, but I don't like the new interface or restrictions... Though the Bash interface capability is pretty cool.
Thanks!
Cody
As the title says, I think one of my USB drivers may be causing the issue. I don't recall why, but a long time ago I did go into verifier.exe and remove all information (shut it off). With this issue, I did go out to Etron and download the latest drivers, uninstalled and deleted the old drivers, rebooted, and installed the Etron USB 3.0 drivers. The reason I believed it was USB drivers is because after inserting a USB pen-drive into a port, no others will be recognized. This is the only issue I noted. When I turn on Verifier.exe with standard config, I get a BSOD within a few minutes. For purpose of data collection, I turned on mini-dumps (no overwrite), set Verifier to run standard config, and allowed the PC to BSOD three times today purposefully. Yesterday it BSOD'd twice before I decided to collect three dumps today for this post.
I can (and am) running my PC with Verifier not monitoring any drivers. However, if someone out there enjoys looking through the attached BSOD data files comes up with an idea, and/or cares to explain how they recognized it, that'd be great. My IT expertise has never delved into the realm of .dmp files.
I am fighting against the Win10 upgrade as long as possible. I can work on them, but I don't like the new interface or restrictions... Though the Bash interface capability is pretty cool.
Thanks!
Cody
My Computer
At a glance
Microsoft Windows 7 Ultimate 64-bit 7601 Mult...AMD FX(tm)-8150 Eight-Core Processor14.00 GBNVIDIA GeForce GTX 1070
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- CyberPowerPC
- OS
- Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
- CPU
- AMD FX(tm)-8150 Eight-Core Processor
- Motherboard
- Gigabyte Technology Co., Ltd. GA-970A-D3
- Memory
- 14.00 GB
- Graphics Card(s)
- NVIDIA GeForce GTX 1070
- Sound Card
- (1) USB Audio Device (2) SB Audigy (3) NVIDIA High Defin
- Screen Resolution
- 1920 x 1080 x 32 bits (4294967296 colors) @ 60 Hz
- Hard Drives
- (1) Samsung SSD 850 EVO 250G SATA Disk Device (2) Samsung SSD 850 EVO 250G SATA Disk Device (3) WDC WD20 EZRX-00D8PB0 SATA Disk Device (4) Generic- Compact Flash USB Device (5) Generic- MS/MS-Pro USB Device (6) Generic- SD/MMC USB Device
- Cooling
- Cooler Master Hyper 212 Evo
- Keyboard
- G910 Orion Spectrum
- Mouse
- Razer Death Adder
- Internet Speed
- Broadband
- Antivirus
- Microsoft Security Essentials