Over 1 million tech questions and answers.

BSOD Fairly Often. Driver Verifier Enabled = BSOD on Boot Every Time

Q: BSOD Fairly Often. Driver Verifier Enabled = BSOD on Boot Every Time

I have a relatively new computer that I've built and I've been getting BSOD's for a while.

At first I thought it was because the pagefile was disabled, but that was just why they weren't getting logged to MiniDump. Then I got it enabled again and now I'm getting a lot of BSODs. It's been 0x3b ntoskrnl exe lately, but when I enabled driver verifier I was getting a different BSOD on each boot.

One of them specifically mentioned a .sys that I can't exactly remember. it was XXhalp.sys or something, and when I Googled it - everyone was talking about deleting monitor profiles from the registry and that somehow old monitor profiles were causing the BSODs, so I donno about that.

I would appreciate any help you can offer. I'll be actively monitoring this (and I'm currently in safe mode with driver verifier still enabled). So just let me know what you need.

Thanks,

Pseudo

RELEVANCY SCORE 200
Preferred Solution: BSOD Fairly Often. Driver Verifier Enabled = BSOD on Boot Every Time

I recommend downloading and running DAP. It can help sort out any driver and firmware related issues on your system

It's worked out well for many of us in the past.

You can download it direct from this link http://downloaddap.org. (This link will open the download page of DAP so you can save a copy to your computer.)

A: BSOD Fairly Often. Driver Verifier Enabled = BSOD on Boot Every Time

Is there anything I can do to get someone to take a look at this?

Read other 9 answers
RELEVANCY SCORE 126.4

Okay so I got a random BSOD one time, I can't remember which one it was to post the details because I've had so many of them whilst running Driver Verifier lol. Basically when I start Driver Verifier and my PC restarts - as soon as it gets to the desktop it BSOD's. The only way I can stop it is by going into safe mode and disabling Driver Verifier. Can provide anymore info if needed.

Included report.

Thanks :x.

A:BSOD every time windows starts with Driver Verifier enabled.

Thread title: BSOD every time windows starts with Driver Verifier enabled.

Well, that is what is to happen. Is there any specific reason that you enabled Driver Verifier? Let us know. Driver Verifier is a very sophisticated tool designed for troubleshooting only. Driver Verifier is not a tool to mess with or to experiment with unnecessarily or to play with. Disable it. Run the computer normally.

If your computer BSODs with Driver Verifier not enabled, let us know; troubleshooting will be needed in that case.

Read other 1 answers
RELEVANCY SCORE 109.2

Hi

I am experiencing many BSOD's lately. This is the latest one.

Any help/advice greatly appreciated.

Regards

Warren

System info

- Vista Ultimate
- X86
- Original OS
- OEM but have disk
- 09/2008
- Intel Core 2 Duo E8400
- NVIDIA GeForce 9800 GT
- Gigabyte G31MF-S2

A:BSOD - Driver verifier enabled - Vista SP2 x86

Hi -

I ran the 9 most recent dumps.

Norton named as probable cause - remove it with Norton Removal Tool.

http://jcgriff2.com/NRT_N360_Removal.html

Update these drivers -

Code:

nvlddmkm.sys Fri May 01 02:10:11 2009 (49FA9243) - NVIDIA GeForce 9800 GT - http://www.nvidia.com/Download/index.aspx?lang=en-us
nvBridge.kmd Fri May 01 01:41:25 2009 (49FA8B85) - NVIDIA GeForce 9800 GT - http://www.nvidia.com/Download/index.aspx?lang=en-us

NuidFltr.sys Wed Aug 15 04:14:02 2007 (46C2B5CA) - Microsoft Intellipoint mouse driver - http://www.microsoft.com/hardware/do...px?category=MK

speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F) - SpeedFan - http://www.almico.com/sfdownload.php
giveio.sys Wed Apr 03 22:33:25 1996 (316334F5) - SpeedFan - http://www.almico.com/sfdownload.php

Rtlh86.sys Mon Jun 25 01:37:23 2007 (467F5493) - Realtek Ethernet - http://www.realtek.com.tw/DOWNLOADS/...&GETDOWN=FALSE
RTKVHDA.sys Thu Feb 14 04:02:28 2008 (47B403A4) - Realtek HD Audio - http://www.realtek.com/downloads/dow...&GetDown=false


Remove these apps and webcam -

Code:

usbVM31b.sys Thu Aug 05 06:05:00 2004 (4112064C) - vm301b intelli kingstone usb vimicro USB PC camera (zc0301PL) - NO Vista drivers

TBPanel.SYS Fri Jul 26 19:01:04 2002 (3D41D4B0) - Cardex TBPanel video conversion app

mxopswd.sys Fri Jan 05 20:37:29 2007 (459EFD59) - Maxtor One Touch


If BSODs persist, run the Driver Verifier -- http://jcgriff2.com/driver_verifier.h... Read more

Read other 16 answers
RELEVANCY SCORE 92.4

Hi running Windows 7 64 bit home premium.

Enabled driver verifier as I was getting BSOD, cannot boot into Windows because of the STOP error 0x0000000A IRQL not less or equal, have loaded system defaults and still no joy.

AMD 1090T X6 with 8GB 2x4Gb of crucial tactical tracer elite RAM SPD at 1333Mhz 1.5V 9-9-9-24-33-jedec

GTX470SOC and 3 HDD'S 1TB boot drive Western Digital Caviar, Seagate ST 500Gb and maxtor 300gb IDE

Did get into windows once and there was a driver crash that was something to do with a HUWEAI dongle that I had installed something to do with a usb ew filter as I recall.

Dongle has been removed, XBOX 360 and a wireless keyboard still attached to USB with nothing else connected other than toslink for sound and monitor cable DVI to HDMI.

Full stop code is (0xfffff98001562ff8 0x0000000000000002 0x0000000000000001 0xfffff8000302e1ae)

Am sure I can get back into windows with system restore disc but am worried that something is seriously wrong if I still get this error despite setting everything to defaults??

Please advise, many thanks.

A:BSOD 0x0000000A After enabling driver verifier, cannot boot windows

Forgot to mention AHCI is activated, don't know if that matters, using default MSAHCI drivers

The driver that faulted in windows was ew_usbenumfilter, the dongle has a couple of other drivers around here called ew_hwusbdev and also ewusbmbb

Main concern is the stop error however, how come it wouldn't boot??

Looking in Windows system 32 seems there are a lot of drivers for this mobile broadband dongle device:

ew_hwupgrade.sys

ew_jubusenum.sys

ew_jucdcacm.sys

ew_juddcecm.sys

ew_juextctrl.sys

ew_juwwanecm.sys

ewdcsc.sys

ewusbmdm.sys

ewusbwwan.sys

Read other 3 answers
RELEVANCY SCORE 87.6

I get a BSOD only when gaming Heroes of Newerth which really only uses a small portion of my computers power, other games I have not noticed any issues (although I dont game other games much). Movies and general computering does not cause any BSOD.

I did a Driver Verifier BSOD came up hidclass.sys saved.. Arghh I had to do a system restore when I came back to windows and it deleted the mini dump! I've attached a old ones and will re-do driver verifier if requested.

I did a windows ram test and HDD test for C: and no issues noticed.

I'm new to this whole process but tried to figure it out on my own first any help is much appreciated!

Windows 7 - 64 bit, Windows was the original OS, Pre-Installed. System is 3 years old same as OS.


? CPU - AMD Phenom II X4 955 Black Edition Deneb 3.2GHz
? Video Card - XFX HD-487A-ZWFC Radeon HD 4870 1GB 256-bit GDDR5 PCI Express 2.0 x16
? MotherBoard - ASUS M4A79XTD EVO AM3 AMD 790X ATX AMD Motherboard
? Power Supply - brand & wattage - OSZ 700watt Model: OCZ700MXSP

? System Manufacturer - My self
? Exact model number (if laptop, check label on bottom)

A:BSOD while gaming - Driver Verifier makes BSOD hidclass.sys

I've tried to set up a Driver Verifier mini dump but when I activate it it makes a bluescreen when I come back. I follow the instructions to then go back to my system restore point but when I do it then removes the dump file. My assumption is that now I want for another natural BSOD and then upload that dump? Or should I redo the Driver Verifier and in safe mode upload the dump files?

Read other 2 answers
RELEVANCY SCORE 87.6

Hello,
As the thread shows im having lots and lots of little(and big) crashes.

Im attaching the SF log and any help will be appreciated

Many thanks,
Dimitris

A:BSOD-PC Freezes randomly-Driver Verifier BSOD's at User Log-On

Added a zip file with three minidumps as i forgot that ive changed the default location of systemroot/minidump to a different disk as im not using virtual memory on os disk

Read other 7 answers
RELEVANCY SCORE 86.8

Hi All

Have been following a number of threads to identify my issue. I can only assume that a driver is at fault as when i run verifier i have to start in safe mode. Attached is my mini dump, can anyone help me identify where the issue is?

Thanks a lot

Lordmwa

EDIT - Added the full lot of info from the diagnostic tool

A:Random BSOD, ran driver verifier now got 0x000000c9 BSOD

Hi lordmwa.

It appears that you have driver verifier enabled. And the verifier detected the Logitech Camera driver, twice, in two crash dumps.

Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {6, 103, fffff98005bb4870, 0}

*** WARNING: Unable to verify timestamp for lv302a64.sys
*** ERROR: Module load completed but symbols could not be loaded for lv302a64.sys
Probably caused by : lv302a64.sys ( lv302a64+15e1 )

Followup: MachineOwner
---------
And the driver is old enough.

Code:
fffff880`06b6c000 fffff880`06b6e400 lv302a64 T (no symbols)
Loaded symbol image file: lv302a64.sys
Image path: \SystemRoot\system32\DRIVERS\lv302a64.sys
Image name: lv302a64.sys
Timestamp: Fri May 01 04:11:07 2009 (49FA2903)
CheckSum: 0000515F
ImageSize: 00002400
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
First, disable Driver Verifier. Then update the logitech drivers from Logitech Support - Downloads, Manuals, FAQs & More.

It is a Desktop PC, and magicISO is not a must for it. I w... Read more

Read other 4 answers
RELEVANCY SCORE 86.8

Recently my computer has started seriously acting up by first disabling all directx and d3d functionality it took a full driver uninstall and reinstall to make that functional again but my computer is still having bsod issue's I don't understand where this came from it happened out of nowhere my 6950 is also overheating for some reason also out of the blue its pushing 103-105C in directx11 games which it usually never hit over 60-70C in on ultra settings which is the new temp the card idles at with the case open and fans pointed at it. I am now moving from a software issue to assuming hardware failure. I need second opinions here please help me.

A:BSOD's in driver verifier, BSOD's on C:/ disk check (os hdd) & more.

Security App

Crashes indicate Symantec being a possible cause. Remove Symantec and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free



   Information
DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.
Hard Drive/Storage

Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition

How to Upload and Post a Screenshot and File in Seven Forums
Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - Disk Check
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Heat:
-Only use the laptop on a hard surface with nothing blocking any of the vents.
-Use a laptop cooling pad if possible
-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not h... Read more

Read other 1 answers
RELEVANCY SCORE 85.2

Yesterday i popped in my motherboard cd and installed asus suite II and reinstalled the Renesas usb 3.0 drivers, Updated my BIOS to a more recent version and raised my ram speed from 1333 to 1866mhz. A short while after this my computer BSOD and it said PFN_LIST_CORRUPT. I used seagate tools to check my hard drive for problems, it came back clear. Chkdsk didnt fix anything. Right now im making a IMAGE of my hard drive and are going to use seagate tools to fix any corrupted sectors. after this PFN_LIST_CORRPUT bsod a few hours later another bsod came on saying "A driver attempting to corrupt the system has been caught. The faulty driver currently on the kernel stack must be replaced with a working version." This second BSOD was caused by the driver verifier i activated, so i shut off driver verifier to prevent it from making any future BSODS. Dump File PFN_LIST_CORRUPT: (https://app.box.com/s/pqnice03kzf2m6pxgb87)

If you want the dump file for the driver verifier BSOD feel free to ask, thank you!

A:PFN_LIST_CORRUPT BSOD, Driver Verifier BSOD

Heres the DM log i just made, Its for 3 BSODS.

Read other 9 answers
RELEVANCY SCORE 83.6

Hi
Thanks in advance for any help. This has happened quite often, but I think I don't often know as he just restarts. Here is info as per guidance. Also, files attached.

Windows 7 Home Premium SP1. 64 bit. Installed by Dell on this new laptop computer.
Dell XPS L502X
System only 3 weeks old.

CPU: i7-2670QM 2.20ghz turbo boost up to 3.1ghz
Memory: 6.144Mb
Graphics card: 2GB NVIDIA GeForce GT 540M Graphics Card
HD: 750GB serial ATA 7200rpm

Have replaced free McAfee 1 month trial with ZoneAlarm Internet Security Suite 10.0.250.000. (Had a BSOD problem when I installed ZA before uninstalling McAfee and had to uninstall McAfee in safe mode. Then thought all resolved.)

Have installed Open Office, Chrome, Firefox. There are some other things installed such as WinRar. My son has installed a couple of things, but as he does not have Admin rights, this is limited.

Thanks

A:BSOD - son's computer so activity at time unknown. Fairly frequent.

Hello shaggydog,

* Your crash log indicates you STILL have the following malware programs installed.

*Kaspersky
Please remove it
http://support.kaspersky.com/downloa...vremover10.zip

* Remove Zone Alarm
http://download.zonealarm.com/bin/fr...cpes_clean.exe

* We recommend that you install MSE for testing purposes
Microsoft Security Essentials - Free Antivirus for Windows

*Also note your Video driver was involved & needs to be reinstalled with the newest version.
When upgrading your graphic driver you MUST remove all traces of the current driver.
In order to do that we recommend using
Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

Read other 4 answers
RELEVANCY SCORE 82.4

I have had BSOD for a while and being super busy I did not have time to look at it and get it fixed. Well Being a computer guy I assumed I could fix it myself. But with tons of research and trying to use every guide I can find I decided to try here(probably should have came here first). Today I started Driver Verifier and having it check all drivers. It crashed a couple times before I realized it was a process I had to stop. I then came here to try and get some help sorting out the driver. Thank you in advance for any and all help anyone provides.

A:Multiple BSOD. Driver Verifier Driver caught a driver corrupting

Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80083058f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------
0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.

If overclocking, reset all overclocks back to their default settings and then follow these:

RAM - run for a minimum of 8 consecutive passes
RAM - Test with Memtest86+

CPU - run the HIGH test
CPU - Stress Test Using IntelBurnTest

Video - run the FURMARK test for 20mins
Graphics Card Problems - Diagnose
Video Card - Stress Test with Furmark

Storage - run the SHORT test using the DOS version
SeaTools for DOS and Windows - How to Use

Read other 1 answers
RELEVANCY SCORE 82

So yeah, I was having some BSOD problems and enabled the driver verifier( for all drivers, no less) without really knowing what I was getting into. Needless to say, I now BSOD and immediately restart long before getting into Windows, and I'm not given the opportunity to even enter safe mode.

It's saying "The IO Manager has detected a violation by the driver being verified" etc., though it's not naming a driver file.

At any rate, I'm just interested in getting back into Windows, so at the moment I'm simply looking to disable it.

I have a startup disk which I have used to enter the recovery console where I in turn went into command prompt. Using verifier.exe, I was able to bring the application up again. However, that one doesn't actually seem to be active; I assume this is because running it in the recovery console checks the recovery console registry/whatever instead of that of the windows installation on the boot drive.

I think I'm at the point where I'll need to manually edit the registry to deactivate the driver verifier, which I'm not entirely sure how to do given the circumstances. I haven't tried using regedit yet, but I suspect that would just default to the recovery program's registry anyway. Besides, I don't know which key it is. So now that I have a command prompt, what do I do next?

A:Accidentaly(kinda) enabled driver verifier

Did you set a restore point first?

If so use the recovery disk and restore the point set just before enabling Verifier, if not see if there is an older one set.

Read other 5 answers
RELEVANCY SCORE 81.6

So recently I've ran driver verifier, my pc crashed and it displayed BSOD with this written DRIVER_VERIFIER_DETECTED_VIOLATION

After that my pc rebooted and i checked my event viewer and this came out:

The computer was overloaded after a virus scan. Virus scan was:0x000000c4 (0x00000000000000e2, 0xffff870826f58940, 0x000002a7d1cf0080, 0x0000000000000000). The pointer is recorded here: C:\WINDOWS\MEMORY.DMP. Reports Id: 45483b4c-9748-4039-83f5-004370f87ac2.

My windows is not english so i tried to translate this sorry for mistakes. This is original one:

Kompiuteris buvo perkrautas atlikus virusų tikrinimą. Virusų tikrinimas buvo: 0x000000c4 (0x00000000000000e2, 0xffff870826f58940, 0x000002a7d1cf0080, 0x0000000000000000). I?keltis įra?yta čia: C:\WINDOWS\MEMORY.DMP. Ataskaitos Id: 45483b4c-9748-4039-83f5-004370f87ac2.

So what should i do now? What kind of problem is this?

My OS is Windows 10.

A:driver verifier BSOD

Quote:





Originally Posted by Domis


So what should i do now?




You should attend to the other thread you already started here My pc started freezing (hard hanging)

Please do not create multiple threads about the same issue.

Read other 1 answers
RELEVANCY SCORE 81.6

Plz check, thanks for more infos....
It's ntoskrnl.exe
Searching forum and no proper solution.

Startup repair doesn't help - can't fix the problem
sfc /scann... no errors
chkdsk /r ... no errors

A:BSOD after driver verifier

  
Quote: Originally Posted by BuzzFuzz


Plz check, thanks for more infos....
It's ntoskrnl.exe
Searching forum and no proper solution.

Startup repair doesn't help - can't fix the problem
sfc /scann... no errors
chkdsk /r ... no errors


Hello there!

Seems like ATITool64.sys is causing to crashes. Please uninstall it and see if the system crashes again. Then turned off Drivers Verifier

Bugcheck:


Code:
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff980014ab000, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88003ff6192, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------
Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
fffff980014ab000

FAULTING_IP:
ATITool64+6192
fffff880`03ff6192 66833800 cmp word ptr [rax],0

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xD6

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff880033c3af0 -- (.trap 0xfffff880033c3af0)
NOTE: The trap frame does not contain all ... Read more

Read other 4 answers
RELEVANCY SCORE 81.6

I'm running Driver Verifier, based on other posts, due to BSOD with Bad Pool Header error. BSOD has only happened a couple of times, although on several occasions my mouse and keyboard will stop responding and I have to reboot. This made me think that the BSOD might be driver related.
 
Since I started Driver Verifier, programs are running very slow and the fans in the PC seem to be running at top speed. It's the fans running so fast and loud that have me worried. I attempted to turn driver verifier off to see if that made any difference. But I got an error message that said "current operation requires admin privilege."  I am the only administrator on this PC.
 
What is the best thing for me to do now?

A:Driver Verifier & BSOD

Approximately 90% of BSOD's are due to 3rd party drivers
10% or less are due to hardware problems
Less than 1% are due to Windows drivers (on a fully updated system)
 
Driver Verifier is supposed to cause BSOD's - that's it's purpose.
It loads extra routines for the drivers - so it's supposed to slow the system down.
 
Open up verifier.exe from the RUN command
Select "Delete existing settings", then click on the "Finish" button.
Then reboot the system so that the changes can take effect.
 
It is not recommended to just run Driver Verifier without having diagnosed previous BSOD's.
And, depending on the settings that you've used, the results can be interpreted in different ways.
Also, Driver Verifier can expose weakness' in drivers that you won't see in normal mode - so you'll be attempting to diagnose problems that don't even exist.
 
So, my question is..."What is wrong with your system that you decided to run Driver Verifier?"
If it was BSOD's, Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.
If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vis... Read more

Read other 0 answers
RELEVANCY SCORE 81.6

System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid.

Upon enabling driver verifier the system bluescreens before even getting into windows. Startup repair runs but does nothing.

Please help,

CK

win 7 64bit

A:Driver verifier BSOD

  
Quote: Originally Posted by ClintonK


System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid.

Upon enabling driver verifier the system bluescreens before even getting into windows. Startup repair runs but does nothing.

Please help,

CK

win 7 64bit



This was caused bby USBfilter.sys. USBFILTER.sys is a USB upper class filter driver for AMD SB700 chipsets. It detects arrival and removal of USB 1.0/1.1 audio devices. ...

I would update and re-install it

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\110710-21621-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e56000 PsLoadedModuleList = 0xfffff800`03093e50
Debug session time: Sun Nov 7 14:36:21.524 2010 (GMT-5)
System Uptime: 0 days 0:00:15.147
Loading Kernel Symbols
.......................................... Read more

Read other 9 answers
RELEVANCY SCORE 81.6

I was having problems with BSOD while either playing flash games on the internet or using Media Player Classic Home Cinema. After searching the internet for solutions i stumbled upon this site and the thread http://www.techsupportforum.com/foru...ed-473665.html.

I followed the steps and got a BSOD after restarting. You advised in that thread to retrieve the dump file and attach it to the next post. I have no idea where i should post it, so i decided to PM it to you.
I hope you are able to help me with this.

Since this is my fathers PC i am not a 100% sure about everything:
? Vista
? 32bit
? Vista
? Full retail version
? 3+ years old, maybe 4+
? I don't believe so

? 2,40 gigahertz Intel Core2 Quad
? ASUS EAH5450 Series
? ASUSTeK Computer INC. P5B-MX
? AOpen Z400-08FC 400W

? No idea
? No idea

I hope someone can help me with this.

A:BSOD Driver Verifier

Hi -

The VERIFIER_ENABLED dump flagged AsusTek Gamer utility driver; ATI video also named -

Code:
atikmdag.sys Tue May 24 22:36:44 2011 (4DDC6B3C)
atikmpag.sys Tue May 24 22:25:20 2011 (4DDC6890)
ATKDispLowFilter.sys Tue May 13 23:02:50 2008 (482A565A)
Update Asus & ATI drivers -
http://www.sysnative.com/drivers/driver.php?id=ATKDispLowFilter.sys
http://www.sysnative.com/drivers/driver.php?id=atikmpag.sys
http://www.sysnative.com/drivers/driver.php?id=atikmdag.sys

Regards. . .

jcgriff2

`


Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\PalmDesert\AppData\Local\Temp\Temp1_Mini050313-01.zip\Mini050313-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*a:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18805.x86fre.vistasp2_gdr.130308-1436
Machine Name:
Kernel base = 0x82410000 PsLoadedModuleList = 0x82527c70
Debug session time: Fri May 3 11:42:13.812 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:11.796
Loading Kernel Symbols
....................................................
Loading User Symbols
ERROR: FindPlugIns 8007007b
************************... Read more

Read other 3 answers
RELEVANCY SCORE 81.6

Howdy,I have been using the driver verifier lately and its showing me bsod-s so im interested in what is holding my pc down.WhoCrashed says ntoskrnl.exe is causing it but that dosen't mean much to me.If all else fails atleast there aren't many non-windows drivers that I can verify so I guess I could try to verify them one at a time(bsods pop up in 2-3 minutes anyways so I don't have to wait very long) but that way is really tedious.
Have a good one.

A:Driver Verifier BSOD-s

Hi -

Two of the dumps were VERIFIER_ENABLED, yet did not name a 3rd party driver.

Remove Riva Tuner - too old for Windows 7 RTM -

Code:

RTCore64.sys Wed May 25 02:39:12 2005 (42941D90)

Uninstall Daemon Tools/ Alcohol 120. This driver common to both is known to cause BSODs -

Code:

sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)

If BSODs persist, uninstall ESET ESS and install ESET NOD32 anti-virus only.

Windbg Logs
--> http://jcgriff2.net/BSOD_Logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.net/BSOD_Logs/_99-db...riff2_.txt.zip

Regards. . .

jcgriff2


`


BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Oct 19 12:35:56.299 2010 (GMT-4)
System Uptime: 0 days 0:05:25.752
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
BUGCHECK_STR: 0xc4_e3
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: ekrn.exe
Bugcheck code 000000C4
Arguments 00000000`000000e3 fffffa80`058d4b51 00000000`049ef3b4 00000000`00000000
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Oct 19 11:19:16.166 2010 (GMT-4)
System Uptime: 0 days 0:05:32.620
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
BUGCHECK_STR: 0xc4_e3
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: ekrn.ex... Read more

Read other 3 answers
RELEVANCY SCORE 81.6

I was getting some BSODs and I found out that it was due to my Lycosa Keyboard. But even after removing keyboard I am getting BSODs.

My RAM is good (Memtest Pass for 8 hours). My hard disk is good.
I reisntalled OS and installed just main drivers-
1. Intel Rapid Storage Technology
2. Nvidia 8800GTX
3. Realtek Audio
4. Intel Inf Chipset
Now, all my drivers are up to date and BIOS also up to date. When I turned on Driver Verifier to check if everything is fine, it shows BSOD at system loading windows 4 out of 10 times. The worst problem is that it doesn't write the Dump.
Initializing Dump and restart.

DETAILS-
Windows 7 64Bit
Intel Core i7 920
Gigabyte EX58-Extreme Motherbaord (Latest BIOS)
Corsair RAM (2 GB x 3)
Corsair Nova 250GB SATA + 1 TB Western Digital Hard Drive (No RAID)
Nvidia 8800GTX
850W Power Supply (Cooler Master)
Liquid Cooling with no overclocking.

A:BSOD with Driver Verifier

please folow this posting instrunctions:
http://www.sevenforums.com/crashes-d...tructions.html

Read other 2 answers
RELEVANCY SCORE 81.6

So recently I've ran driver verifier, my pc crashed and it displayed BSOD with this written DRIVER_VERIFIER_DETECTED_VIOLATION

After that my pc rebooted and i checked my event viewer and this came out:

The computer was overloaded after a virus scan. Virus scan was:0x000000c4 (0x00000000000000e2, 0xffff870826f58940, 0x000002a7d1cf0080, 0x0000000000000000). The pointer is recorded here: C:\WINDOWS\MEMORY.DMP. Reports Id: 45483b4c-9748-4039-83f5-004370f87ac2.

My windows is not english so i tried to translate this sorry for mistakes. This is original one:

Kompiuteris buvo perkrautas atlikus virusų tikrinimą. Virusų tikrinimas buvo: 0x000000c4 (0x00000000000000e2, 0xffff870826f58940, 0x000002a7d1cf0080, 0x0000000000000000). I?keltis įra?yta čia: C:\WINDOWS\MEMORY.DMP. Ataskaitos Id: 45483b4c-9748-4039-83f5-004370f87ac2.

So what should i do now? What kind of problem is this?

My OS is Windows 10.

Read other answers
RELEVANCY SCORE 81.6

Hello,

I have been having random crashes during all sorts of operations....watching a flash video,opening up a program,running a game or even at idle.
Weird thing is that the pc never crashed whilst running torture tests with prime95 and furmark.Prime 95 completed 12 hours in blend run, and as long as possible in large and small fft's before i had to stop it due to very high temps(system is usually overclocked-and the QX6700 isn't exactly cooling friendly at 130TDP).
The crashes however occur in both default clocked and overclocked...
System file checker(sfc scannow) completes with no problem
I attach the jcgriff2 and perfmon files for any help or ideas-The attachments were taken with the system in default clocks just to be sure.

Win7 x64 Ultimate
Seasonic X-series 760W
ABIT AW9d-MAX
Intel QX6700
8GB Ram OCZ Reaper
EVGA 460gtx
Asus Xonar D2X
RocketRaid 2640x4
7x Hard disks
Thank you,
Dimitris

A:Driver Verifier BSOD's

I attach an updated dmp file of a SSD error
as well as the link to a really large *.dmp file created with today's bsods(size was 559mb-zipped to 130).
http://uploading.com/files/e1d853d9/MEMORY.zip/

Read other 9 answers
RELEVANCY SCORE 81.2

Same error again... I was using Google Earth, and my external monitor went black (this happens when I'm out of RAM, but I have additional 4 GB paging file, and 16 GB physical RAM), I turned my laptop to sleep (usually I can fix this black screen problem by turning to sleep and back on) and back on, and it showed BSOD - SYSTEM_SERVICE_EXCEPTION:
ntoskrnl.exe+142760
0x0000003b
00000000`c0000005
fffff801`4003aa65
ffffd000`22d9bce0

DMP file - https://mega.nz/#!L88W0LDa!IQoTAfjpK...yswv_OOrNhyrUU

BTW I don't have those crash-causing NVIDIA drivers installed for 2 months now, all I have is Intel HD 4600 Graphics which I installed in non-traditional way (by using 'Have Disk'), because there is no other way, Toshiba doesn't provide drivers like these anymore, so I had to update using original Intel drivers (they are compatible with my processor and intel graphics version).

I just ran driver verifier, and here are 3 BSOD messages that showed up

SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDDRIVER_VERIFIER_FOUND_VIOLATION (TVALZ_O.SYS) - TOSHIBA driver which has showed up in BSOD's few months agoIRQL_NOT_LESS_OR_EQUAL

http://answers.microsoft.com/en-us/w...ge=3#LastReply

Read other answers
RELEVANCY SCORE 80.8

My first time doing all this (running Verifier, uploading dump data, etc.)

Any questions please just ask.

A:BSOD when starting up using Driver Verifier

Driver verifier is supposed to cause BSODs. Is there any reason that you enabled it? If your previous BSODs lead you to do it, disable DV.

Uninstall BitDefender. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know for any further BSOD, obviously without DV. If it is needed, you will be suggested for it at teh proper time.
________________________________

Code:
BugCheck C5, {ffffffff, 2, 0, fffff80002ff79cc}

*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

Read other 1 answers
RELEVANCY SCORE 80.8

I've been having a persistent BSOD in the past few weeks. I decided to run Driver Verifier a couple days ago to find out the problem. It just blue-screened and I zipped up the memory dump file below. Help?http://www.mediafire.com/?hn2azubn2tnn781System Info-----------OS Name Microsoft Windows 7 UltimateVersion 6.1.7601 Service Pack 1 Build 7601Other OS Description Not AvailableOS Manufacturer Microsoft CorporationSystem Manufacturer Gigabyte Technology Co., Ltd.System Model M68MT-S2System Type x64-based PCProcessor AMD FX™-4100 Quad-Core Processor, 3600 Mhz, 2 Core(s), 4 Logical Processor(s)BIOS Version/Date Award Software International, Inc. FCd, 20/02/2012SMBIOS Version 2.4Windows Directory C:\WindowsSystem Directory C:\Windows\system32Boot Device \Device\HarddiskVolume1Locale CanadaHardware Abstraction Layer Version = "6.1.7601.17514"User Name Uranium-PC\UraniumTime Zone Eastern Daylight TimeInstalled Physical Memory (RAM) 8.00 GBTotal Physical Memory 7.98 GBAvailable Physical Memory 6.33 GB

A:Persistent BSOD - Driver Verifier

Interesting: A VERIFIER_ENABLED crash with a system uptime of 52 hours!Probably caused by : t_mouse.syst_mouse.sys Thu Apr 16 23:45:37 2009t_mouse.sys ... iBall Advanced Mouse driver http://www.iball.co.in/Download.aspxIt seems the mouse being used is causing the problem: Remove it.========================BSOD BUGCHECK SUMMARY................................................................Loading Dump File [C:\CactusIsland\SoulSnatcher_BC\070412-30217-01.dmp]Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030Debug session time: Thu Jul 5 05:57:26.731 2012 (UTC + 10:00)System Uptime: 2 days 4:38:07.034Unable to load image \SystemRoot\system32\DRIVERS\t_mouse.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for t_mouse.sys*** ERROR: Module load completed but symbols could not be loaded for t_mouse.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : t_mouse.sys ( t_mouse+3310 )DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)The IO manager has caught a misbehaving driver.Arguments:Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a call to IoMarkIrpPending.Arg2: fffff880069c6310, The address in the driver's code where the error was detected.Arg3: fffff98048c3ecf0, IRP address.Arg4: 0000000000000103, Status code.BUGCHECK_STR: 0xc9_24cDRIVER_VERIFIER_IO_VIOLATION_TYPE: 24cDEFAULT_... Read more

Read other 1 answers
RELEVANCY SCORE 80.8

Hi,
 
I am having some issues with my GPU, mostly rare random crashes like when opening GPU-Z,
and with later Crimson i can crash in games as well, don't think it happens (if not super rarely?) on Catalyst.
 
Anyhow, i had Driver Verifier on as per instructions, and noticed when i woke up today that it had crashed during the night, the cause for atikmpag.sys.
 
So here are the dump files etc.
 
The only thing that was on during the night was Avisynth converting a file, and the settings use GPU which i guess might be the cause (not that it normally crashes, but for the verifier).
 

 
ConvertToYV12(matrix="Rec601", interlaced=false).Normalize(0.9)
fft3dgpu(sigma=1.3, plane=3)
smdegrain(tr=2,lsb=true,thsad=500,lsb_out=true,search=3)
Dither_convey_yuv4xxp16_on_yvxx()

 
Basically ff3dgpu used the GPU, but still not sure if that's the thing to blame, only had verifier on for like a day, but it's the only thing that was running during the night.
Hopefully the dumps will tell something more.

A:Driver Verifier - atikmpag BSOD

Hmm, looking at the event viewer i can see that Windows tried to update my GPU Driver right before the crash.
This is weird, i can't find anything in the update logs, the update never succeeded either, and i can't even find the update if i search now.
I don't have the latest driver for other reasons so i know there is other drivers, but i should have disabled it from updating, makes no sense.

Read other 0 answers
RELEVANCY SCORE 80.8

BSOD running driver verifier named Agrsm64.sys as the Bugcheck
This is the driver for My Agere Systems PCI-SV92E Soft Modem

Driver Provider: Agere Systems
Driver Date: 03/21/2008
Driver Version: 2.1.88.0
Driver: agrsm64.sys
File Version: 2.07

This modem has to be setup in safe mode to get it to work correctly. If I install it in normal windows I get a Code 52 unsigned driver error.
Also if I update the driver via device manager then the device has a code 52 error unsigned driver

A:BSOD while running driver verifier

A little off-topic, but that is a Dial-Up modem, and if you're using Cable/Broadband or if you don't use a phone line for fax that is connected to your computer , then you can safely disable that device and if you know you're way around, you can physically remove the card from the PC.

Read other 19 answers
RELEVANCY SCORE 80.8

Have randomly gotten BSOD several times after getting new computer. Reinstalled video and audio drivers, but still getting BSOD.

Installed a second HDD (New) and 8GB of additional RAM (New). Memory test and HDD test shows OK.

Did install old TV tuner card, which states 2006 driver is up to date.

All dump files attached, latest (102713-13026-01) was after running driver verifier.

Thanks for the help!

A:Random BSOD and after driver verifier

Hi,

Among the attached DMP files, we seem to be stuck on two consistent bug checks:

KMODE_EXCEPTION_NOT_HANDLED (1e)

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

The latest DMP file is still of the *1e bugcheck is and is failing to detect a device driver within violation.

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)

Probably caused by : hardware

Due to verifier failing to detect a device driver and having a *3d faulting hardware, this is more than likely a hardware issue.

How new is this computer? If it's BRAND new, such as several days to only a week, contact the manufacturer and let them know you are getting hardware related BSOD's and would like a replacement ASAP.

Regards,

Patrick

Read other 3 answers
RELEVANCY SCORE 80.8

Hi all,

This is my first post. Please excuse any failings therefore.

Recently, over the last three days, I have been experiencing random BSOD's, atleast once a day. I have not added any new hardware or any new software that I am aware of apart from Windows Updates. I an running Driver Verifier and it crashed on startup today morning. I believe all the crashes came quickly after startup.

Your help would be much appreciated. I looked at the dumps and they seem to indicate USB but I am not sure since the cause changes each time.

SF Diagnostics attached! Thanks

A:Windows 8 Pro x64 - BSOD with Driver Verifier

Hi,

Slightly confused, which O/S do you have installed as you have Win 7 Ultimate in specs and Win 8 Pro in title?

Looking at your MSinfo file you need to post this in Windows 8 forums

Windows 8 Forums

Cheers

Dave

Read other 3 answers
RELEVANCY SCORE 80.8

BSOD running driver verifier named Agrsm64.sys as the Bugcheck
This is the driver for My Agere Systems PCI-SV92E Soft Modem

Driver Provider: Agere Systems
Driver Date: 03/21/2008
Driver Version: 2.1.88.0
Driver: agrsm64.sys
File Version: 2.07

This modem has to be setup in safe mode to get it to work correctly. If I install it in normal windows I get a Code 52 unsigned driver error.
Also if I update the driver via device manager then the device has a code 52 error unsigned driver

A:BSOD while running driver verifier

A little off-topic, but that is a Dial-Up modem, and if you're using Cable/Broadband or if you don't use a phone line for fax that is connected to your computer , then you can safely disable that device and if you know you're way around, you can physically remove the card from the PC.

Read other 19 answers
RELEVANCY SCORE 80.8

BSOD running driver verifier named Agrsm64.sys as the Bugcheck
This is the driver for My Agere Systems PCI-SV92E Soft Modem

Driver Provider: Agere Systems
Driver Date: 03/21/2008
Driver Version: 2.1.88.0
Driver: agrsm64.sys
File Version: 2.07

This modem has to be setup in safe mode to get it to work correctly. If I install it in normal windows I get a Code 52 unsigned driver error.
Also if I update the driver via device manager then the device has a code 52 error unsigned driver

A:BSOD while running driver verifier

A little off-topic, but that is a Dial-Up modem, and if you're using Cable/Broadband or if you don't use a phone line for fax that is connected to your computer , then you can safely disable that device and if you know you're way around, you can physically remove the card from the PC.

Read other 2 answers
RELEVANCY SCORE 80.8

I have another post where people are helping me with BSODs on my gaming pc whenever I play games and they suggested I run driver verifier and send them the two more bsod minidump files. My question is once I enable driver verifier how long should I wait to disable it? If I don't get a bsod within the first 1 hour of it running should I turn it off and assume my drivers are not the problem since when playing games I always get the bsod within the first 15 minutes.

One more questions, they recommend that I turn off auto restart when I get a bsod, but if I do get a bsod with auto restart disabled how would I boot up again during a bsod? would I just press and hold the power button on the pc?

here's the link to my other thread in case you want to look at it.
How do I read/analyze this dump file so I know what is causing the BSO - Windows 10 Forums

thanks!!

Read other answers
RELEVANCY SCORE 80.8

Hi, so since my computer was randomly freezing up for no apparent reason, I did some research and enabled driver verifier which then led me to a BSOD instead of just freezing (which I believe is the effect I want to achieve). In any case, I got a dump file and I have no idea how to analyze it. Attached is the complete SF-Diagnostic archive. Any help is appreciated.

A:BSOD after enabling driver verifier

Hi.

Please disable verifier as it has not provided any information to us.

Remove:

Code:
Start Menu\Programs\Norton Internet Security Public:Start Menu\Programs\Norton Internet Security Public
Start Menu\Programs\Sandboxie Public:Start Menu\Programs\Sandboxie Public
Norton Internet Security & Sandboxie for testing purpose. You can put it back after troubleshooting is done.

Then please follow the steps below:




Quote:
Based on the bugchecks, I would recommend you follow and complete the steps given below:1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity ... Read more

Read other 1 answers
RELEVANCY SCORE 80.8

Hello

I decided to use driver verifier after having trouble with regular BSOD concerning: MemoryManagement, DriverIRQLNotEqual and others. Now I keep having BSOD (Driver_Verifier_detected_violation) as I boot my laptop up. I don't even have time to login.

OS:Windows8.1.

What to do?

A:BSOD Loop after using driver verifier

Reboot into Safe Mode and disable it from there: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

Once in Safe Mode, run verifier.exe and select "Delete existing settings" and click on "Finish". Then reboot into normal mode and it should work w/o problems.

Read other 7 answers
RELEVANCY SCORE 80.8

My laptop is ASUS x42j series and has been used for more than 2 years. It did ran just fine up until 2 days ago when it started freezing with color dots and patterns on the screen. I did a Regcure Pro scan and fix most of the errors as well as trying the driver verifier run to detect the failure. can somebody help me decode this problem?

A:bsod after running driver verifier.

Ok had a look at your files and a few things come to mind, first there are no crash dumps so I can not definitely pin down the problem only give my best suggestions fix this please follow this tutorial:

Dump Files - Configure Windows to Create on BSOD

Now onto the things of note:

Please uninstall Daemon tools it is known to cause BSODs, once it is uninstalled download and run this tool:

DuplexSecure - Downloads

whjen the tool runs if the uninstall button is grayed out just close the window, if it is not click it and let the tool run. DO NOT click the install button it will install a driver known to cause BSODs.

Next please uninstall Tuneup Utilities, these programs are very unnecessary and can do more harm than good, they know less about your computer than you do and if your using it to "clean" your registry its probably doing harm.

Please uninstall the Asus utilities on your computer they are nothing but bloatware


Code:
Start Menu\Programs\ASUS Utility\ASUS Live Update Utility\ASUS Live Update
Start Menu\Programs\ASUS Utility\ASUS Splendid Utility
Start Menu\Programs\ASUS Utility\SmartLogon
Start Menu\Programs\ASUS\ASUS AP Bank
Start Menu\Programs\ASUS\ASUS WebStorage
Last please update the following drivers

JMicron PCI Express Gigabit Ethernet Adapter found Here

and Realtek High Definition Audio found Here

Read other 1 answers
RELEVANCY SCORE 80.8

I was playing battlefield 3 and got a BSOD today

031212-38688-01.dmp
3/12/2012 4:01:44 PM
MEMORY_MANAGEMENT
0x0000001a
00000000`00041284
00000000`01787001
00000000`00000920
ffff700`01080000
ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft? Windows? Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\031212-38688-01.dmp 8 15 7601 292,264

that is copy-pasted out of Blue Screen Viewer. I recently ran Driver Verifier last night and it gave me a bluescreen for "Applecharger.sys" which i disabled in Auto run to fix that problem. But the blue screen posted above was for ntoskrnl.exe. I forgot to turn my driver verifier off so im thinking maybe that is the cause of the BSOD. Does anyone else think that was the problem or is there something else corrupt on my system. (im not very good with computers at all, sorry if I spoke wrong about some technical aspects of my problem). THANK you!\

I did a SFC /SCANNOW and a CHKDSK /r and both showed up with no errors after the BSOD happened to me.

A:If driver verifier is left on will it cause a BSOD?

Driver verifier is Supposed to make it crash if it find a misbehaving driver. It doesn't always

we still need the dmp

Read other 5 answers
RELEVANCY SCORE 80.8

I've been getting BSOD's randomly so I tried driver verifier to find the source of it. I got a bsod on startup and disabled it through safemode. I have a dump file.
Can someone help me with whats causing it? Please tell me if you need additional information.

Specs:
i5 4590
MSI PC Mate
R9 280X
Asus Xonar DGX
Panda Wireless Adapter
Toshiba Q SSD
Seagate HDD

Edit (3/25/15) : I have done as blueevis had recommended and removed daemon tools. Unfortunately I am still getting BSOD's. I would be grateful for any help.

A:BSOD with driver verifier. Can someone decipher this?

Hi ddkotan & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes -

Code:
**************************Sat Mar 21 11:52:25.341 2015 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\032015-6562-01.dmp]

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 8 Kernel Version 9600 MP (4 procs) Free x64

System Uptime: 0 days 0:00:10.076

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Probably caused by : ntoskrnl.exe ( nt+695934 )

BugCheck C9, {21f, fffff801e5d19934, ffffcf82023c6dc0, 0}
BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)

Arguments:
Arg1: 000000000000021f, A driver has not filled out a dispatch routine for a required IRP major function.
Arg2: fffff801e5d19934, The address in the driver's code where the error was detected.
Arg3: ffffcf82023c6dc0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR: 0xc9_21f

FAILURE_BUCKET_ID: WRONG_SYMBOLS

CPUID: "Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz"

MaxSpeed: 3300

CurrentSpeed: 3300

BIOS Version V4.6

BIOS Release Date 11/07/2014

Manufacturer MSI

Product Name MS-7850

Baseboard Product Z9... Read more

Read other 4 answers
RELEVANCY SCORE 80.8

Hi all,

This is my first post. Please excuse any failings therefore.

Recently, over the last three days, I have been experiencing random BSOD's, atleast once a day. I have not added any new hardware or any new software that I am aware of apart from Windows Updates. I an running Driver Verifier and it crashed on startup today morning. I believe all the crashes came quickly after startup.

Your help would be much appreciated. I looked at the dumps and they seem to indicate USB but I am not sure since the cause changes each time.

SF Diagnostics attached! Thanks

A:Windows 8 Pro x64 - BSOD with Driver Verifier

Any help?

Thanks

Read other 3 answers
RELEVANCY SCORE 80.8

First off, thank you so much for having this kind of information and help out there, I'm hoping to learn more about Windows and at some point begin to diagnose and troubleshoot my own problems. Second, I have been having BSOD's more frequently in the past 3 to 4 weeks and it got to the point that I completely wiped my drive (a Crucial 128GB RealSSD C300) and installed a fresh copy of Windows 7 Pro. Now after the wipe, I am not experiencing BSOD's quite as frequent however whenever my computer is in sleep for a few hours, I'll come back to wake it up only to have it report is was shutdown improperly. After digging around and reading a bit I decided I would run the driver verifier to see if anything would come up. It has been a day since I started it but I finally had a BSOD during an update to a program (the EA Origin service). Any insight into this problem is greatly appreciated!

A:[SOLVED] Driver Verifier BSOD

Hi -

The lone dump was VERIFIER_ENABLED, but did not name a 3rd party driver. This means the likely cause is hardware failure.

Did you have BSODs before the Crucial 128GB RealSSD C300 was installed?

Regards. . .

jcgriff2

`


Code:

Opened log file 'C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\_99-dbug.txt'

Microsoft (R) Windows Debugger Version 6.2.8102.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-17269-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*a:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0341b000 PsLoadedModuleList = 0xfffff800`03660670
Debug session time: Wed Feb 8 22:11:23.819 2012 (UTC - 5:00)
System Uptime: 0 days 5:22:27.989
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..................
TRIAGER: Could not open triage file : K:\WinDDK\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : K:\WinDD... Read more

Read other 6 answers
RELEVANCY SCORE 80.4

Hi all.

My computer has always had intermittent BSOD but generally it's been only 1-2 a month and after a system restart everything works fine. In the last couple of weeks I've been getting BSOD after only a few minutes of operation every time I start up and generally after these errors the computer won't boot - sometimes it will be a black screen after BIOS check, sometimes it won't even get that far - just black screen without the BIOS check even starting. Usually the only way to get it to boot again is to disconnect the power and remove the CMOS battery from the motherboard. I've run driver verifier which has indeed generated it's own minidumps but I don't really understand what these error reports are trying to tell me - if someone could take a look and point me in the right direction it would be much appreciated.

thanks.

A:Driver related BSOD - minidumps by driver verifier

Your BIOS dates from 2010. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

Only 128 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

This device has problems in Device Manager:





Teredo Tunneling Pseudo-Interface ROOT\*TEREDO\0000 This device cannot start.



Please right click on it and select "Uninstall", then reboot and check to see if the error goes away. If not, post back to let us know.

Many, many Live Kernel Events in the WER section of MSINFO32.
Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog))
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

While waiting for a reply, please monito... Read more

Read other 1 answers
RELEVANCY SCORE 80

I've been having problems with mostly memory and driver related issues, crashing frequently in both games that require lots of resources and games that shouldn't require much at all. I enabled Driver Verifier to see if I could discern what the problem was, but now it crashes on startup. Not sure how this thing will work but there's plenty of crashes in the zip, I assume. I'll do my best to provide additional information if needed.

I should also note that I would more appreciate help figuring out what the problem is. The most recent couple would be after driver verifier was enabled. I know I could simply turn off the verifier and run my computer as usual, but I thought this would help me fix the greater problem.

Read other answers
RELEVANCY SCORE 80

Hey guys,

So this is my second distinct BSOD in the last while. I turned on driver verifier to investigate the first BSOD problem because minidump files arent being created even after turning on small memory dumps (kernel dumps dont show up either). So this new BSOD appears immediately when the starting windows screen appears.

Ive attached the ntbtlog.txt file which was created through the enable boot logging option.

Any info would be awesome, Thanks a lot

A:Driver Verifier BSOD - NO dmp files are being created

Welcome
Its difficult to diagnose a BSOD without the reports, but lets try.
Uninstall your Anti Virus and replace with
Microsoft Security Essentials - Free Antivirus for Windows
Set up a clean boot. Do not restore any items until, you are instructed to do so.
Troubleshoot Application Conflicts by Performing a Clean Startup
Make a full Anti Virus scan.
: Download Malwarebytes Anti-Malware 1.62 - FileHippo.com (Full Scan)
Make sure that you are configured correctly.
Dump Files - Configure Windows to Create on BSOD
Submit any new BSODs after you make these changes.

Read other 9 answers
RELEVANCY SCORE 80

I've struggled to get to this point, but I think I narrowed it down.

The BSOD is intermittent, it happens 4 or 5 times a month. It's been happening for about a year. Usually I just restart the PC and move on with my life, but I finally got sick of it and here I am. I couldn't be certain when the change happened, because I put all my parts into this PC at the same exact time. So I couldn't narrow it down by saying, ''Well the BSOD happened when I put this part in! Ah ha!''

I had it down to two things, either hardware failure or drivers. I spent hours using memtest86+ to narrow out the ram, then a few more hours scanning the hdd for errors, then a few more hunting down and upgrading every single driver and making sure it was all up to date. Cleaning installing half a dozen times to try different things. It's been a really long few days, but I think I figured it out as best I could. I ran Driver Verifier early on and it crashed my PC with a BSOD QUICK. So I was pretty confident it was a driver issue. But I wanted to narrow down hardware just in case so if anyone asked, I could honestly say I had tested everything.

Can someone take a few minutes and look at these .dmp files for me and let me know what course of action I can take to fix this for good? You don't even know how grateful I would be for just a tiny bit of help to get this over with, I might cry with relief lol. Kidding about the crying, but I would be immensely grateful for a few minutes of someone's time to hel... Read more

A:Driver Verifier found the cause of the BSOD, please help with the solution?

Hi. . .

Both dumps were indeed VERIFIER_ENABLED, however neither named a 3rd party driver, which means the cause of both is unknown hardware failure.

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

All I can really do here is to give you some hardware diagnostic programs to run.RAM - memtest86+ - run 1 stick at a time; alternate the slots - https://www.sysnative.com/forums/har...memtest86.html
HDD - SeaTools for DOS, LONG test - https://www.sysnative.com/forums/har...agnostics.html
FurMark video card test - https://www.sysnative.com/forums/har...ress-test.html
Prime95 CPU - https://www.sysnative.com/forums/har...s-testing.html

The problem may also be with other hardware parts such as the motherboard or PSU for which there are no software tests.

If you are encountering a specific hardware issue, feel free to post in our Hardware Forum - Motherboards, Bios & CPU

Regards. . .

jcgriff2

`

Read other 1 answers
RELEVANCY SCORE 80

I've struggled to get to this point, but I think I narrowed it down.

The BSOD is intermittent, it happens 4 or 5 times a month. It's been happening for about a year. Usually I just restart the PC and move on with my life, but I finally got sick of it and here I am. I couldn't be certain when the change happened, because I put all my parts into this PC at the same exact time. So I couldn't narrow it down by saying, ''Well the BSOD happened when I put this part in! Ah ha!''

I had it down to two things, either hardware failure or drivers. I spent hours using memtest86+ to narrow out the ram, then a few more hours scanning the hdd for errors, then a few more hunting down and upgrading every single driver and making sure it was all up to date. Cleaning installing half a dozen times to try different things. It's been a really long few days, but I think I figured it out as best I could. I ran Driver Verifier early on and it crashed my PC with a BSOD QUICK. So I was pretty confident it was a driver issue. But I wanted to narrow down hardware just in case so if anyone asked, I could honestly say I had tested everything.

Can someone take a few minutes and look at these .dmp files for me and let me know what course of action I can take to fix this for good? You don't even know how grateful I would be for just a tiny bit of help to get this over with, I might cry with relief lol. Kidding about the crying, but I would be immensely grateful for a few minutes of someone's time to hel... Read more

Read other answers
RELEVANCY SCORE 80

Hey guys, first post here, sooo i've been getting random bsod's and i know its a driver so i used the verifier which caught something but i dont know what.

Help!

Which driver is causing this madness!

Thanks in advance

Windows 7 . . .
- x64
- the original installed OS on the system is supposed to be vista
- full retail
- 2 years old ish.
- fresh installation, 2 days old on intel ssd

hp tx2
amd turion x2 zm-80
intel 160gb g2 ssd w/ latest firmware
ati radeon hd 3200

A:BSOD w/ driver verifier....now what? all files included

  
Quote: Originally Posted by xxdunnxx


Hey guys, first post here, sooo i've been getting random bsod's and i know its a driver so i used the verifier which caught something but i dont know what.

Help!

Which driver is causing this madness!

Thanks in advance

Windows 7 . . .
- x64
- the original installed OS on the system is supposed to be vista
- full retail
- 2 years old ish.
- fresh installation, 2 days old on intel ssd

hp tx2
amd turion x2 zm-80
intel 160gb g2 ssd w/ latest firmware
ati radeon hd 3200



Driver verified and Related to AODDriver2.sys AMD OverDrive Service Driver from Advanced Micro Devices

I would remove it at least to test. I would not overclock.

Read other 3 answers
RELEVANCY SCORE 80

Good evening all.

Since a couple of days I'm getting BSOD's once a day with the notice that my Driver Verifier has detected a violation. These particular BSOD's occured in pretty much every activity so far, from playing a game to watching a video or just browsing through some forums. I've also noticed that my notebooks fans get louder since the BSOD appeared, but I can't imagine that there's too much dust inside because I've just bought this notebook a few weeks ago and haven't used it that much.

If you need any more information just ask and it would be much appreciated, if you could help me out with this issues. Many thanks in advance and here's my file:

Attachment 54713

EDIT: I've installed Speedfan and MSI Afterburner lately, but Speedfan only to see the temps and MSI AB only to record games, nothing else. I'm mentioning this just in case these programs could cause troubles.

EDIT2: I've just re-installed Speedfan, and just as I wanted to open it because my fans were louder than usual once again the BSOD I mentioned above appeared again. Could it be that Speedfan was causing those issues? I've uninstalled it and now my notebook is suddenly not as noisy anymore either, but I'll check if it remains like this for a longer period.

A:BSOD - Driver Verifier Violation Detected

Update: My notebook is louder than usual again, but I haven't experienced another BSOD yet. Will keep you updated.

Update #2: No BSOD's today, seems like it was Speedfan causing the troubles. Still, could one of you guys check my file to see if there is/was anything else possibly causing problems?

Read other 1 answers
RELEVANCY SCORE 80

Put on driver verifier on unsigned drivers a few weeks ago. It has crashed before due to driver verifier, but this is the first time anything has appeared in the minidump.

A:Driver verifier BSOD, usbport.sys in bluescreenview

Yes Driver Verifier has found the driver(s) responsible.

I always recommend that before you go changing drivers that creating a system restore point is a good option, please follow these instructions on how to create one.

System Restore Point - Create

It indicates that your Bigfoot Networks Killer Xeno PCI-E Gaming Adapter Driver is causing issues. Can you please update it here.

Drivers | VisionTek - High-Performance PC and Mac Upgrades and Enhancements


Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {7, fffff88004ee3320, fffff98010e1cee0, 0}

Unable to load image Xeno7x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Xeno7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
Probably caused by : Xeno7x64.sys ( Xeno7x64+b320 )

Code:
fffff880`04ed8000 fffff880`04f01000 Xeno7x64 T (no symbols)
Loaded symbol image file: Xeno7x64.sys
Image path: Xeno7x64.sys
Image name: Xeno7x64.sys
Timestamp: Wed May 18 23:55:16 2011 (4DD44E54)
CheckSum: 000... Read more

Read other 3 answers