Windows Support Forum

[SOLVED] BSOD hardware fault, driver verifier run

Q: [SOLVED] BSOD hardware fault, driver verifier run

I have an HP 8100 elite that keeps bsod. i ran the driver verifier and attached are the zipped results.

How to I read the log files?

http://www.techsupportforum.com/forums/f299/solved-bsod-hardware-fault-driver-verifier-run-588143.html
Relevancy 100%
Preferred Solution: [SOLVED] BSOD hardware fault, driver verifier run

I recommend downloading and running Reimage. It's a computer repair tool that has been proven to identify and fix many Windows problems with a high level of success.

I've used it in the past to identify and fix everything from blue screens (BSOD's), ActiveX errors, corrupt files and processes, dll/exe/sys errors, recover lost memory, Windows update problems, defragging, malware removal etc.

You can download it direct from this link http://downloadreimage.com/directdownload.php. (This link will automatically start a download of Reimage that you can save to your computer.)

Relevancy 82.99%

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 to weeks and it got to the point that I completely [SOLVED] Driver Verifier BSOD wiped my drive a Crucial GB RealSSD C and installed a fresh copy of Windows 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 [SOLVED] Driver Verifier BSOD 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:\WinDDK\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e3, fffffa800e832531, 649eb08, 0}

TRIAGER: Could not open triage file : K:\WinDDK\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

Followup: MachineOwner
---------

2: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
Arg2: fffffa800e832531, Address inside the driver making the incorrect API call.
Arg3: 000000000649eb08, User-mode address used as API parameter.
Arg4: 0000000000000000

Debugging Details:
------------------

TRIAGER: Could not open triage file : K:\WinDDK\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR: 0xc4_e3

FAULTING_IP:
+0
fffffa80`0e832531 85c0 test eax,eax

FOLLOWUP_IP:
nt!VerifierBugCheckIfAppropriate+3c
fffff800`039213dc cc int 3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: ekrn.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER:... Read more

http://www.techsupportforum.com/forums/f299/solved-driver-verifier-bsod-629326.html
Relevancy 78.69%

removed daemonTools and installed newest ATI driver. Anything else problematic?

? Windows 7
? x64
? Original OS was win7 x64 (from fresh install)
? full retail
? Age of system: 6 months? Self built.
? Reinstalled 2 months ago

? CPU: Intil core 17 2600k
? Video Card: amd radeon hd 6800 series (driver: 8.871.0.0)
? MotherBoard: asrock p67 extreme6
? Power Supply - brand & wattage: CORSAIR Enthusiast Series CMPSU-650TX 650W

? System Manufacturer: self-built
? Exact model number: n/a

How do you guys know how to read these? There's no primer/howto guide for what to look for out there is there? Just takes experience?

Thank you VERY MUCH for being so kind to go over stuff like this!

A:[SOLVED] mouse crawled to snail's-pace and unresponsive, bsod with driver verifier

Hi -

Find an update for your Logitech Mouse -

Code:
LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
http://www.sysnative.com/drivers/table/#LGVirHid.sys

Regards. . .

jcgriff2


`




BSOD SUMMARY

Code:
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\092711-18220-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Sep 27 11:42:05.794 2011 (GMT-4)
System Uptime: 0 days 0:03:02.637
*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR: 0xc9_220
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xc9_220_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`00000220 fffff880`050ff710 fffff980`7315edc0 fffffa80`1051cb80
BiosVersion = P1.70
BiosReleaseDate = 06/22/2011
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed: 3400
CurrentSpeed: 3392
??????????????????????????????????????????????????????????????????????????????????????``

http://www.techsupportforum.com/forums/f299/solved-mouse-crawled-to-snails-pace-and-unresponsive-bsod-with-driver-verifier-603131.html
Relevancy 78.69%

New Win Pro notebook causes BSOD First WinDBG result DRIVER POWER STATE FAILURE F module was pci sys Then I ran driver verifier and it died with C and the module was vsdatant sys Analyze log Code kd gt analyze -v r kv lmnt lmtsmn Bugcheck Analysis DRIVER VERIFIER DETECTED VIOLATION c A device driver attempting to corrupt the system has been caught This is because the driver was specified in the registry as being suspect by the administrator and the kernel has enabled substantial checking of this driver If the driver attempts to corrupt the 0x9F attached - BSOD - and Minidump [SOLVED] 0xC4, Driver Verifier sysinfo system bugchecks xC xC and xA will be among the most commonly seen crashes Arguments Arg Waiting at DISPATCH LEVEL without a timeout Arg IRQL value Arg fffff dc b Object to wait on Arg Timeout parameter Debugging Details ------------------ BUGCHECK STR xc CUSTOMER CRASH COUNT DEFAULT BUCKET ID VERIFIER ENABLED VISTA MINIDUMP PROCESS NAME System CURRENT IRQL LAST CONTROL TRANSFER from fffff f dc to fffff a ef STACK TEXT fffff a d fffff f dc c fffff dc b nt KeBugCheckEx fffff a e fffff f b fffff fffff e nt VerifierBugCheckIfAppropriate x c fffff a fffff d f fffff dc b fffff dc fffff da c e nt VerifierKeWaitForSingleObject x fffff a a fffff dc b fffff dc fffff da c e [SOLVED] BSOD 0x9F - Driver Verifier - 0xC4, Minidump and sysinfo attached vsdatant x f fffff a a fffff dc fffff da c e fffffa e c vsdatant x b STACK COMMAND kb FOLLOWUP IP vsdatant f fffff d f SYMBOL STACK INDEX SYMBOL NAME vsdatant f FOLLOWUP NAME MachineOwner MODULE NAME vsdatant IMAGE NAME vsdatant sys DEBUG FLR IMAGE TIMESTAMP b cb FAILURE BUCKET ID X xc VRF vsdatant f BUCKET ID X xc VRF vsdatant f Followup MachineOwner --------- rax rbx c rcx c rdx rsi rdi rip fffff a ef rsp fffff a d rbp r r fffff dc b r fffff f cac r d r r fffffa bae r fffff db f r fffff iopl nv up ei pl zr na po nc cs ss ds b es b fs gs b efl nt KeBugCheckEx fffff a ef c mov qword ptr rsp rcx ss fffff a e c Child-SP RetAddr Args to Child Call Site fffff a d fffff f dc c fffff dc b nt KeBugCheckEx fffff a e fffff f b fffff fffff e nt VerifierBugCheckIfAppropriate x c fffff a fffff d f fffff dc b fffff dc fffff da c e nt VerifierKeWaitForSingleObject x fffff a a fffff dc b fffff dc fffff da c e vsdatant x f fffff a a fffff dc fffff da c e fffffa e c vsdatant x b start end module name fffff bbd fffff bc kdcom kdcom dll Tue Jul A BDFDB fffff a d fffff fea nt ntkrnlmp exe Tue Jul A BC fffff fea fffff hal hal dll Tue Jul A BDF fffff c fffff c c volmgrx volmgrx sys Tue Jul A BC fffff c c fffff c c PCIIDEX PCIIDEX SYS Tue Jul A BC fffff c c fffff c amdxata amdxata sys Tue May A F EB fffff c fffff cc mcupdate GenuineIntel mcupdate GenuineIntel dll Tue Jul A BDF fffff cc fffff cdc PSHED PSHED dll Tue Jul A BE fffff cdc fffff d a CLFS CLFS SYS Tue Jul A BC D fffff d a fffff dfa CI CI dll Tue Jul A BE D fffff e fffff e atapi atapi sys Tue Jul A BC fffff e fffff e ataport ataport SYS Tue Jul A BC fffff e fffff e e msahci msahci sys Tue Jul A BCABD fffff e fffff eec Wdf Wdf sys Tue Jul A BC F fffff eec fffff efb WDFLDR WDFLDR SYS Tue Jul A BC A fffff efb fffff f ACPI ACPI sys Tue Jul A BC fffff f fffff f b WMILIB WMILIB SYS Tue Jul A BC fffff f b fffff f msisadrv msisadrv sys Tue Jul A BC FE fffff f fffff f pci pci sys Tue Jul A BC fffff f fffff fa vdrvroot vdrvroot sys Tue Jul A BCADB fffff fa fffff fba partmgr partmgr sys Tue Jul A BC E fffff fba fffff fc compbatt compbatt sys Tue Jul A BC B fffff fc fffff fcf BATTC BATTC SYS Tue Jul A BC B fffff fcf fffff fe volmgr volmgr sys Tue Jul A BC D fffff fe fffff ffe mountmgr mountmgr sys Tue Jul A BC A fffff fffff c volsnap volsnap sys Tue Jul A BC fffff c fffff rdyboost rdyboost sys Tue Jul A BC A fffff b fffff fc fltmgr fltmgr sys Tue Jul A BC F fffff fc fffff fileinfo fileinfo sys Tue Jul A BC fffff fffff e msrpc msrpc sys Tue Jul A BC C fffff e fffff e cng cng sys Tue Jul A BC fffff fffff pcw pcw sys Tue Jul A BC FF fffff fffff b Fs Rec Fs Rec sy... Read more

A:[SOLVED] BSOD 0x9F - Driver Verifier - 0xC4, Minidump and sysinfo attached

Step 1 - turn off Driver Verifier (it's purpose is to cause your system to crash).

Step 2 - remove Zone Alarm from your system. If you must have 3rd party firewall control, I suggest this free program: http://www.sphinx-soft.com/Vista/

http://www.techsupportforum.com/forums/f299/solved-bsod-0x9f-driver-verifier-0xc4-minidump-and-sysinfo-attached-468478.html
Relevancy 76.54%

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

http://www.sevenforums.com/bsod-help-support/359623-multiple-bsod-driver-verifier-driver-caught-driver-corrupting.html
Relevancy 74.39%

Same error again I was using Google Earth and my external monitor went black this happens when I'm out of RAM driver BSOD running causes TOSHIBA after Verifier Driver (L50-A-19N) [TVALZ_O.SYS] but I have additional GB paging file and GB physical RAM I TOSHIBA driver [TVALZ_O.SYS] causes BSOD after running Driver Verifier (L50-A-19N) 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 x b c fffff aa ffffd d bce DMP file - https mega nz L W LDa IQoTAfjpK yswv OOrNhyrUU BTW I don't have those crash-causing NVIDIA drivers installed for months now all I have is Intel HD 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 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 TOSHIBA driver [TVALZ_O.SYS] causes BSOD after running Driver Verifier (L50-A-19N) w ge LastReply

https://forum.toshiba.eu/showthread.php?91363-TOSHIBA-driver-TVALZ_O-SYS-causes-BSOD-after-running-Driver-Verifier-(L50-A-19N)
Relevancy 73.96%

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 monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Out of 7 memory dumps there were 5 different BSOD error codes (and the Driver Verifier dumps are suggestive of hardware problems also). The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers) - and older systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Please run these free hardware diagnostics: Hardware Diagnostics

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.





NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.





Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.



Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

... Read more

http://www.eightforums.com/bsod-crashes-debugging/46815-driver-related-bsod-minidumps-driver-verifier.html
Relevancy 73.53%

I recently had to re-install windows in order to correct an error I was getting for League of Legends, but after stepping away from the computer for a few minutes, I came back to the computer in the middle of it restarting after a crash. Surely enough, there was also a minidump in the folder, so I'm hoping someone can help me make sense of this.

View attachment Minidump.zip
Included in the zip folder is the CBS log I got after running sfc.exe to check for corrupt files, which came back with a 'yes, but cannot repair'.
 

https://forums.techguy.org/threads/solved-bsod-win8-driver-fault.1153530/
Relevancy 73.1%

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
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {89722f84, 0, 84969ab4, 0}

Unable to load image \SystemRoot\system32\drivers\ATKDispLowFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ATKDispLowFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for ATKDispLowFilter.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : ATKDispLowFilter.sys ( ATKDispLowFilter+ab4 )

Followup: MachineOwner
---------

1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
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: 89722f84, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: 84969ab4, if non-zero, the address which referenced memory.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82547874
Unable to read MiSystemVaType memory at 82527420
89722f84

FAULTING_IP:
ATKDispLowFilter+ab4
84969ab4 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xD5

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: 859db4c4 -- (.trap 0xffffffff859db4c4)
ErrCode = 00000000
eax=00000000 ebx=898570f4 ecx=899cf400 edx=0001000e esi=89722f48 edi=898570e8
eip=84969ab4 esp=859db538 ebp=8... Read more

http://www.techsupportforum.com/forums/f299/bsod-driver-verifier-694472.html
Relevancy 73.1%

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
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff980063cce40, 0, fffff88003e5a1aa, 0}

Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys

Could not read faulting driver name
Probably caused by : usbfilter.sys ( usbfilter+41aa )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
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: fffff980063cce40, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88003e5a1aa, 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 fffff800030fe0e0
fffff980063cce40

FAULTING_IP:
usbfilter+41aa
fffff880`03e5a1aa 8b4230 mov eax,dword ptr [rdx+30h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xD5

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff88002f62280 -- (.trap 0xfffff88002f62280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000... Read more

http://www.sevenforums.com/bsod-help-support/123254-driver-verifier-bsod.html
Relevancy 73.1%

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-vista/
 

http://www.bleepingcomputer.com/forums/t/618672/driver-verifier-bsod/
Relevancy 73.1%

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

http://www.sevenforums.com/bsod-help-support/115840-bsod-driver-verifier.html
Relevancy 73.1%

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.exe
Bugcheck code 000000C4
Arguments 00000000`000000e3 fffffa80`05e7bb51 00000000`049ef3b4 00000000`00000000
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Oct 19 10:11:29.296 2010 (GMT-4)
System Uptime: 0 days 2:48:17.718
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+b0 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iw3mp.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02db0800 fffff880`0859cf70 00000000`00000000
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Oct 19 07:18:35.196 2010 (GMT-4)
System Uptime: 0 days 0:01:36.649
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`058e5b51 00000000`049ef3b4 00000000`00000000
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Tue Oct 19 01:11:06.089 2010 (GMT-4)
System Uptime: 0 days 0:01:26.542
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`058d5b51 00000000`048af3b4 00000000`00000000
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Mon Oct 18 21:28:42.791 2010 (GMT-4)
System Uptime: 0 days 2:57:02.213
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: System
Bugcheck code 000000BE
Arguments fffff880`03f678c0 07000001`1a806101 fffff880`02f8b980 00000000`0000000a
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Debug session time: Sun Oct 17 07:59:49.393 2010 (GMT-4)
System Uptime: 0 days 0:58:47.893
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROC... Read more

http://www.techsupportforum.com/forums/f299/driver-verifier-bsod-s-522788.html
Relevancy 73.1%

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 registers.
Some register values may be zeroed or incorrect.
rax=fffff980014ab000 rbx=0000000000000000 rcx=fffff88003ff60fb
rdx=0000000000000046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003ff6192 rsp=fffff880033c3c80 rbp=0000000000000010
r8=0000000000000000 r9=fffff880033c4210 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
ATITool64+0x6192:
fffff880`03ff6192 66833800 cmp word ptr [rax],0 ds:fffff980`014ab000=????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e289fc to fffff80002e7cc40

STACK_TEXT:
fffff880`033c3988 fffff800`02e289fc : 00000000`00000050 fffff980`014ab000 00000000`00000000 fffff880`033c3af0 : nt!KeBugCheckEx
fffff880`033c3990 fffff800`02e7ad6e : 00000000`00000000 fffff980`014ab000 00000000`00000000 fffff980`014aaff0 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`033c3af0 fffff880`03ff6192 : 00000001`0000000b 00000170`00000000 ffff0001`0000000b 00000170`0000000d : nt!KiPageFault+0x16e
fffff880`033c3c80 00000001`0000000b : 00000170`00000000 ffff0001`0000000b 00000170`0000000d fffff880`033c5000 : ATITool64+0x6192
fffff880`033c3c88 00000170`00000000 : ffff0001`0000000b 00000170`0000000d fffff880`033c5000 fffff880`033bf000 : 0x1`0000000b
fffff880`033c3c90 ffff0001`0000000b : 00000170`0000000d fffff880`033c5000 fffff880`033bf000 00000007`00000010 : 0x170`00000000
fffff880`033c3c98 00000170`0000000d : fffff880`033c5000 fffff880`033bf000 00000007`00000010 ffffffff`00000000 : 0xffff0001`0000000b
fffff880`033c3ca0 fffff880`033c5000 : fffff880`033bf000 00000007`00000010 ffffffff`00000000 00000000`00000000 : 0x170`0000000d
fffff880`033c3ca8 fffff880`033bf000 : 00000007`00000010 ffffffff`00000000 00000000`00000000 fffff880`033c4210 : 0xfffff880`033c5000
fffff880`033c3cb0 00000007`00000010 : ffffffff`00000000 00000000`00000000 fffff880`033c4210 fffff880`00000001 : 0xfffff880`033bf000
fffff880`033c3cb8 ffffffff`00000000 : 00000000`00000000 fffff880`033c4210 fffff880`00000001 fffff800`030a6300 : 0x7`00000010
fffff880`033c3cc0 00000000`00000000 : fffff880`033c4210 fffff880`00000001 fffff800`030a6300 00000000`00000000 : 0xffffffff`00000000
STACK_COMMAND: kb

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

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ATITool64+6192

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ATITool64

IMAGE_NAME: ATITool64.sys

DEBUG_FLR_IMAGE_TI... Read more

http://www.sevenforums.com/bsod-help-support/195490-bsod-after-driver-verifier.html
Relevancy 73.1%

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/

http://www.sevenforums.com/bsod-help-support/228187-driver-verifier-bsods.html
Relevancy 72.67%

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

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?

http://www.sevenforums.com/bsod-help-support/358185-bsod-fairly-often-driver-verifier-enabled-bsod-boot-every-time.html
Relevancy 72.24%

I recently started a new job and was given a new Dell Laptop. I am having seemingly randomly BSOD issues. Some days it doesn't happen at all and some days it can happen up to ten times. I've got several BSOD errors (mainly CRITICAL PROCESS DIED). I believe it's a driver

related issue. I've tried updating all my drivers and firmware to no avail.

I used the Driver Verifier and immediately got errors with sedfilter.sys and symefasi64.sys. I had to boot into safe mode to turn the verifier off. I tried the verifier without those two enabled and got DRIVER VERIFIER DETECTED VIOLATION.

Help would be greatly appreciated, this issue is a real pain!

Here are the debug files:
debug-PMORRIS-Thu_03_03_2016_132145_24.zip

A:Driver Related BSOD - Driver Verifier

I found this with a Google search:

sedfilter.sys
Description: Related to SED Enhancement Driver from Dell Inc.

More here: What is sedfilter.sys ? | System Explorer

http://www.tenforums.com/bsod-crashes-debugging/42580-driver-related-bsod-driver-verifier.html
Relevancy 72.24%

I get a BSOD only when gaming Heroes of Newerth which really only uses a small portion of my computers power other games I while gaming Verifier BSOD Driver - makes BSOD hidclass.sys have not noticed any issues although I dont game other games BSOD while gaming - Driver Verifier makes BSOD hidclass.sys much Movies and general computering does not cause any BSOD I did a Driver Verifier BSOD came up hidclass sys BSOD while gaming - Driver Verifier makes BSOD hidclass.sys saved BSOD while gaming - Driver Verifier makes BSOD hidclass.sys 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 - bit Windows was the original OS Pre-Installed System is years old same as OS CPU - AMD Phenom II X Black Edition Deneb GHz Video Card - XFX HD- A-ZWFC Radeon HD GB -bit GDDR PCI Express x MotherBoard - ASUS M A XTD EVO AM AMD X ATX AMD Motherboard Power Supply - brand amp wattage - OSZ watt Model OCZ MXSP 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?

http://www.techsupportforum.com/forums/f299/bsod-while-gaming-driver-verifier-makes-bsod-hidclass-sys-586452.html
Relevancy 72.24%

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

http://www.sevenforums.com/bsod-help-support/358075-bsod-pc-freezes-randomly-driver-verifier-bsods-user-log.html
Relevancy 72.24%

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

http://www.sevenforums.com/bsod-help-support/276653-bsod-after-running-driver-verifier.html
Relevancy 72.24%

I have another post where people are helping me with BSODs on verifier BSOD? don't should get a disable If driver I I When 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 When should I disable driver verifier If I don't get a BSOD? the first 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 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 Forums thanks

http://www.tenforums.com/drivers-hardware/38243-when-should-i-disable-driver-verifier-if-i-dont-get-bsod.html
Relevancy 72.24%

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

http://www.sevenforums.com/bsod-help-support/276192-windows-8-pro-x64-bsod-driver-verifier.html
Relevancy 72.24%

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

http://www.eightforums.com/bsod-crashes-debugging/19122-windows-8-pro-x64-bsod-driver-verifier.html
Relevancy 72.24%

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 ConvertToYV matrix Rec interlaced false Normalize fft dgpu sigma plane smdegrain tr lsb true thsad lsb out true search Dither convey yuv xxp on yvxx Basically ff dgpu 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 atikmpag - BSOD Verifier Driver 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.

http://www.bleepingcomputer.com/forums/t/615696/driver-verifier-atikmpag-bsod/
Relevancy 72.24%

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

http://www.techsupportforum.com/forums/f299/random-bsod-and-after-driver-verifier-738258.html
Relevancy 72.24%

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 violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:Piriform - Speccy
CPUID - HWMonitor

http://www.sevenforums.com/bsod-help-support/308368-bsod-after-enabling-driver-verifier.html
Relevancy 72.24%

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_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMPPROCESS_NAME: SystemWARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.FAILURE_BUCKET_ID: X64_0xc9_24c_VRF_t_mouse+3310Bugcheck code 000000C9Arguments 00000000`0000024c fffff880`069c6310 fffff980`48c3ecf0 00000000`00000103BiosVersion = FCdBiosReleaseDate = 02/20/2012SystemManufacturer = Gigabyte Technology Co., Ltd.SystemProductName = M68MT-S2................................................................

http://www.bleepingcomputer.com/forums/t/459354/persistent-bsod-driver-verifier/
Relevancy 72.24%

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
---------

http://www.sevenforums.com/bsod-help-support/361620-bsod-when-starting-up-using-driver-verifier.html
Relevancy 72.24%

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 Z97 PC Mate(MS-7850)

??????????????????????????????????????????????????????????????????????????????????????``
**************************Thu Mar 19 02:31:43.829 2015 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\031815-4734-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 20:01:50.530

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

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

*** WARNING: Unable to verify timestamp for dxgkrnl.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+1a895 )

BugCheck 139, {3, ffffd0002b065e70, ffffd0002b065dc8, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)

Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002b065e70, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002b065dc8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR: 0x139

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

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 Z97 PC Mate(MS-7850)

??????????????????????????????????????????????????????????????????????????????????????``
**************************Tue Mar 17 10:04:40.786 2015 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\031715-5234-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: 2 days 1:39:45.599

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

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

Probably caused by : win32k.sys ( win32k+46da7 )

BugCheck 139, {3, ffffd0002304a870, ffffd0002304a7c8, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (13... Read more

http://www.eightforums.com/bsod-crashes-debugging/63362-bsod-driver-verifier-can-someone-decipher.html
Relevancy 72.24%

I was playing battlefield and got a BSOD today - - dmp PM MEMORY MANAGEMENT x a ffff ntoskrnl exe ntoskrnl exe cc NT Kernel amp System Microsoft Windows Operating System Microsoft Corporation win sp gdr - x ntoskrnl exe cc C Windows Minidump - - dmp is cause left verifier a BSOD? If driver on will it that is copy-pasted out of Blue Screen Viewer I recently ran Driver Verifier last night and it gave me a bluescreen for quot Applecharger sys quot 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 If driver verifier is left on will it cause a BSOD? 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

http://www.sevenforums.com/bsod-help-support/219040-if-driver-verifier-left-will-cause-bsod.html
Relevancy 72.24%

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.

http://www.eightforums.com/bsod-crashes-debugging/56564-bsod-loop-after-using-driver-verifier.html
Relevancy 71.38%

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 happen at startup, but should happen after using it for a while).

Temperature

For monitoring heat of the system, use Speccy or HWMonitor:
Speccy System Information

HWMonitor

This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
http://www.carrona.org/drivers/driver.php?id=xusb21.sys

AppleCharger.sys Tue Apr 27 09:54:05 2010 (4BD65FDD)
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys

nusb3hub.sys Thu Feb 10 11:52:32 2011 (4D537D20)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys

nusb3xhc.sys Thu Feb 10 11:52:33 2011 (4D537D21)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys

dtsoftbus01.sys Fri Jan 13 19:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
Daemon Tools/Alcohol %

Uninstall DAEMON Tools and/or Alcohol % software. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

The below is for information purposes only. Contains relevant information from the blue screen analysis:

Code:
Debug session time: Mon Apr 29 02:58:17.131 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042813-96970-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:00:56.019
Probably caused by : ntkrnlmp.exe ( nt!CmBootLastKnownGood+2f )
BugCheck 5A, {1, 1, 0, 0}
BugCheck Info: CRITICAL_SERVICE_FAILED (5a)
Bugcheck code 0000005A
Arguments:
Arg1: 0000000000000001
Arg2: 0000000000000001
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR: 0x5A
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
P... Read more

http://www.sevenforums.com/bsod-help-support/288160-bsods-driver-verifier-bsods-c-disk-check-os-hdd-more.html
Relevancy 71.38%

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 would suggest you to uninstall it, at least upto when you find your computer is stable. mcdbus.sys causes system instabilities.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
Click on the Start button
Type ?msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the ?Startup? tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.
Let us know the results.

http://www.sevenforums.com/bsod-help-support/313481-random-bsod-ran-driver-verifier-now-got-0x000000c9-bsod.html
Relevancy 71.38%

I've been having troubles for nearly a month now I've tried replacing RAM and checking RAM slots checking my HDD with several programs including Windows programs checking drivers in various ways and upgrading my OS from disk as a Hail Mary The OS upgrade was the only thing to seemingly make any change as it noticed immediately upon startup that the NET Framework was damaged Repairing it did not solve this issue I've used Driver Verifier to determine the issue and it crashes at the login screen When I restart into safe mode with networking BlueEventViewer determines that it is ntoskrnl exe and tcpipreg sys From previous forum searches on multiple different forums I have concluded that ntoskrnl exe is merely taking the blame but I am unsure on tcpipreg sys Attached are a perfmon zip and a sysnative zip If anything else is needed please let me know Edit I'd like to add that if I remove the power cord to the laptop I lose input The mouse will still move but refuses to click "tcpipreg.sys+35a5" - BSOD Verifier Driver and keyboard input fails entirely This is only solved with Driver Verifier BSOD - "tcpipreg.sys+35a5" a hard shutdown restart as far as I can tell This is a very recent issue and I cannot tie it to any software or hardware changes And as Driver Verifier BSOD - "tcpipreg.sys+35a5" for other required info OS - Windows Professional SP This is an x -based PC Windows Professional SP was originally installed This is an OEM version The system was built in March April I last reinstalled the OS on December th CPU - Intel i MQ GPU - Nvidia GTX M I'm not sure who manufactured this but I purchased it from ibuypower I am not sure how to check the serial number This is a laptop

http://www.bleepingcomputer.com/forums/t/599852/driver-verifier-bsod-tcpipregsys35a5/
Relevancy 71.38%

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: 0002E73E
ImageSize: 00029000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

http://www.sevenforums.com/bsod-help-support/326845-driver-verifier-bsod-usbport-sys-bluescreenview.html
Relevancy 71.38%

Hello, while working one evening I got my first BSOD on this machine, so I enabled driver verifier and have been getting an 0x0000000a on start up infrequently.

I'm assuming this is going to have something to do with the drivers for my mobo, as I ended up grabbing a lot of Intel Smart connect and crap. I've been updating/uninstalling unnecessary drivers, but I'm no good at analyzing dumps, so could anyone help point me in the right direction here?

A:BSOD (0x0000000a) with driver verifier - looking for some confirmation

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff8000327d315}

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

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000327d315, address which referenced memory

Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b0100
GetUlongFromAddress: unable to read from fffff800034b01c0
0000000000000000 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+1e3
fffff800`0327d315 488b00 mov rax,qword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800374e950 -- (.trap 0xfffff8800374e950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880029c9210
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000327d315 rsp=fffff8800374eae0 rbp=0000000000000000
r8=0000000000000000 r9=fffff880009b3180 r10=0000000000000000
r11=fffff80003430260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KeSetEvent+0x1e3:
fffff800`0327d315 488b00 mov rax,qword ptr [rax] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032781a9 to fffff80003278c00

STACK_TEXT:
fffff880`0374e808 fffff800`032781a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0374e810 fffff800`03276e20 : 00000000`00000160 00000000`00000000 00000000`0000000d fffff880`029c9208 : nt!KiBugCheckDispatch+0x69
fffff880`0374e950 fffff800`0327d315 : fffffa80`07f53702 fffffa80`07f53710 00000000`00000000 fffff980`07a94ea0 : nt!KiPageFault+0x260
fffff880`0374eae0 fffff880`07119817 : fffff880`00000000 fffff980`00000008 fffff800`03426d00 fffffa80`0ac29f50 : nt!KeSetEvent+0x1e3
fffff880`0374eb50 fffff880`00000000 : fffff980`00000008 fffff800`03426d00 fffffa80`0ac29f50 fffffa80`07f53710 : MBfilt64+0x1817
fffff880`0374eb58 fffff980`00000008 : fffff800`03426d00 fffffa80`0ac29f50 fffffa80`07f53710 fffff800`037213fb : 0xfffff880`00000000
fffff880`0374eb60 fffff800`03426d00 : fffffa80`0ac29f50 fffffa80`07f53710 fffff800`037213fb fffffa80`07f53710 : 0xfffff980`00000008
fffff880`0374eb68 fffffa80`0ac29f50 : fffffa80`07f53710 fffff800`037213fb ... Read more

http://www.sevenforums.com/bsod-help-support/293407-bsod-0x0000000a-driver-verifier-looking-some-confirmation.html
Relevancy 71.38%

Hello again my previous BSOD errors have stopped after someone in the forums told me to change the settings and install new drivers However after downloading a new nVidia graphics card driver my computer would constantly be hit with a Driver Verifier Detected Violation error I was wondering what I should do to fix this problem I was able to run my PC on safemode and turn of turn off the verifier but people have said that this is not enough Minidump files http www sendspace com file qfsc Speccy http speccy piriform com results uGRgevQJeUE jNDQcc kTda Minitool Box Result MiniToolBox by Farbar Version - - Ran by Joshua administrator on - - at Running from C Users Joshua Downloads Microsoft Windows Pro X Boot Mode Normal Event log errors Application errors Error PM Source Software Protection Platform Service User Description Verifier Driver Detected BSOD Violation License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId Driver Verifier Detected Violation BSOD c b -d fd- a -b b - b af NotificationInterval Driver Verifier Detected Violation BSOD Trigger UserLogon SessionId Error PM Source Software Protection Platform Service User Description License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId c b -d fd- a -b b - b af NotificationInterval Trigger NetworkAvailable Error PM Source Application Error User Description Faulting application name MsiExec exe version time stamp x f e Faulting module name MSIB tmp version time stamp x d Exception code xc Fault offset x Faulting process id x Faulting application start time xMsiExec exe Faulting application path MsiExec exe Faulting module path MsiExec exe Report Id MsiExec exe Faulting package full name MsiExec exe Faulting package-relative application ID MsiExec exe Error PM Source MsiInstaller User Joshua-PC Description Product Adobe Reader XI - Update ' AC BA - AD - - - A C ' could not be installed Error code Windows Installer can create logs to help troubleshoot issues with installing software packages Use the following link for instructions on turning on logging support http go microsoft com fwlink LinkId Error PM Source Software Protection Platform Service User Description License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId c b -d fd- a -b b - b af NotificationInterval Trigger NetworkAvailable Error PM Source Software Protection Platform Service User Description License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId c b -d fd- a -b b - b af NotificationInterval Trigger NetworkAvailable Error PM Source Software Protection Platform Service User Description License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId c b -d fd- a -b b - b af NotificationInterval Trigger NetworkAvailable Error PM Source Software Protection Platform Service User Description License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId c b -d fd- a -b b - b af NotificationInterval Trigger NetworkAvailable Error PM Source Software Protection Platform Service User Description License Activation slui exe failed with the following error code hr xC F Command-line arguments RuleId ff ba- a- -bbb - f a b Action AutoActivateSilent AppId c -d - d - e-d ec f f SkuId c b -d fd- a -b b - b af NotificationInterval Trigger NetworkAvailable Error PM Source Softwar... Read more

A:Driver Verifier Detected Violation BSOD

Hi
 
As part of an attempt to figure out the reason behind the blue screens, you might have accidentally enabled "Verfier" program. To disable that, please follow the below steps.
 
Open an elevated command prompt - http://www.bleepingcomputer.com/tutorials/windows-elevated-command-prompt/
 
Type Verifier /reset and press Enter key. Reboot the system to apply the change. 
 
 Enter Verifier /query and you should get a response similar to "No drivers are currently verified".

http://www.bleepingcomputer.com/forums/t/536261/driver-verifier-detected-violation-bsod/
Relevancy 71.38%

Hi i recently installed a new graphics card aswell as ram, and i have been recieving different bsod at random. really need help this. i changed my ram to the old one still got bsod .

Specs =
OS - Windows 7 home
ram- 6gb
hdd- 2tb
antivirus-avast

image of bluescreen viwer with different bsod errors


ImageShack? - Online Photo and Video Hosting

A:Bsod driver verifier detected violation

You have uploaded four crash dumps and there is no driver verifier detected violation. There is no trace of DV enabled in either of dumps, but there is enough need to enable DV. Have you thought something and posted something else?

Anyway, there are two drivers at fault ... AswSNX.sys and AswSP.sys. Both are parts of Avast antivirus. Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.

http://www.sevenforums.com/bsod-help-support/270645-bsod-driver-verifier-detected-violation.html
Relevancy 71.38%

I have been getting BSOD several times a day I assume I have a driver issue Specs AMD Athlon x GHz processor Gigabyte GN-WP GS PCI WLAN card Realtek PCIe GBE Verifier Driver - attached Help minidump BSOD Network Controller Nvidia GForce LE graphics card BSOD Help - Driver Verifier minidump attached G DDR PC RAM Gigabyte GA-MA GM-S motherboard OS bit Windows clean install I have updated all drivers that I could think of video card chipset audio Bios update NIC I performed RAM tests no issues there reset page file checked harddrive pulled out each ram stick but still got BSOD Checked power voltages temps with no issues I have run out of ideas I can see from the minidump that my AVG virus protection could be involved but I am not sure how to read these minidumps I BSOD Help - Driver Verifier minidump attached would appreciate any help Here is the KD Analyze from the minidump that resulted from verifier kd gt analyze -v Bugcheck Analysis PAGE FAULT IN NONPAGED AREA Invalid system memory was referenced This cannot be protected by try-except it must be protected by a Probe Typically the address is just plain bad or it is pointing at freed memory Arguments Arg fffffffffffffff memory referenced Arg value read operation write operation Arg fffff dc ed If non-zero the instruction address which referenced the bad memory address Arg reserved Debugging Details ------------------ Could not read faulting driver name WRITE ADDRESS GetPointerFromAddress unable to read from fffff cfd e fffffffffffffff FAULTING IP fltmgr FltReferenceContext d fffff dc ed f fc lock xadd dword ptr r h eax MM INTERNAL CODE CUSTOMER CRASH COUNT DEFAULT BUCKET ID VISTA DRIVER FAULT BUGCHECK STR x PROCESS NAME Safari exe CURRENT IRQL TRAP FRAME fffff a -- trap xfffff a NOTE The trap frame does not contain all registers Some register values may be zeroed or incorrect rax rbx rcx rdx rsi rdi rip fffff dc ed rsp fffff a b rbp d r fffffa ba r ffffffffffffffa r fffffa e c r fffff a r r r r iopl nv up ei ng nz na pe nc fltmgr FltReferenceContext xd fffff dc ed f fc lock xadd dword ptr r h eax ds f ffffffff fffffff Resetting default scope LAST CONTROL TRANSFER from fffff b e to fffff ac f STACK TEXT fffff a b fffff b e ffffffff fffffff fffff a nt KeBugCheckEx fffff a c fffff ac fee fffff a nt FNODOBFM string' x fffff a fffff dc ed fffffa c a a fffff db fffffa e c fffffa e c nt KiPageFault x e fffff a b fffff efe c fffffa e c fffff a fffffa c a a fltmgr FltReferenceContext xd fffff a f fffff db fffffa luafv LuafvPreSetInformation x fffff a fffff db be fffff a fffff ad fffffa b d fffffa cab fltmgr FltpPerformPreCallbacks x f fffff a fffff db c fffffa a fffffa fffffa c fffffa cab fltmgr FltpPassThrough x d fffff a d fffff d a d fffff ae d c fcf fltmgr FltpDispatch xb fffff a a fffff ae d c fcf fffffa AVGIDSFilter x a d fffff a a fffff ae d c fcf fffffa fffffa a f x fffff a a fffff da b fffffa b da fffffa a fffffa a nt ExAllocatePoolWithQuotaTag xbc fffff a a fffff ac a fffffa cab dfe fffff nt NtSetInformationFile x c fffff a bb nt KiSystemServiceCopyEnd x STACK COMMAND kb FOLLOWUP IP luafv LuafvPreSetInformation fffff efe c b c mov rcx qword ptr rsp h SYMBOL STACK INDEX SYMBOL NAME luafv LuafvPreSetInformation FOLLOWUP NAME MachineOwner MODULE NAME luafv IMAGE NAME luafv sys DEBUG FLR IMAGE TIMESTAMP a bc FAILURE BUCKET ID X x luafv LuafvPreSetInformation BUCKET ID X x luafv LuafvPreSetInformation

A:BSOD Help - Driver Verifier minidump attached

Actually this is not the verifier minidump. I guess I lost that when I did the system restore. I will have to figure a way to get the minidump posted from safemode before I system restore. I will post that shortly.

http://www.techsupportforum.com/forums/f299/bsod-help-driver-verifier-minidump-attached-442910.html
Relevancy 71.38%

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 - Verifier BSOD Violation Driver Detected a violation These particular BSOD's BSOD - Driver Verifier Violation Detected 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 BSOD - Driver Verifier Violation Detected haven't used it that much If you need any more information just ask and it would be much appreciated BSOD - Driver Verifier Violation Detected if you could help me out with this issues Many thanks in advance and here's my file Attachment 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 EDIT 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?

http://www.eightforums.com/bsod-crashes-debugging/57928-bsod-driver-verifier-violation-detected.html
Relevancy 71.38%

I was having BSOD crash episodes several time a day. I followed the advice to setup Driver Verifier to discover what the issue was.  That is where the problems got worse
:
Now every every boot fails because of a DRIVER_VERIFIER_DETECTED_VIOLATION.
 
I tried to reconfigure driver verifier so that it would not check anything... the error still happens at boot. I cot to cmd and tried verifier /bootmode resetonbootfail and also verifier /reset.  No Joy.
 
Through the Windows 10 BSOD menus I am able to get into the Safe Mode, but that's about it.
 
I'm attaching the latest dump file.
 
Any suggestions?
 
Thanks!

A:BSOD crashes - Tried Driver Verifier, not it's much worse. Win 10

Do you have a backup of any files/documents/pics/music/important stuff  etc etc etc  ?

http://www.bleepingcomputer.com/forums/t/594885/bsod-crashes-tried-driver-verifier-not-its-much-worse-win-10/
Relevancy 71.38%

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.

http://www.sevenforums.com/bsod-help-support/195095-bsod-w-driver-verifier-now-what-all-files-included.html
Relevancy 71.38%

Hello,

BSOD happened randomly and frequently in recent days. I tried to narrow down the problem by myself but I can't recall what major changes I did to my PC to cause BSOD during the time. Therefore, I took advice from good people here to use Driver Verifier. Then BSOD happened even before I can enter windows...

Here is the system info and dump files after Driver Verifier. Thank you for your help

Best,
Allen

A:BSOD before enter Windows (when Driver Verifier is on)

Welcome aboard.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88001097324, fffff9800656cee0, 0}

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

Followup: MachineOwner
---------
Uninstall Daemon tools. It is the most frequent BSOD causer in windows 7.

Let us know the results.

http://www.sevenforums.com/bsod-help-support/264978-bsod-before-enter-windows-when-driver-verifier.html
Relevancy 71.38%

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.htm


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

Regards. . .

jcgriff2


`


BSOD BUGCHECK SUMMARY

Code:

Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sun Oct 17 17:50:31.542 2010 (GMT-4)
System Uptime: 0 days 17:22:42.154
Probably caused by : memory_corruption ( nt!MiMapPagesForZeroPageThread+aa )
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
Bugcheck code 1000007E
Arguments c0000005 82a7b13f 80399c38 80399934
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sat Oct 16 20:46:07.170 2010 (GMT-4)
System Uptime: 0 days 15:59:06.315
*** WARNING: Unable to verify timestamp for pcouffin.sys
*** ERROR: Module load completed but symbols could not be loaded for pcouffin.sys
Probably caused by : pcouffin.sys
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
Bugcheck code 0000009F
Arguments 00000003 8515b9e0 876a9c18 892c69f8
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Fri Oct 15 19:06:20.342 2010 (GMT-4)
System Uptime: 0 days 0:00:40.170
Probably caused by : win32k.sys ( win32k!MAPPER::vEmergency+a5 )
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
Bugcheck code 1000008E
Arguments c0000005 82572930 8cf25898 00000000
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sat Oct 9 22:22:51.033 2010 (GMT-4)
System Uptime: 0 days 0:12:04.883
BugCheck D1, {0, 2, 0, 99c0b18b}
Probably caused by : afd.sys ( afd!AfdUpdateConnectionForTimerWheel+3e )
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
Bugcheck code 000000D1
Arguments 00000000 00000002 00000000 99c0b18b
??????????????????????????????????????????????????????????????????????????????????????``
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Debug session time: Sat Oct 9 22:09:05.588 2010 (GMT-4)
System Uptime: 0 days 0:20:28.460
Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
BUGCHECK_STR: 0x1a_5003
DEFAULT... Read more

http://www.techsupportforum.com/forums/f299/bsod-driver-verifier-enabled-vista-sp2-x86-523218.html
Relevancy 71.38%

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.

http://www.sevenforums.com/bsod-help-support/248027-driver-verifier-bsod-no-dmp-files-being-created.html
Relevancy 70.52%

Hello,

After a recent software install I have been seeing a blank black screen after logging into windows vista, and have had to manually start explorer.exe from task manager. I remedied this problem once in the past by following the verifier instructions from jcgriff2 on this thread http://www.techsupportforum.com/microsoft-support/windows-vista-support/360482-computer-crashes-windbg-analysis.html but after a recent software and driver install for an mp3 player, the same problem occured; I would get a black startup screen, would have to manually start explorer.exe, and would lack many of my startup programs like avg virus tray and others. I retried using the verifier method, and repeatedly got BSODs after restarting my computer. Can anyone help me fix this issue? The minidump file is attached at the bottom. Thank you.

Joseph Wang

A:BSOD after running driver verifier from command prompt

Quote:





Originally Posted by joewangtt


Hello,

After a recent software install I have been seeing a blank black screen after logging into windows vista, and have had to manually start explorer.exe from task manager. I remedied this problem once in the past by following the verifier instructions from jcgriff2 on this thread http://www.techsupportforum.com/microsoft-support/windows-vista-support/360482-computer-crashes-windbg-analysis.html but after a recent software and driver install for an mp3 player, the same problem occured; I would get a black startup screen, would have to manually start explorer.exe, and would lack many of my startup programs like avg virus tray and others. I retried using the verifier method, and repeatedly got BSODs after restarting my computer. Can anyone help me fix this issue? The minidump file is attached at the bottom. Thank you.

Joseph Wang




Hi Joseph. . .

Well, the driver verifier did its job and flagged a rogue driver. The verifier will either cause or force a BSOD once a driver is caught. In the instructions from the post you referenced, I mention the fact that one may need to resort to system restore, system repair, etc... to regain control of the system if the verifier is successful. The next step is dealing with the bad driver - removal, update, etc..

Driver verifier post - http://www.techsupportforum.com/2046409-post2.html

The dump file you attached was in fact a verifier-enabled Vista mini kernel dump. It was BSOD #4 for the day as of Fri Apr 3 21:30:05.259 2009 (GMT-4). The bugcheck -

0xc1 (0xb4ad2ff0, 0xb4ad2ffc, 0x274010, 0x24), caused by the driver verifier flagging nltdi.sys, timestamp = Mon Apr 23 07:02:47 2007. It belongs to Netlimiter - the Internet monitoring tool.

0xc1 = a driver wrote to an invalid section of the special pool.

Un-install Netlimiter.

Some reasons for the BSODs - Netlimiter clashed with recent Windows Updates or possibly with one of these 3rd party drivers - probably the 1st one listed -

Code:

Realtek Ethernet
Rtlh86.sys Tue Jan 20 01:49:26 2009 (497573F6)

NVIDIA
nvBridge.kmd Wed Feb 18 19:14:13 2009 (499CA455)
nvlddmkm.sys Wed Feb 18 19:40:51 2009 (499CAA93)

AVG
avgtdix.sys Wed Jan 28 13:46:08 2009 (4980A7F0)
avgldx86.sys Thu Feb 19 06:46:30 2009 (499D4696)


I found other older drivers in the loaded driver listing that I would advise you look into -

Code:


Blackberry
RimSerial.sys Tue Jan 09 11:52:20 2007 (45A3C844)

GEAR Software CD/DVD filter
GEARAspiWDM.sys Mon Aug 07 13:11:27 2006 (44D7743F)

SpeedFan
giveio.sys Wed Apr 03 22:33:25 1996 (316334F5)
speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)

No information available for this driver -
- it may be dynamically allocated during program execution
aovdcxox.SYS Mon Jun 04 01:12:12 2007 (46639F2C)

Realtek audio codec
RTKVHDA.sys Wed Jul 18 07:31:17 2007 (469DFA05)

Ralink RT61 wifi
netr61.sys Fri Sep 28 09:37:28 2007 (46FD0398)

Sonic Solutions
SaibIa32.sys Tue Oct 09 04:24:03 2007 (470B3AA3)
SaibVd32.sys Tue Oct 09 04:24:07 2007 (470B3AA7)

Symantec/ Norton Ghost ( ?? )
symsnap.sys Wed Dec 12 14:31:49 2007 (47603725)
v2imount.sys Wed Dec 12 14:07:19 2007 (47603167)




.

I believe the drivers listed above could be next on the driver verifier's hit list.

Bottom line here is that the verifier worked and the aftermath is no surprise to me. I applaud your initiative in searching, locating and running the driver verifier. But some things found in forums are very user specific. Driver Verifier is a vital asset in troubleshooting BSODs, but as you now know, it can lead you down many unknown roads during its workday.

My advice to you -
1. un-install Netlimiter
2. un-install SpeedFan - new version out that does not include the 1996 driver -
http://www.almico.com/sfdownload.php
3. un-install Norton Ghost (if my gues... Read more

http://www.techsupportforum.com/forums/f299/bsod-after-running-driver-verifier-from-command-prompt-363215.html
Relevancy 70.52%

So i enabled Driver Verifier and got a BSOD I disabled it and looked at another post from November regarding ScpVBus sys I had the exact same BSOD for the exact same reason If you are BSOD Verifier/DRIVER_POWER_STATE_FAILURE problem while enabling Driver looking at this Arc you know what im talking BSOD while enabling Driver Verifier/DRIVER_POWER_STATE_FAILURE problem about ScpVBus is Scarlet Crush Productions SCP Driver It tricks the XBOX Microsoft controller driver thinking it is a Dualshock PS Controller The BSOD says clear The IO manager has detected a violation by a driver that is being verified must be debugged and replace with a working version Well i don't know if Scarlet Crush have any new updates available for it I want to keep it because it is hard for me playing a game without my PS controller Any help so the driver can stop its misbehavior Why i turned on Driver Verifier on the first place is because i have a BSOD while enabling Driver Verifier/DRIVER_POWER_STATE_FAILURE problem DRIVER POWER STATE FAILURE that is ongoing and the dump says that it is unidentified Unknown Image I tried to verify what driver that is causing this problem The question on the first place is it the Scarlet Crush driver Little embarrassing for me lol

A:BSOD while enabling Driver Verifier/DRIVER_POWER_STATE_FAILURE problem

Blue Screen of Death (BSOD) Posting Instructions

http://www.sevenforums.com/bsod-help-support/356222-bsod-while-enabling-driver-verifier-driver_power_state_failure-problem.html
Relevancy 70.52%

I've been having a lot of BSOD problems while playing games lately and it (the bsod) says it's the dxgkrnl.sys that causes it which I read online it was a driver issue, so I ran the Windows Driver Verifier from command prompt and once my pc started up I got a BSOD and informed me I had faulty drivers, I'm just unsure of what drivers are actually conflicting. If anyone could help it'd be awesome.
The minidump is attached, thanks.

A:BSOD after running driver verifier from command prompt

This is not a Driver Verifier generated memory dump - and it points to the same file as before. It's also the 3rd dump file generated on July 8 - so I must ask..."Where are the rest?"

Please zip up the entire contents of the C:\Windows\Minidump folder and upload that .zip file with your next post.

Also, please let us know where, in the sequence of BSOD's, that you enabled Driver Verifier - and if you've disabled it.

Also, please let us know what instructions that you followed to run it.

Older drivers running when the crash occurred. Please notice that DB3G.sys is from 2005!:

Code:
SI3132.sys Wed Oct 03 14:39:29 2007
SiWinAcc.sys Thu Jun 14 20:02:02 2007
SiRemFil.sys Wed Jun 20 15:42:10 2007
DB3G.sys Mon Nov 07 01:33:11 2005
Dump file:

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\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
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01c1f000 PsLoadedModuleList = 0xfffff800`01de3dd0
Debug session time: Wed Jul 8 21:06:52.313 2009 (GMT-4)
System Uptime: 0 days 1:01:48.420
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88090643aa0, 1, fffffa60030c7359, 5}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::CloseAllocation+35 )

Followup: MachineOwner
---------

2: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q
GetPointerFromAddress: unable to read from fffff80001e46000
THREAD fffffa80090d7720 Cid 0e80.0a0c Teb: 0000000079b95000 Win32Thread: fffff900c27d8d50 RUNNING on processor 2
Not impersonating
GetUlongFromAddress: unable to read from fffff80001dc5c00
Owning Process fffffa8005d4a920 Image: WAR.exe
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 237717
Context Switch Count 3119780 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x000000006f440eea
Stack Init fffffa60084e2db0 Current fffffa60084e2940
Base fffffa60084e3000 Limit fffffa60084dc000 Call 0
Priority 11 BasePriority 8 PriorityDecrement 2 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffffa60`084e2678 fffff800`01cd9a26 : 00000000`00000050 fffff880`90643aa0 00000000`00000001 fffffa60`084e2760 : nt!KeBugCheckEx
fffffa60`084e2680 fffff800`01c77fd9 : 00000000`00000001 fffffa60`02a33003 fffff880`0a4ba000 fffff880`10643aa0 : nt! ?? ::FNODOBFM::`string'+0x2c42d
fffffa60`084e2760 fffffa60`030c7359 : 00000000`00000001 fffffa60`084e2998 00000000`00000001 fffff880`0fd8e910 : nt!KiPageFault+0x119 (TrapFrame @ fffffa60`084e... Read more

http://www.techsupportforum.com/forums/f299/bsod-after-running-driver-verifier-from-command-prompt-393484.html
Relevancy 70.52%

Hello I have recently build build my own pc This pc has never worked stable i've been experiencing random bsod's Sometimes they come in a row and the system is stable for only a few minutes Sometimes usually when I tweaked a little with the system like increased the voltage over the ram modules or removed a network card which I didn't use reinstall windows the system would be stable for days before the bsod's came in big numbers again Today I used the driver verifier to see if the problem was driver related When my computer would verifier Driver Random startup + BSOD's crash start up with driver Random BSOD's + Driver verifier startup crash verifier enabled the system would crash before it could startup windows It did however generate a minidump file containing information about the crash The last minidumps that are attached are caused by the driver varifier startup crash the other files are due to random crashes over the past month My system specs Random BSOD's + Driver verifier startup crash Windows Ultimate x Full Retail Processor AMD Phenom II X T Processor GHz Memory x GB DDR - G Video Card Asus Eah- MB Motherboard MSI A-G - Socket AM - ATX I Random BSOD's + Driver verifier startup crash hope dat I have provided you with enough information Any help on this matter would be greatly appreciated

A:Random BSOD's + Driver verifier startup crash

  
Quote: Originally Posted by Jim Tol


Hello,

I have recently build build my own pc. This pc has never worked stable, i've been experiencing random bsod's. Sometimes they come 20 in a row and the system is stable for only a few minutes. Sometimes, usually when I tweaked a little with the system, like increased the voltage over the ram modules or removed a network card which I didn't use, reinstall windows, the system would be stable for days before the bsod's came in big numbers again.

Today I used the driver verifier to see if the problem was driver related. When my computer would start up with driver verifier enabled, the system would crash before it could startup windows. It did however generate a minidump file containing information about the crash. The last 5 minidumps that are attached are caused by the driver varifier startup crash, the other files are due to random crashes over the past month.

My system specs:
Windows 7 Ultimate x64, Full Retail
Processor: AMD Phenom II X6 1055T Processor 2.80 GHz
Memory: 2x 2GB DDR3-1333G
Video Card: Asus Eah-5670, 512 MB
Motherboard: MSI 870A-G54 - Socket AM3 - ATX

I hope dat I have provided you with enough information. Any help on this matter would be greatly appreciated!


virtually all were identical and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. I would remove it to test.

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\Windows_NT6_BSOD_jcgriff2\053111-24850-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032a3e50
Debug session time: Tue May 31 10:35:50.580 2011 (GMT-4)
System Uptime: 0 days 0:00:19.876
Loading Kernel Symbols
...............................................................
......................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88002a2d308, fffff9800e57eea0, 0}

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

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88002a2d308, The address in the driver's code where the error was detected.
Arg3: fffff9800e57eea0, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------... Read more

http://www.sevenforums.com/bsod-help-support/166431-random-bsods-driver-verifier-startup-crash.html
Relevancy 70.52%

DRIVER VERIFIER - Windows amp Vista If your BSODs are rd party software related the Driver Verifier will help & Windows 8.1, - 8.0, (BSOD-related) Vista Verifier Driver 7 flush out the rogue Driver Verifier - Windows 8.1, 8.0, 7 & Vista (BSOD-related) driver by flagging it and causing your system to BSOD Please feel free to run the Driver Verifier however system information is also needed Please see BSOD Posting Driver Verifier - Windows 8.1, 8.0, 7 & Vista (BSOD-related) Instructions sticky Create a Driver Verifier - Windows 8.1, 8.0, 7 & Vista (BSOD-related) Windows System Restore Point - Vista - START type rstrui - create a restore point Windows - START type create select quot Create a Restore Point quot Windows - - Using Microsoft System Restore Windows HP Support Run the Driver Verifier - Code START type verifier make these selections - Select nd option - quot Create custom settings for code developers quot Select nd option - quot Select individual settings from a full list quot Check these boxes - Special Pool Pool Tracking Force IRQL checking Deadlock Detection Security Checks new as of Windows Concurrency Stress Test new as of Windows DDI compliance checking new as of Windows Miscellaneous Checks Select last option - quot Select driver names from a list quot Click on the Provider heading - sorts list by Provider Check ALL boxes where quot Microsoft quot IS NOT the Provider Click on Finish Re-boot IMPORTANT - PLEASE READ - If the Driver Verifier DV finds a violation it will result in a BSOD - After re-start you may not be able to log on to normal Windows Boot into SAFEMODE - tap the F key repeatedly during boot-up Select quot System Restore quot Choose the restore point that you created in step - For Driver Verifier status --- select last option st screen -or- --- type verifier query in a cmd DOS screen - To turn Driver Verifier off - verifier reset then re-boot - The Driver Verifier needs to run as long as possible - even if the status screen appears clear - All future BSOD dumps must be VERIFIER ENABLED MINIDUMPs - otherwise the dump s are of no use If your system does BSOD while the Driver Verifier is running please retrieve the dump file from c windows minidump zip it up amp attach to your next post About Driver Verifier Driver Verifer information -- gt driver verifier Windows Vista - Microsoft Search Driver Verifier issues within Vista Windows -- gt http support microsoft com default aspx verifier amp res Driver Verifier Special Pool Feature - http support microsoft com kb Using Driver Verifier to identify issues with Windows drivers for advanced users Memory dump options - http support microsoft com kb If you have any questions please send me a PM jcgriff

Relevancy 70.52%

Hi there, I've recently been getting random BSOD events, 8 so far, showing 5 different causes, (ndis.sys / ntoskrnl.exe (x3) / Rt64win7.sys / cdd.dll )
I've ran memtest on all 4 sticks of ram with no errors and ran the machine with driver verifier on.
this is when i got 2 BSOD within a few minutes of each other, both pointing to nvlddmkm.sys+9b0a1.
i have the latest drivers installed from nvidia for the graphics card (and had them installed at the time of the last two BSOD)

should i try an older video card driver?

any help would be greatly appreciated.

Edit: BSOD last night again, win32k.sys this time

Attachment 306899

A:Random BSOD, nvlddmkm.sys identified by driver verifier

I've uninstalled all nvidia drivers, cleaned using the DDU tool and installed 334.89 driver. i'll see how it goes.

also noticed my processor has been running at 3.69GHz so ive disabled intel turbo boost to bring it back down to 2.79GHz. not sure if this will do anything at all but im willing to try it out.

http://www.sevenforums.com/bsod-help-support/322347-random-bsod-nvlddmkm-sys-identified-driver-verifier.html
Relevancy 70.52%

OS - Windows x Original installed OS on system Windows hidclass.sys driver after running win32k.sys BSoD: verifier) (and Home Premium Currently Windows Ultimate OEM SP is installed Age of system hardware is about months Age of OS installation BSoD: win32k.sys (and hidclass.sys after running driver verifier) - have you re-installed the OS I installed W Ultimate the moment I got my PC I have not reinstalled later CPU Intel Core i - QM Video Card NVIDIA GTX M MotherBoard I'd guess ASUS maybe Power Supply - brand amp wattage No idea as this is BSoD: win32k.sys (and hidclass.sys after running driver verifier) a laptop System Manufacturer Asus Exact model number if laptop check label on BSoD: win32k.sys (and hidclass.sys after running driver verifier) bottom Asus G SX laptop Okay so I got a BSoD earlier which probably was caused by win k sys so I ran memtest with passes and I got no errors Then I enabled Driver Verifier and the first time I booted up my PC I got a BSoD at the login screen I don't remember what it said When I started my PC again I could log in but as the desktop was loading I got a BSoD blaming hidclass sys I rebooted a couple of times just to make sure and I got it every time So far I think I understand that hidclass sys is rarely the cause itself but that some USB-thingy is to blame I had some problems with perfmon it did it's thing but in the end it said quot An error occured while attempting to generate the report The wait for the report generation tool to finish has timed out but I did some things I didn't really understand and went to C Perflogs and picked up some files that I compressed together with the jcgriff tool results I don't know if it is of any help Please ask if there is anything more you need to know Regards adrianpip

A:BSoD: win32k.sys (and hidclass.sys after running driver verifier)

We need the DMP files.

Please follow the instructions posted here.

http://www.techsupportforum.com/foru...ta-452654.html

If you already have the DMP files please upload them in your next post.

http://www.techsupportforum.com/forums/f299/bsod-win32k-sys-and-hidclass-sys-after-running-driver-verifier-654701.html
Relevancy 70.52%

Before I start every blue screen I get is a irql not equal Verifier BSOD Driver on irql_not_equal_or_less startup after windows or less and I have run memtest on my ram cards with no issues Also I am using bit Windows For a while now I have BSOD irql_not_equal_or_less on startup after windows Driver Verifier been having some problems with blue screens on my computer when I am turning it off or into sleep and sometimes during startup Well I mostly fixed it by updating multiple drivers on my computer like my intel graphics driver After that it really only blue screened when I tried to put it into sleep mode Yet recently I tried re-downloading league-of-legends and every time it would blue screen near the end of the download Thus to fix this I searched on the windows help BSOD irql_not_equal_or_less on startup after windows Driver Verifier forum and found the Driver Verifier software on windows BSOD irql_not_equal_or_less on startup after windows Driver Verifier and used it following the instructions Well now I am unable to get back into windows using the dual-booted Linux OS because it bluescreens right after I put in my login password Then I try safe mode and my computer just turns off not booting up in safe mode either Basically my question is how to get my computer to boot windows up Since I know it is very much needed is there a way I can open or post the MiniDump files from Linux Since I cannot boot windows its hard to get exact computer info unless I can from Linux but here is what I can remember Windows bit intel Core i GHz Gbs Ram Sony Vaio Laptop Integrated Graphics Intel Graphics driver Directx Please help me and if you need any info on my computer I would be happy to try and get it if you can tell me how to on linux -Jeffrey

A:BSOD irql_not_equal_or_less on startup after windows Driver Verifier

Can you try to boot into safe mode (F8)

Then try this:

SF Diagnostic Tool - Using for Troubleshooting

http://www.sevenforums.com/bsod-help-support/336695-bsod-irql_not_equal_or_less-startup-after-windows-driver-verifier.html
Relevancy 70.52%

DRIVER VERIFIER - Windows amp Vista If your BSODs are rd party software related the Driver Verifier will help flush out Driver 10, Vista Verifier 8, (BSOD-related) - & 8.1, Windows 7 the rogue Driver Verifier - Windows 10, 8.1, 8, 7 & Vista (BSOD-related) driver by flagging it and causing your system to BSOD Please feel free to run the Driver Verifier however system information is also needed Please see BSOD Posting Instructions sticky Create a Windows System Restore Point - Vista - START type rstrui - create a Driver Verifier - Windows 10, 8.1, 8, 7 & Vista (BSOD-related) restore point Windows - START type create select quot Create a Restore Point quot Windows - - Using Microsoft System Restore Windows HP Support Run the Driver Verifier - Code START type verifier make these selections - Select nd option - quot Create custom settings for code developers quot Select nd option - quot Select individual settings from a full list quot Check these boxes - Special Pool Pool Tracking Force IRQL checking Deadlock Detection Security Checks new as of Windows Concurrency Stress Test new as of Windows DDI compliance checking new as of Windows Miscellaneous Checks Select last option - quot Select driver names from a list quot Click on the Provider heading - sorts list by Provider Check ALL boxes where quot Microsoft quot IS NOT the Provider Click on Finish Re-boot IMPORTANT - PLEASE READ - If the Driver Verifier DV finds a violation it will result in a BSOD - After re-start you may not be able to log on to normal Windows Boot into SAFEMODE - tap the F key repeatedly during boot-up Select quot System Restore quot Choose the restore point that you created in step - For Driver Verifier status --- select last option st screen -or- --- type verifier query in a cmd DOS screen - To turn Driver Verifier off - verifier reset then re-boot - The Driver Verifier needs to run as long as possible - even if the status screen appears clear - All future BSOD dumps must be VERIFIER ENABLED MINIDUMPs - otherwise the dump s are of no use If your system does BSOD while the Driver Verifier is running please retrieve the dump file from c windows minidump zip it up amp attach to your next post About Driver Verifier Driver Verifer information -- gt driver verifier Windows Vista - Microsoft Search Driver Verifier issues within Vista Windows -- gt http support microsoft com default aspx verifier amp res Driver Verifier Special Pool Feature - http support microsoft com kb Using Driver Verifier to identify issues with Windows drivers for advanced users Memory dump options - http support microsoft com kb If you have any questions please send me a PM jcgriff

Relevancy 70.52%

I'm not gonna write anything about it here, but here's a link to microsoft.answers - > I've been writing there for 2 months now.

You can read about it here:
http://answers.microsoft.com/en-us/w...ge=3#LastReply

Today I ran Driver Verifier and it detected that the faulty driver is TVALZ_O.SYS which is TOSHIBA ACPI-Based Value Added Logical and General Purpose Device Driver..
Why are toshiba not upgrading their drivers ? I saw that windows 10 driver page last summer and it hasn't changed since then.. Same drivers are still there and nothing new, mostly TOSHIBA bloatware and CYBER... camera software, etc.. Nothing for Intel or NVIDIA or other important drivers.

https://forum.toshiba.eu/showthread.php?90099-Windows-10-TVALZ_O-SYS-BSOD-after-running-Driver-Verifier
Relevancy 70.52%

So I was previously receiving help within a different thread as I wasnt sure what was going on, you can see what was done in the thread here: http://www.bleepingcomputer.com/forums/t/598419/sluggish-response-times-computer-hanging-multiple-restarts-required/
 
After going thru the troubleshooting, i was prompted to update my nvidia driver,, which i did but then found photoshop was not recognizing my GPU, so I then realized PS needed an update, which I did. After updating and trying to open PS I twice in a row got a BSOD stating KERNEL_SECURITY_CHECK_FAILURE
 
I did some reading and decided it was most likely a driver issue so ran the driver verifier as instructed here on the BC forums and then restarted and atempted to run PS again, prompting another BSOD for which I have attached the log
 

 122115-33078-01.zip   90.86KB
  0 downloads

http://www.bleepingcomputer.com/forums/t/600113/driver-verifier-bsod-dump-log-continuous-issues-help-please/
Relevancy 70.52%

DRIVER VERIFIER If your BSODs are software related Driver Verifier can 7 Windows 8.1, related & 10, BSOD - Driver - Verifier Vista 8, help by Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista subjecting rd party drivers to a variety of stresses and tests to find improper behavior Driver Verifier monitors selected rd party kernel-mode drivers to detect illegal function calls or actions that might corrupt the system If Driver Verifier detects a violation it will flag disable the offending driver and force a BSOD The additional info added to the memory dump file will hopefully yield clues Create a Windows System Restore Point - Vista - START type rstrui - create a restore pointWindows amp - START type create select Create a Restore Point Windows - Swipe mouse top-right of screen to bring up Charms click on Search type create select Create a Restore Point Run Driver Verifier -- Windows amp Vista - START type verifier - Windows amp - Press WIN X keys select Command Prompt Admin type verifierMake these selections - Select nd option - Create custom settings for code developers Select nd option - Select individual settings from a full list Check these boxes - Special Pool Force IRQL checking Pool Tracking Deadlock Detection Security Checks new as of Windows Miscellaneous Checks Power framework delay fuzzing new as of Windows DDI compliance checking new as of Windows Select last option - Select driver names from a list Click on the Provider heading - sorts list by Provider Check ALL boxes where Microsoft IS NOT the Provider Click on Finish Re-boot If you are unable to boot into normal Windows after VERIFIER ENABLED BSOD - Spoiler p Boot into SAFEMODE - tap the F key repeatedly during boot-up Select System Restore Choose the restore point that you created in step span span span span span span li ul li ul To check Driver Verifier status - Spoiler --- select last option st screen -or- --- type verifier query in a cmd DOS screen - To turn Driver Verifier off - verifier reset then re-boot To VERIFY Driver Verifier SETTINGS - Spoiler --- type verifier querysettings in a cmd DOS screen - Driver Verifier needs to run for hours minimum - even if the status screen appears clear If a VERIFIER ENABLED BSOD occurs please get the dump file from c windows minidump zip it up amp attach to your next post Additional info from Windows Dev Center - Spoiler About Driver VerifierDriver Verifier OptionsUsing Driver VerifierMemory Dump Options Regards jcgriff

http://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/
Relevancy 70.52%

Have had problems with bluescreens and whocrashed told me it was most likely caused by some driver.
Turned on verifier after your guide and it crashed after I went to bed..

A:BSOD, computer idling with driver verifier running

Hi there!

Seems like the crashes are caused by netr28x.sys i.e. Ralink 802.11n Wireless Adapters. I would recommend to remove to and reinstall it. Then disable Driver Verifier.

Code:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aa830f, address which referenced memory

Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cff100
GetUlongFromAddress: unable to read from fffff80002cff1c0
0000000000000010 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlInsertEntryHashTable+73
fffff800`02aa830f 488b4810 mov rcx,qword ptr [rax+10h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0

TRAP_FRAME: fffff80000b9a290 -- (.trap 0xfffff80000b9a290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009286928 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aa830f rsp=fffff80000b9a420 rbp=fffff80000b9b238
r8=fffffa8007a2f3c0 r9=000000000000007f r10=000013f1cdf7d6bb
r11=000000000000ccbc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!RtlInsertEntryHashTable+0x73:
fffff800`02aa830f 488b4810 mov rcx,qword ptr [rax+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ac71a9 to fffff80002ac7c00

STACK_TEXT:
fffff800`00b9a148 fffff800`02ac71a9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9a150 fffff800`02ac5e20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`00b9b3d8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9a290 fffff800`02aa830f : fffffa80`08285070 00000000`00000000 00000000`00000003 00000000`0000000b : nt!KiPageFault+0x260
fffff800`00b9a420 fffff880`01778bc5 : fffff800`00b9b3d8 fffff880`01947980 fffff880`01947980 00000000`00000005 : nt!RtlInsertEntryHashTable+0x73
fffff800`00b9a470 fffff880`01778d13 : fffffa80`0a38bdb0 00000000`00000005 fffff880`0438c075 fffff880`04393eca : NETIO!KfdAleInsertFlowContextTable+0xb5
fffff800`00b9a4c0 fffff880`018491f5 : 00000000`00000000 fffff880`042fc001 00000000`00000002 00000000`00000007 : NETIO!KfdAleInitializeFlowTable+0x13
fffff800`00b9a4f0 fffff880`01848894 : fffff880`02da2110 fffff980`017f4310 fffffa80`0a38bdb0 00000000`00000000 : tcpip!WfpAlepAuthorizeReceive+0x7a5
fffff800`00b9ab20 fffff880`0184759c : 00000000`00000000 fffffa80`0000002c 00000000`00000000 fffffa80`094118e0 : tcpip!WfpAleAuthorizeReceive+0x584
fffff800`00b9ae00 fffff880`0187e78e : 00000000`00000000 fffff800`00b9b280 fffff800`00b9b338 00000000`00000000 : tcpip!WfpAleConnectAcceptIndicate+0x29c
fffff800`00b9aef0 fffff880`0188a27d : 00000000`00000002 fffff880`016af755 fffffa80`07a21ee0 fffff980`16e9ceb0 : tcpip!ProcessALEForTransportPacket+0x5fe
fffff800`00b9b160 fffff880`0187f70f : fffffa80`0a38bdb0 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!ProcessAleForNonTcpIn+0x1ad
fffff800`00b9b280 fffff880`01860891 : fffffa80`00000011 fffffa80`07c90002 fffffa80`07b875d4 00000000`00000004 : tcpip!WfpProcessInTransportStackIndication+0xb1f
fffff800`00b9b5f0 fffff880`01882f73 : fffffa80`07c976f0 fffffa80`07a74820 00000000`00000000 fffffa80`07b8f000 : tcpip!InetInspectReceiveDatagram+0... Read more

http://www.sevenforums.com/bsod-help-support/296826-bsod-computer-idling-driver-verifier-running.html
Relevancy 70.52%

I need help with this, can't quite figure out the problem. It's really... odd. In addition to other minor system problems in this brand new build, I have a somewhat recurring driver crash related to the common Driver Verifier problem. I can't find the driver myself, so I don't know which one or ones it may be. In addition, the crash most frequently occurs when using AIDA64/Everest to check my motherboard's specs. I can view most of it, including the hardware set-up, but clicking 'BIOS' or 'ACPI' to check those parts causes an instant crash. I don't know if this is normal.


I'm not so much versed in drivers or Driver Verifier, so before I did anything I wanted to come here. Also, I tried to upload my SF data correctly, let me know if you need anything else, or if I made a mistake. Thanks for taking a look.

A:Driver Verifier BSoD on checking BIOS, 0x000000C4

First, Disable Driver Verifier.
Driver Verifier - Enable and Disable

Then uninstall AIDA64 Extreme Edition

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {83, 99bc018, 2c, 99bc}

*** WARNING: Unable to verify timestamp for kerneld.x64
*** ERROR: Module load completed but symbols could not be loaded for kerneld.x64
Probably caused by : kerneld.x64 ( kerneld+218d )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000083, MmMapIoSpace called to map, but the caller hasn't locked down the MDL pages.
Arg2: 00000000099bc018, Starting physical address to map.
Arg3: 000000000000002c, Number of bytes to map.
Arg4: 00000000000099bc, The first page frame number that isn't locked down.

Debugging Details:
------------------
BUGCHECK_STR: 0xc4_83

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: aida64.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000356d3dc to fffff800030e6fc0

STACK_TEXT:
fffff880`04a2c3b8 fffff800`0356d3dc : 00000000`000000c4 00000000`00000083 00000000`099bc018 00000000`0000002c : nt!KeBugCheckEx
fffff880`04a2c3c0 fffff800`0356dc53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`04a2c400 fffff800`0357e9a6 : 00000000`099bc018 00000000`00000000 00000000`00000002 00000000`00000000 : nt!MmCheckMapIoSpace+0xe3
fffff880`04a2c450 fffff880`0848418d : 00000000`099bc018 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierMmMapIoSpace+0x46
fffff880`04a2c490 00000000`099bc018 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kerneld+0x218d
fffff880`04a2c498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x99bc018
STACK_COMMAND: kb

FOLLOWUP_IP:
kerneld+218d
fffff880`0848418d ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: kerneld+218d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: kerneld

IMAGE_NAME: kerneld.x64

DEBUG_FLR_IMAGE_TIMESTAMP: 508d112b

FAILURE_BUCKET_ID: X64_0xc4_83_VRF_kerneld+218d

BUCKET_ID: X64_0xc4_83_VRF_kerneld+218d

Followup: MachineOwner
---------

1: kd> lmvm kerneld
start end module name
fffff880`08482000 fffff880`0848d000 kerneld T (no symbols)
Loaded symbol image file: kerneld.x64
Image path: \??\C:\Program Files (x86)\AIDA64 Extreme\kerneld.x64
Image name: kerneld.x64
Timestamp: Sun Oct 28 16:34:11 2012 (508D112B)
CheckSum: 0000AF16
ImageSize: 0000B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Let us know the results.

http://www.sevenforums.com/bsod-help-support/261608-driver-verifier-bsod-checking-bios-0x000000c4.html
Relevancy 70.52%

Hi,

I am haunted by BSOD for some months now (approx 1-2 per week). They mostly occur during some RAM intensive things (videos, skype, image processing, antivirus check). I am pretty sure it is memory and/or driver related. I unsucessfully tried various things to fix it yet:

- Changed Ram, run memtest86 for 10h+. Everything ok.
- Checked Ram Voltage. No change.
- Reinstalled Windows7. No change, they quickly returned.
- Changed Antivirus Software. Checked for Malware. Ok
- Updated several Drivers, including graphic card driver

Now I run Driver Verifier and just got a Bluescreen. However, I am not able to completly understand which driver caused it. The latest Bluescreen has these information. Please help me to understand it.

Best Regards,
Zodurac

A:BSOD Created Minidump with Driver Verifier. Need help to read it.

Hi Zodurac.

This issue is not seeming to be a driver related one.

Code:
BugCheck C4, {13e, fffff98059e10fd0, fffff98099e10fd0, fffffa8009a9dc80}

Probably caused by : Npfs.SYS ( Npfs!NpRemoveDataQueueEntry+a5 )
But something interesting is there about your RAMs.

Code:
Size 4096MB
Form Factor 09h - DIMM
Device Locator DIMM4
Bank Locator BANK3
Speed 0MHz
Manufacturer Manufacturer03

Code:
Size 2048MB
Form Factor 09h - DIMM
Device Locator DIMM3
Bank Locator BANK2
Speed 0MHz
Manufacturer Manufacturer02

Code:
Size 2048MB
Device Set [None]
Device Locator DIMM1
Bank Locator BANK0
Speed 0MHz
Manufacturer Manufacturer00
You have two different types of RAM?

Can you keep the 4 GB one only, remove both the 2 GB sticks and see what happens?

Another thing is the RAM speed .... 0MHz! I am astonished .... but I am not able to explain it. I will request essenbe to comment on it.

http://www.sevenforums.com/bsod-help-support/334936-bsod-created-minidump-driver-verifier-need-help-read.html
Relevancy 70.09%

Yesterday i popped in my motherboard cd and installed asus suite II and reinstalled the Renesas usb drivers Updated my BIOS to a more recent version and raised my ram speed BSOD PFN_LIST_CORRUPT Driver BSOD, Verifier from to mhz 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 quot 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 quot 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 pqnice kzf m pxgb 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.

http://www.sevenforums.com/bsod-help-support/334810-pfn_list_corrupt-bsod-driver-verifier-bsod.html
Relevancy 69.66%

Hi running Windows bit home premium Enabled driver verifier as I was getting BSOD cannot boot into Windows because of the STOP error x A IRQL not less or equal have loaded system defaults and still no joy AMD T X with GB x Gb of crucial tactical tracer elite RAM SPD at Mhz V - - - - -jedec GTX SOC and HDD'S TB boot drive Western Digital Caviar Seagate ST Gb and maxtor gb 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 After cannot enabling driver boot BSOD 0x0000000A verifier, windows to do with a usb ew filter as I recall Dongle has been removed XBOX 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 xfffff ff x x xfffff e ae Am sure I can get back into windows with system restore disc but am BSOD 0x0000000A After enabling driver verifier, cannot boot windows 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

http://www.sevenforums.com/bsod-help-support/270905-bsod-0x0000000a-after-enabling-driver-verifier-cannot-boot-windows.html
Relevancy 69.66%

Hi Everyone,

I have started playing dark souls 2, and after 5 minutes of game play I get BSOD saying - "driver verify detected violation" . I have failed to verify the problem can someone please help?

I have attached the mini dump here:

https://www.dropbox.com/s/s8h0ng3g5o...14-7500-01.dmp

My PC:

CPU: i5 750
Motherboard: p55-ud3l
Memory: 1600 2x4 G.Skill
Graphic card: saphire 7950 vapor-x
SSD: intel 120GB 520 + crusial 256GB M4
HD: 2 sata hard drives
mouse: Roccat kone XTD
keyboard: Roccat Isku
Thanks!

A:BSOD playing darksouls2 driver verifier detected violation

I am not any type of expert on dump files, but I see some things that might be relevant. First, you can see the kernel is watching a driver, but does not specify which one.






DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000000
Arg3: ffffe00134722880
Arg4: 0000000000000000



The drivers below are from 2010, but because they are old doesn't necessarily mean they are causing a problem. You might check and see if you can find an update for them.

What is interesting is the Trixx.sys driver shows as located in your user folder and not in the Windows\System32\drivers folder. Not sure what happened, but if this is an older program, you may have needed to install it in some type of compatibility mode. It looks like the trixx.sys file is related to the Sapphire Video card, so the others might be also. You might check for drivers for the card to see if any new ones are available.


Image path: \??\C:\Users\YourUser\AppData\Local\Temp\TRIXX.sys
Image name: TRIXX.sys
Timestamp: Wed Oct 06 11:14:37 2010 (4CACA06D)
CheckSum: 000101C9
ImageSize: 0000C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Image path: \SystemRoot\System32\drivers\mvxxmm.sys
Image name: mvxxmm.sys
Browse all global symbols functions data
Timestamp: Wed Mar 17 02:52:37 2010 (4BA08A45)
CheckSum: 0000EA9D
ImageSize: 00008000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Image path: \SystemRoot\System32\drivers\mv91xx.sys
Image name: mv91xx.sys
Browse all global symbols functions data
Timestamp: Wed Mar 17 02:53:06 2010 (4BA08A62)
CheckSum: 0005315F
ImageSize: 0008D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

http://www.eightforums.com/bsod-crashes-debugging/45352-bsod-playing-darksouls2-driver-verifier-detected-violation.html
Relevancy 69.66%

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.

http://www.sevenforums.com/bsod-help-support/368784-bsod-every-time-windows-starts-driver-verifier-enabled.html
Relevancy 69.66%

Hi everyone Sorry for my english im not the best at languages So here is my problem ive just bought an inspirion laptop and after the driver updates it starts to get BSOD's attached I have no idea what cause the problem but last time ive run the program called driver verifier so the last dmp file is caused by that i think so I guess you have enough information but if you need more information i will give answer as soon as possible Here is my laptop Processor Intel CoreTM driver .dmp the files, verifier is with after BSOD last (attached installing thr win7 i - QM GHz MB cache Processor GHz Turbo upto GHz Qual Core Threads M Cache Memory GB Shared Single Channel DDR Memory Chipset Mobile Intel Series Express Chipset Video Card Dual Graphic Card Integrated MB Intel HD MB NVIDIA GeForce GT M Display inch display x Audio and Speakers SRS Premium Sound - speakers W each Built-in microphone Hard Drive GB SATA hard drive RPM Optical Drive Internal tray-load DVD -RW Power -cell WHr Li-Ion Battery Camera MP Integrated x native HD BSOD after installing win7 (attached thr .dmp files, the last is with driver verifier Webcam Wireless Wi-Fi Options BSOD after installing win7 (attached thr .dmp files, the last is with driver verifier Wi-Fi Bluetooth Options Intel Centrino Wireless-N x bgn Bluetooth WiMax Options Intel Centrino Wireless-N WiMAX x bgn WiMax Ports Slots amp Chassis Externally Accessible USB USB USB with E-SATA amp Power Share HDMI v Port VGA Port Integrated network connector LAN RJ AC adapter connector Audio jacks -line out Mic-in -in- Media Card Reader Digital SD Memory Card Secure Digital Extended Capacity SDXC Secure Digital High Capacity SDHC Multi Media Card MMC MultiMedia Card plus MMC Memory Stick MS Memory Stick PRO MS Pro I would like to thank everybody who has read this and please help me

A:BSOD after installing win7 (attached thr .dmp files, the last is with driver verifier

i had a new one here is it:

http://www.techsupportforum.com/forums/f217/bsod-after-installing-win7-attached-thr-dmp-files-the-last-is-with-driver-verifier-645540.html
Relevancy 69.66%

Hi everyone Sorry for my english im not the after driver with verifier) installing (attached files BSOD last .dmp is the the win7 best at languages So here is my problem ive just bought an inspirion laptop and after the driver BSOD after installing win7 (attached the .dmp files the last is with driver verifier) updates it starts to get BSOD's attached I have no idea what cause the problem but last BSOD after installing win7 (attached the .dmp files the last is with driver verifier) time ive run the program called driver verifier so the last dmp file is caused by that i think so I guess you have enough information but if you need more information i will give answer as soon as possible Here is my laptop Code Processor Intel CoreTM i - QM GHz MB cache Processor GHz Turbo upto GHz Qual Core Threads M Cache Memory GB Shared Single Channel DDR Memory Chipset Mobile Intel Series Express Chipset Video Card Dual Graphic Card Integrated MB Intel HD MB NVIDIA GeForce GT M Display inch display x Audio and Speakers SRS Premium Sound - speakers W each Built-in microphone Hard Drive GB SATA hard drive RPM Optical Drive Internal tray-load DVD -RW Power -cell WHr Li-Ion Battery Camera MP Integrated x native HD Webcam Wireless Wi-Fi Options Wi-Fi Bluetooth Options Intel Centrino Wireless-N x bgn Bluetooth WiMax Options Intel Centrino Wireless-N WiMAX x bgn WiMax Ports Slots amp Chassis Externally Accessible USB USB USB with E-SATA amp Power Share HDMI v Port VGA Port Integrated network connector LAN RJ AC adapter connector Audio jacks -line out Mic-in -in- Media Card Reader Digital SD Memory Card Secure Digital Extended Capacity SDXC Secure Digital High Capacity SDHC Multi Media Card MMC MultiMedia Card plus MMC Memory Stick MS Memory Stick PRO MS Pro I would like to thank everybody who has read this and please help me

A:BSOD after installing win7 (attached the .dmp files the last is with driver verifier)

Is it a brand new laptop?

http://www.techsupportforum.com/forums/f299/bsod-after-installing-win7-attached-the-dmp-files-the-last-is-with-driver-verifier-645542.html
Relevancy 69.66%

Hi there.

I'm struggeling with an issue on my machine and hopefully someone can help me. I get sometimes a BSOD after I quitted a game, mostly when it is high end (e.g. Bioshock infinite). I activated then Driver Verifier to search for the source of the problem, got a bluescreen after 1 minute with a reference to HIDCLASS.SYS.

Gathered dump files are attached to this post. Thanks alot.

A:BSOD when quitting a heavy load game / Driver Verifier

This situation is interesting, because it behaved like driver verifier is enabled even before you enabled DV yourself.

Code:
BugCheck C4, {91, 2, fffff80003660cc0, 0}

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

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80003660cc0
Arg4: 0000000000000000

Debugging Details:
------------------
BUGCHECK_STR: 0xc4_91

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0

LAST_CONTROL_TRANSFER: from fffff8000352d5ba to fffff800034d6c40
Two red lines indicate that DV is enabled. The blue line makes it sure that DV was not enabled. Then why it may occur? Most probable reason is a driver bug. And the green line indicates that there is a driver bug. What is to do in such a situation? First of all, better you shift to an older driver version, which is stable and bug free in the best of my knowledge.
Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
If it says the the free version of Driver Fusion cannot remove all the elements, stop there and follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.
If the stop 0xC4 continues with this version too, we will think it differently in the next time.

Now coming to the DV enabled HIDCLASS.sys BSODs.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {224, fffff88006cba710, fffff9802960a750, ffffffffc00000bb}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

Followup: MachineOwner
---------
Hidclass.sys is the OS element, so it cannot be the real reason behind the crash. But it is keyboard/mouse related. So better you try to update these drivers:

DRIVERNAMELOCATIONlgbusenum Logitech GamePanel Virtual Bus Enumerator Driver c:\windows\system32\drivers\lgbusenum.sys Kerneltreiberlgshidfilt Logitech Gaming KMDF HID Filter Driver c:\windows\system32\drivers\lgshidfilt.sys Kerneltreiber Jalgvirhid Logitech Gamepanel Virtual HID Device Driver c:\windows\system32\drivers... Read more

http://www.sevenforums.com/bsod-help-support/284753-bsod-when-quitting-heavy-load-game-driver-verifier.html
Relevancy 69.66%

Hello there On my freshly installed Windows notebook I am still having random Starcraft crashes maybe once application crashing Verifier attempt to BSOD Driver - from solve a week or two As part of the attempt to figure out what is causing this I have run the Windows built-in Driver Verifier Driver Verifier - Enable and Disable I am not even able to boot into Windows itself after consecutive BSODs and accompanying reboots After disabling Driver Verifier in safe mode I am able to attach the results extracted from the SF Diagnostic Tool Some other information that may be applicable to my situation - Windows Memory Diagnostic passes no problems - Windows is not tweaked in any way - msconfig ccleaner services etc - CPU GPU temps are normal acceptable - under SC GPU is C CPU C - However the Intel HM chip is C under load and C while surfing watching video There is no heatsink on this chip - Short tests by Seagate SeaTools all pass have not run the long tests - Running Error Scan in HD Tune also didn't show any errors - According to SMART I do have BSOD from Driver Verifier - attempt to solve crashing application End-to-End Errors value is from what I've read this may or may not mean anything Could these errors register due to the HD not having optimal physical connection I noticed overnight the computer was acting sluggish with low IO performance which turned out to be a physical connection issue - just had the slide the HD back in a bit TIA for any help

A:BSOD from Driver Verifier - attempt to solve crashing application

It indicates to Daemon tools.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88004349324, fffff980075fce10, 0}

*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

Followup: MachineOwner
---------
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
Double click to open it.
Click this button only:

If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Now disable Driver Verifier. Run it only when it is needed.

If the BSODs continue, let us know. We will try to find if Intel ATA/ATAPI Controller is really causing any problem or not. Otherwise we will decide that SPTD was making it fail.

http://www.sevenforums.com/bsod-help-support/288559-bsod-driver-verifier-attempt-solve-crashing-application.html
Relevancy 69.66%

Hello I have been experiencing lots of BSODs lately all at random and all showing BSOD Driver while running Verifier, probable reason netbt.sys different reasons At first I thought that I had a memory problem - so I removed one BSOD while running Driver Verifier, probable reason netbt.sys of the RAM modules and the laptop worked OK for a few days However today the BSODs started again I ran Driver Verifier for a few hours and started getting BSOD after BSOD I checked the minidump and from what I saw the reason is probably netbt sys Dump File - - dmp Crash Time PM Bug Check String DRIVER CORRUPTED EXPOOL Bug Check Code x c Parameter fffffa e Parameter Parameter Parameter fffff b d Caused By Driver netbt sys Caused By Address netbt sys bf File Description Product Name Company File Version Processor x Crash Address ntoskrnl exe Stack Address Stack Address Stack Address Computer Name Full Path C Windows Minidump - - dmp Processors Count Major Version Minor Version Dump File Size Before running Driver Verifier I was getting a BAD POOL HEADER x BSODs I'm running Windows Home Premium x on a Toshiba Qosmio X laptop The OS is OEM I have also attached the jcgriff perfmon reports and the minidump txt export just in case Thanks in advance for all the help you can provide me with -

A:BSOD while running Driver Verifier, probable reason netbt.sys

I am not seeing the .dmp files in the files you have attached. Please attach that file also.

http://www.sevenforums.com/bsod-help-support/241423-bsod-while-running-driver-verifier-probable-reason-netbt-sys.html
Relevancy 69.66%

I began having startup problems leading to a BSOD. When I ran driver verifier, It repeatedly crashed upon reboot and I had to disable verifier in safe mode to boot. The error seemed to be with ntsokrnlpa.exe and HIDCLASS.sys This was after a reinstall (W7 Pro x86 w/ SP1) Stop code: 0x000000c9 (0x00000220, 0x9237FA8C, 0x9B13CE00, 0x8AD70030) The IO Manager has detected a violation by a driver that is being verified. The faulty driver that is being verified must be debugged and replaced with a working version: Dump files attached. Thanks for your help!

A:BSOD driver verifier error 0x000000c9 IO Manager Violation

There is no dump file in your upload
Dump Files - Configure Windows to Create on BSOD

http://www.sevenforums.com/bsod-help-support/275072-bsod-driver-verifier-error-0x000000c9-io-manager-violation.html
Relevancy 69.66%

Happy post-thanksgiving!

I am home trying to help my dad fix his computer. Windows 7. BSOD has come with errors including: Memory_management; IRQL_NOT_LESS_OR_EQUAL; and Bad_Pool_Header.

Computer will run normally and will BSOD after three or four hours. It will need to be restarted multiple times, until it will successfully load to desktop, only to BSOD again three or four hours later.

Used windows memory test. No problems detected.

Driver verifier (verifying third-party apps) was running on the last two dumps.


All dumps are uploaded. Specifically, please look at the dumps from today and yesterday. Any suggestions or help would be much appreciated. Thank you!!!

A:BSOD - Memory Management and more - Driver Verifier Running - Dumps UL

I have uploaded another zip which includes:

1. A perfmon report. The perfmon report states that the computer failed Hardware Drive and Driver checks and System Service checks. Not sure how to read it but there was a number of failures.

2. systeminfo

3. Hosts

4. Driverlist

5. Eventsys

6. Eventapp

7. Windowsupdate and

8. The BSOD dumps
Hope this info helps. Let me know if you need anymore info and I will gladly supply...I'm willing to try anything as I'm not sure what to do next...

Thank you!

http://www.sevenforums.com/bsod-help-support/353648-bsod-memory-management-more-driver-verifier-running-dumps-ul.html
Relevancy 69.66%

First of all I would like to apologize for my bad english it is not my native language I really need help Hi I've been using ubuntu for almost years so a few months ago I decided to install windows mostly for gaming since the first week my pc just lock up freeze at random times also do a buzzy sound from the speakers I did a clean install again but didn't work I've tried installing windows as well but it still freezes Already tried updating drivers using differents softwares like driver booster or slimdrivers scans for viruses spyware malware updating the BIOS repairing the registry checking the CPU and GPU temps which are good so it's not overheating also run memtest for about hours did using Random freezes driver for verifier BSOD's) sound(even with buzzy passes and without a single error and Random freezes with buzzy sound(even using driver verifier for BSOD's) NOTHING WORK I decided to use driver verifier looking for a bad driver or something like Random freezes with buzzy sound(even using driver verifier for BSOD's) that but the pc still freeze and didn't show up any BSOD's So I really don't know what to do know Using ubuntu NEVER got me a freeze or crash that's why I believe it's a software issue system specs CPU AMD fx six core GPU Nvidia gt gb DDR Memory GB DDR gb gb Kingston Motherboard A M-A DELUXE SO Windows ultimate x I need help

http://www.sevenforums.com/bsod-help-support/386135-random-freezes-buzzy-sound-even-using-driver-verifier-bsods.html
Relevancy 69.66%

Hello everyone I am getting lost trying to troubleshoot my BSOD problem myself I sincerely thank you for your help in advance All my knowledge is from Google searches please assume I know nothing regarding IT Summary of History Jan this year generated verifier BSOD, driver crashes used random multiple and Bought laptop Sager NP with a Samsung EVO M SSD GB HDD chose Windows professional bit as my OS installed on above m SSD For random BSOD, used driver verifier and multiple crashes generated personal use gaming websurf media email etc Started getting random BSOD during normal everyday use no detectable pattern and times My then current guesses-- possible sound driver clash w Sound Blaster Cinema and Realtek audio since opening laptop I've had unresponsive issues with SB Cinema Tried uninstalling SB Cinema but I'm random BSOD, used driver verifier and multiple crashes generated unable to error unable to Also issue with losing sound when resuming from hibernate sleep March th Decided to clean install with prepackaged drivers and OS disc Did not install SB Cinama All seemed well except still getting no sound after resuming from hibernate sleep-- realized if I go into sleep again and resume sound will come back April th hit with first BSOD after clean install then subsequent random BSOD next few days see below screenshot of bluescreenview BSOD crashtimes Sometimes during these few months Ran SFC config results normal I also did run a HDD check through Windows and no errors Also ran standard Windows Memory Diagnostic results normal Yesterday ran hrs passes of Memtest errors Also ran pass of Memtest errors Today Ran Driver Verifier using this tutorial and all sorts of problems arose-- Most or all of the logged crashes are from shutting down improper shutdown during my restarts and I wouldn't even get an actual bluescreen it just resets Also while Driver Verifier was on computer would be very sluggish Internet connectivity would be very sluggish Firefox would crash multiple times My wireless mouse would stop responding suddenly I'd have to use touchpad After each crash I would look at BlueScreenView and try to Google the Bug Check String stop error code and also the driver causing issue but I fail at finding the solution as I don't know how to figure out the pattern Below is a screenshot of my BlueScreenView And here is my log file DEOWBA-Thu zip Again your help is greatly appreciated

http://www.sevenforums.com/bsod-help-support/395085-random-bsod-used-driver-verifier-multiple-crashes-generated.html
Relevancy 69.66%

Hello Right now I BSOD: Fault ?? Hardware am trying my best to keep my laptop running while I am posting this thread I have been victimized by relentless blue screens which I suspect is a result of some hardware problem I initially thought this was a Windows and or Virus problem BSOD: Hardware Fault ?? I posted a thread as well http forums techguy org virus-oth -extreme-system-slowdown-blue-screens htm l but I recently formatted and reinstalled Windows but the blue screens keep coming back I am using IBM Thinkpad R a model so pretty old by now It runs Intel Centrino GHz proc GB IDE hard disk it initially came with MB RAM but I upgraded it to GB Windows XP SP Here are the problems I am facing since last one month Extreme system slowdown while running two or MS Office files or Outlook or even two tabs on Google Chrome The mouse pointer tends to get stuck while moving on the screen as if my system is busy even when Task manager shows system usage between to times I face a slowdown I end up with a blue screen it mostly says something like A critical process thread has been stopped to stop further damage and a few error codes are X F X X A F DA X A C C X A CB C though the error codes change every time Also at times I get a blue screen while boot up that says Unmountable Disk and while running Windows I see Unknown Hard Error I showed my laptop to someone and he predicted that the MB RAM was causing the trouble and took it out but it still did not solve the problem The problem occurs instantly if I move my laptop from my desk to another location i e the moment I move it I get a blue screen I did run a memtest and it returned no errors Can anyone please help me figure out what s the problem I am living with it for more than a month now and its frustrating Thanks nbsp

A:BSOD: Hardware Fault ??

If moving it causes that kind of issue - I'd be looking at loose connections. DVD drive connection, AC adapter connections, Hard Drive connections.
 

https://forums.techguy.org/threads/bsod-hardware-fault.949929/
Relevancy 69.23%

I am getting BSOD at random times although I think I get them more when I'm watching videos on Driver and only drivers Verifier instal (clean fails Microsoft BSOD on VLC a lot of times VLC will just crash other times it will BSOD I also get BSOD while doing other things as well BSOD and Driver Verifier only fails on Microsoft drivers (clean instal as crashes on other apps like Firefox as well I also recently replaced my HDD to a SSD because the HDD started giving SMART warning however I'm still getting BSOD app crashes I looked online at the BSOD error messages and decided to try the Driver Verifier tool When I run with only non-Microsoft drivers nothing happen still got one crash but I think it was just a normal random crash However when I ran verifier with BSOD and Driver Verifier only fails on Microsoft drivers (clean instal only Microsoft drivers I can't BSOD and Driver Verifier only fails on Microsoft drivers (clean instal boot I will BSOD right after my Asus logo and the error will say DRIVER VERIFIER DETECTED VIOLATION Some of the BSOD crash errors I've gotten SYSTEM SERVICE EXCEPTION -- gt ntoskrnl exe DRIVER IRQL NOT LESS OR EQUAL -- gt ntoskrnl exe BAD POOL HEADER -- gt ntoskrnl exe I got driver irql not less or equal three times in the past few days and bad pool header twice I also have an entry on BlueScreenView that is blank under quot Bug Check String quot but points to driver ndis sys Things I have tried sfc scannow Memtest passes Replaced HDD to SDD LinX Around minutes Heaven Benchmark Around minutes Swap RAM slots this is a laptop and I only have RAM piece Reinstall Windows Could it be RAM problem Memtest did not run long enough errors so far Motherboard problem Windows incompatible When I purchased this laptop years ago it came with Windows DM Log Collector was giving me empty zip files so I used SF Diagnostic Tools instead Please let me know if it is missing any files memory dmg mb debug-AsusPC zip

A:BSOD and Driver Verifier only fails on Microsoft drivers (clean instal

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Code:
Service KMSELDI Service KMSELDI c:\program files\kmspico\service_kms.exe
Start Menu\Programs\KMSpico Public:Start Menu\Programs\KMSpico Public

Forum rules





4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

http://www.tenforums.com/bsod-crashes-debugging/54633-bsod-driver-verifier-only-fails-microsoft-drivers-clean-instal.html
Relevancy 68.8%

HI THERE i'm really disappointed i got blue screen amp blue screen error several time a day since MONTHS I loaded WINDBG to BSOD FAULT disk SRV.SYS & IN WITH hardware read my last BSOD there were'nt same i mean this is the Code Bugcheck Analysis Use analyze -v to get detailed debugging information BugCheck F fffffa b fffffa b fffff dc d Probably caused by hardware disk Followup MachineOwner --------- kd gt BSOD WITH SRV.SYS & hardware disk IN FAULT analyze -v Bugcheck Analysis CRITICAL OBJECT TERMINATION f A process or thread crucial to BSOD WITH SRV.SYS & hardware disk IN FAULT system operation has unexpectedly exited or been terminated Several processes and threads are necessary for the operation of the system when they are terminated for any reason the system can no longer function Arguments Arg Process Arg fffffa b Terminating object Arg fffffa b Process image file name BSOD WITH SRV.SYS & hardware disk IN FAULT Arg fffff dc d Explanatory message ascii Debugging Details ------------------ PROCESS OBJECT fffffa b IMAGE NAME hardware disk DEBUG FLR IMAGE TIMESTAMP FAULTING MODULE PROCESS NAME csrss exe EXCEPTION RECORD fffff c b -- exr xfffff c b ExceptionAddress e f ExceptionCode c In-page I O error ExceptionFlags NumberParameters Parameter Parameter fefd fd a Parameter c e Inpage operation failed at fefd fd a due to I O error c e EXCEPTION CODE NTSTATUS xc - L CUSTOMER CRASH COUNT DEFAULT BUCKET ID VISTA DRIVER FAULT CURRENT IRQL ERROR CODE NTSTATUS xc - L EXCEPTION PARAMETER EXCEPTION PARAMETER fefd fd a EXCEPTION PARAMETER c e IO ERROR NTSTATUS xc e - Un p riph rique qui n EXCEPTION STR xc c e FAULTING IP a e f BUGCHECK STR xF IOERR C E FOLLOWUP IP a fe fd fd a FOLLOWUP NAME MachineOwner MODULE NAME hardware disk STACK COMMAND kb FAILURE BUCKET ID X xF IOERR C E IMAGE hardware disk BUCKET ID X xF IOERR C E IMAGE hardware disk Followup MachineOwner --------- kd gt analyze -v And the Second Code Bugcheck Analysis Use analyze -v to get detailed debugging information BugCheck A fffff fc f ffffffffc e b fffff eed Probably caused by srv sys srv TerminateServer Followup MachineOwner --------- kd gt analyze -v Bugcheck Analysis KERNEL DATA INPAGE ERROR a The requested page of kernel data could not be read in Typically caused by a bad block in the paging file or disk controller error Also see KERNEL STACK INPAGE ERROR If the error status is xC E xC C xC D or xC it means the disk subsystem has experienced a failure If the error status is xC A then it means the request failed because a filesystem failed to make forward progress Arguments Arg fffff fc f lock type that was held value or PTE address Arg ffffffffc e error status normally i o status code Arg b current process virtual address for lock type or PTE Arg fffff eed virtual address that could not be in-paged or PTE contents if arg is a PTE address Debugging Details ------------------ ERROR CODE NTSTATUS xc e - Un p riph rique qui n DISK HARDWARE ERROR There was error with disk hardware BUGCHECK STR x a c e CUSTOMER CRASH COUNT DEFAULT BUCKET ID VISTA DRIVER FAULT PROCESS NAME System CURRENT IRQL TRAP FRAME fffff bd -- trap xfffff bd NOTE The trap frame does not contain all registers Some register values may be zeroed or incorrect rax ff b rbx rcx fffff a d b rdx fffffa d eb rsi rdi rip fffff eed rsp fffff bd e rbp r r r fffffa d r r r r r iopl nv up ei ng nz ac po cy srv SrvCloseShare fffff eed fff push rbx Resetting default scope LAST CONTROL TRANSFER from fffff afa to fffff a STACK TEXT fffff bd fffff afa a fffff fc f ffffffff c e b nt KeBugCheckEx fffff bd fffff a b fffffa e fffff bd b fffff c fffff b nt FNODOBFM string' x c e fffff bd fffff aa c ffffffff ffffffff nt MiIssueHardFault x b fffff bd f fffff a e fffff a d b fffff a d b nt MmAccessFault x c fffff bd fffff eed fffff f e fffff a fffff a b fffff a d b nt KiPageFault x e fffff bd e fffff f e fffff a fffff a b fffff a d b f srv SrvCloseShare fffff bd f fffff f e fffffa b f df fffff c a f fffffa d ... Read more

A:BSOD WITH SRV.SYS & hardware disk IN FAULT

Oh, you're not dead yet

Hello and welcome to TSF.

At a glance, it looks like you're having some problems with memory management. Please follow the instructions here: http://www.techsupportforum.com/foru...ns-452654.html

http://www.techsupportforum.com/forums/f299/bsod-with-srv-sys-and-hardware-disk-in-fault-553145.html
Relevancy 67.51%

Hey this is my first time posting here but I'm familiar with BSOD's fault. hardware during Windows bootup, suspecting forums and such Well I might as well describe my problem I have a HP Pavilion dv ca laptop running Windows Vista Home Premium CPU AMD Turion X GHz Graphics Card NVIDIA GeForce Go M RAM Gb DDR Well Windows BSOD's during bootup, suspecting hardware fault. this all started out a few weeks ago I was busy doing my normal stuff browsing the web talking to my friends on Skype and listening to music in iTunes when I get a notification for an update to bring iTunes up to I did the update and the process went smoothly But then things started to go horribly wrong for me During the reboot sequence Vista blue screened and went into autorestart Unfortunately I was unable to make out what the message said During POST everything was fine but when Vista tried to boot up I chose start Windows Normally when it gave me the option to it blue screened yet again during this bootup and restarted So in a rut I quickly hit f and managed to get into boot options Naturally I tried to get into safe mode BUT that's when things started to get weird It tried to boot but I got absolutely no GUI at all Explorer exe somehow didn't load up properly or anything My mouse was working as the pointer was up and I could move it around and everything but behind it was just a black screen Nothing else at all Frustrated I hard rebooted and did a system restore BUT during the restore I chose a restore point that was set the day before it gave me a message saying that the restore point could not be used please use another one That was an odd one So I fiddled around with the different restore points until I found a good one that was set before the iTunes install But then this is when things got really weird Windows finally managed to boot properly and I could get into my desktop But then I noticed that the internet wasn't connecting I tried to connect manually but Windows kept saying that the dependency group service could not be started This was getting a little odd So I tried to start it manually by going into My Computer BUT when I tried to do that Windows told me that it couldn't start it up at all and then afterwards I got BSOD' yet again Frustrated and going through a horrible anxiety attack my schoolwork and personal files are on this laptop here and I'm not one for backing up on a regular basis I tried doing another system restore THIS time it seemed to have worked out ok cause now the services had managed to get working again I'm typing this up right now on said laptop because everything's stable at the moment However I'm suspecting that Windows won't boot up right if I do a restart and go through the whole cycle yet again leaving me in an anxious mess Since I have no idea where the BSOD report dump is I checked the reliability monitor and it gave me this http i photobucket com albums a ityReport jpg - Part http i photobucket com albums a ityReport jpg - Part http i photobucket com albums a ityReport jpg - Part http i photobucket com albums a ityReport jpg - Part So finally my question is what just happened How did iTunes do this DID iTunes do this Is my computer still properly stable Is a Vista reinstall in my future I need some help making sense out of my situation I appreciate you guys taking the time to read this

A:Windows BSOD's during bootup, suspecting hardware fault.

UPDATE: A friend of mine that's CompTIA A+ Certified took a look at the computer finally and ran some memtests; turns out that there was a bad stick of RAM that was doing this. I'm grabbing another 1 gig stick during the weekend, so that'll be fine now.

This topic can now be closed. :)

http://www.techsupportforum.com/forums/f299/windows-bsods-during-bootup-suspecting-hardware-fault-309627.html
Relevancy 66.65%

Hi The problem is a mix of BSOD s and freezes I only noticed the error message on the BSOD a couple of times which was quot page fault in non-paged area quot with a reference to the file win k sys It then started a memory dump and rebooted on completion Attached is the minidump file and and in fault with install Page hardware new BSOD area non-paged a txt document with the error codes The machine is new I built it last September - specs below with Page fault in non-paged area BSOD with new install and hardware Vista -bit SP It had been running absolutely fine since a week ago when I swapped my old Seagate hard drive out and put in the current drives and installed them in RAID Initially I thought that it was the RAID config or drivers and have since done several Page fault in non-paged area BSOD with new install and hardware reinstalls However same probs kept occurring I was Page fault in non-paged area BSOD with new install and hardware also worried that my system might be underpowered and that the nd hd was just slightly too much I ve consequently also reinstalled everything on one of the hard drives and disconnected the other as it is now but still the same problems I can t help feeling that it s hardware-related and am on the verge of buying a higher-powered PSU I ve run Memtest a couple of times to coverage no errors Have Kaspersky Internet Security installed fully updated and nothing detected just now after a full scan Hope you can help Am desperately trying to do my work on this machine Thanks Specs Asus P Q motherboard Intel C D E stock Geil Black Dragon GB MHz dual channel Powercolor HD PCS Mb x GB Seagate currently x DVDRW Corsair VX W several fans EDIT Another crash just now but this time the screen went haywire with lots of colours and lines - no BSOD or anything else Wasn t doing anything stressful just IE Could the video card be damaged Had the processor running lightly overclocked before Christmas and tried it with Crysis - could this have pushed the PSU to beyond limits nbsp

Relevancy 66.65%

Hi, I've recently been using drivermax to update my drivers. After my updates, I've been randomly getting BSODs then and now. I looked into the minidump with bluescreenviewer but cannot find a fix to the problem. I've uploaded the minidump. Please help! I'm using a shared a computer so I don't know if the origin of the problem is caused by someone else.

A:BSOD after driver updates. No idea which driver is at fault

I didn't see the BSOD protocols....sorry! Here is the required folder. Also, i'm told that the computer crashes frequently when trying to run old pc game like bioshock or empire earth.

http://www.sevenforums.com/bsod-help-support/295698-bsod-after-driver-updates-no-idea-driver-fault.html
Relevancy 65.79%

Okay so when I play World of Warcraft for minutes- hours the game randomly shuts down I found out my problem was that my Video Card isnt up to date so I updated I updated and im still getting the same issue I looked at my EPU- Engine and when i click on VGA it says VGA [SOLVED] Area BSOD not Page Driver less or Page Non Equal IQRL Fault not detected Can someone please tell me what the possible problem can be and how I can fix this My graphics [SOLVED] BSOD Driver IQRL not less or Equal Page Fault Non Page Area card is a ATI Radeon HD mb I cant attach mini-dumps because for some odd reason it I apparently dont have permission so if anyone know how to bypass through this please let me know System specs Motherboard ASUS M A -M Processor AMD Phenom II X GHz RAM GBDDR VGA ATI RADEON HD mb Oh and by the way it sometimes goes blackscreen with these lines coming down while the game plays in the background and I have to manually turn off my computer Sometimes it gives me BSODs with PAGE FAULT NON PAGE AREA or IRQL NOT LESS OR EQUAL

A:[SOLVED] BSOD Driver IQRL not less or Equal Page Fault Non Page Area

Smells like video card puttering out.

Are you referring to a permission denial by attempting to attach the dumps directly? You'll need to zip them first before sending them over, as only certain file types are permitted. Plus there's a 5 MB limit (doubt that's the cause though).

http://www.techsupportforum.com/forums/f299/solved-bsod-driver-iqrl-not-less-or-equal-page-fault-non-page-area-565765.html
Relevancy 65.36%

I have bought a new hardware recently Asus M A LT-M hardware and Area Nonpaged system Fault unstabilitity BSOD change. after In Page LE AMD II X and Geil GB DDR Value - - I assembled everything togheter with hardware left from BSOD and system unstabilitity after hardware change. Page Fault In Nonpaged Area my old PC which gave me this CPU AMD II X Mainboard Asus M A LT-M LE Memory Geil GB DDR Value - - Hard Drive BSOD and system unstabilitity after hardware change. Page Fault In Nonpaged Area GB Westgate Video Geforce GT Power Supply Chieftec smart W I formatted whole HDD and installed fresh copy of Windows XP service pack After few hours my windows started crashing BSOD PAGE FAULT IN NONPAGED AREA STOP x nv disp dll dumps of the BSOD in the attachment when I tried to play Crysis or Race Driver Grid I checked other games and windows crash in all of them Modern Warfare Need For Speed Shift Left Dead with same BSOD I tried reinstalling GPU drivers but that didn t helped I also tried installing old ones no success I have noticed that almost all of my applications suddenly crash Mozilla Chrome Office after few minutes of use Furthermore the files I download from the internet or copied from the usb sticks to HDD gets corrupted by CRC errors very often I reinstalled system two times but that didn t solved crashing and BSODS After that I had all my hardware component tested and I also have found nothing CPU Tested with orthos I ran two instances to test first two cores and the third one One hour test with no errors - C when IDLE - C when in stress RAM I tested my stick with Memtest passes and hour of testing which gave me no errors I tried testing them with this Memtest from hcidesign com it gave me few errors but I find Memtest to be more reliable Maybe I m wrong HDD Tested with HD tune CHKDSK and HDD Scan no errors C - C GPU Couldn t test because system crash when I try to run any graphic advanced application or game but it was fine before I changed my hardware C in IDLE and up to C in stress Here s my question what should I do I m getting out of ideas At start I thought that all errors are caused by bad stick of RAM but Memtest didn t showed any errors which made me confused Thanks for the help I ll provide you with all information you ll need just tell me Any kind of advice will be appreciated nbsp

A:BSOD and system unstabilitity after hardware change. Page Fault In Nonpaged Area

0x50AGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

nv4.disp.dll is a Nvidia display driver. Try the following:

1. Download Driver Cleaner Pro or Driver Sweeper (both have free versions; make sure the version will work with your OS) to your desktop screen and install.

2. Download the latest diver(s) for your video card but don't install them.

3. Uninstall your video card drivers and reboot your PC into Safe Mode. Run Driver Cleaner Pro or Driver Sweeper but ONLY for the video card drivers. I had someone use it on their chipset drivers! If it doesn't find any video card drivers that is quite okay.

4. Reboot and install new video card drivers.
 

http://www.techspot.com/community/topics/bsod-and-system-unstabilitity-after-hardware-change-page-fault-in-nonpaged-area.152973/
Relevancy 65.36%

Hi During this week I been having BSODs I installed Windows and all the updates Drivers from the manufacturers and some Apps games Verifier [SOLVED] BSOD others and furmark prime Ccleaner Visual Studio etc It is a clean Windows Install I [SOLVED] Verifier BSOD and others dont know what triggers them I tried to run a Verifier but I have an exception DRIVER VERIFIER IOMANAGER I'm a rookie using and understanding Windbg but what I saw in the last BSOD have something to do with HIDD sys but Im not sure that is the end of the problem Attached too I put the previous two BSODs that could give us more info about what is going on Regarding step OS Windows x -bit or x x What was the original installed OS on sthe ystem New installation Is the OS an OEM version came pre-installed on system or full retail version YOU purchased it from retailer I bought it from Windows Store digital download Approximate age of system hardware Months Approximate age of OS installation if you know day Have you re-installed the OS No CPU AMD FX- Video Card ATI AMD Radeon HD R X MotherBoard ASUS M A X EVO R Power Supply - Sentey W System Manufacturer No idea I purchase it in a tech store already with its parts I made some modifications like put a water cooling instead of the air cooling But in short it says quot To be filled by OEM quot Laptop or Desktop Desktop I did memtest passes advanced settings default cache No errors sfc scannow with errors and then Dism restore health Everything fine I did a chkdisk No errors Regarding Step I cant run a Driver Verifier as one of them is the offending driver and I cant log in I have to quot kill quot verifier with verifier reset on safe mode In the meantime I will check this carrona page PD I also put a rar archive with other BSODs that I had before the Sysnative In case you want to see them

A:[SOLVED] Verifier BSOD and others

Update:

I ran Memtest86+, 3 passes : No errors.

http://www.techsupportforum.com/forums/f299/solved-verifier-bsod-and-others-989513.html
Relevancy 64.5%

Hi to Driver from but likely Fault, which one? BSOD What do? all Ever since I purchased my Asus W J T ATI Mobility X I ve been plagued by BSOD casued by no particular action and at completely random times and intervals Suspecting the RAM I replaced it despite making it through many passes of memtest but no dice BSOD likely from Driver Fault, but which one? What to do? the problem persisted The Windows Error Reporter tells me I have a driver problem and running my minidumps through Windb tells me the same thing but they rarely get more specific than that I occasionally am told that my video driver is at fault but I ve upgraded it every time a new one is available and have tried the Omega Drivers as well to avail I ve tried updating virtually every other driver as well since I can t be sure it s the video driver Writing this very post somehow caused a BSOD so I ve been forced to switch to my faithful Linux backup computer for the time being Since the T can support it I think I may try to install Vista -bit and hope that a new set of drivers will resolve the problem Is this likely The three most recent Minidumps will be attached as soon as I can get the other computer running long enough to edit this post Thanks Brett nbsp

A:BSOD likely from Driver Fault, but which one? What to do?

When you have done Windb do you continue on to the kd> space at the bottom for further analysis by typing !analyze -v and then press enter to get detailed bugging information?

I have found that zeros me right to the driver causing the issue.

Edited Update: I read your minidumps and the two from 3/11 and 3/24 point to the ntkrpamp.exe and the one on 3/26 is due to win32k.sys. From what I have been reading, some from the archives of Tech Spot itself, 80% of it points to faulty RAM. Do a MemTest86+ for at least 10 passes to see if you have any memory errors.

Others here have greater knowledge than I, but if you have bad memory that can cause all kinds of headaches.
 

http://www.techspot.com/community/topics/bsod-likely-from-driver-fault-but-which-one-what-to-do.73358/
Relevancy 63.64%

I've done a memtest ran it for passes no errors I have quite a few minidump files and a dxdiag attached These BSOD basically driver BSOD fault NTFS happen when I am using a lot BSOD NTFS driver fault of USB devices it seems or anything that uses internet I use a Hawking hi-gain USB dish hwu dd rev b and my mouse and keyboard are USB Could it be a possible failing hard drive I've made sure all of my cables were secured correctly I've also made sure I am virus free and malware free I use avast anti-virus My system BSOD NTFS driver fault is stable if I am not doing a lot of things at once But if I am running a browser or two a game and an email client I will get a blue screen shortly after I've noticed this problem while watching youtube videos or hulu I am guaranteed a blue screen I've done a SFC SCANNOW in safe mode as well as a chkdsk f nothing seems to resolve the issue I've gotten blue screens in the past and it seems to only have gotten worse now I can't do much of anything I've recently added a webcam which is USB but removed it to see if it was causing the issue and still the same problem Any help would be appreciated

A:BSOD NTFS driver fault

Do you have a RAID setup? First, make sure all your windows updates are done. Then update your gpu and sound drivers. Run driver sweeper after you uninstall the drivers, to clean up any leftovers in safe mode and then install the newest drivers.

Then run the memory diagnostic - search for mem in the start menu.

Then, try a clean boot.

How to perform a clean boot procedure to determine whether background programs are interfering with a game or a program that you currently use

http://www.vistax64.com/general-discussion/256203-bsod-ntfs-driver-fault.html
Relevancy 63.64%

I've been having frequent BSODs for a while now. They happen intermittently, usually when I'm doing something graphical such as using skype, or streaming a video. I've tried a number of different versions of ATI's graphics drivers, to no avail. I've tried reinstalling them several times.

I ran driver verifier, but I couldn't get past the Windows bootup screen with it on. On a possibly related note, every time I start the computer, this screen freezes for a second, flickers once, and then continues.

I made this build about 8 months ago. I've got an ATI Radeon HD 5770 and I'm currently using driver version 8.850.0.0. Any help is very much appreciated

Thanks

A:BSOD - maybe display driver's fault?

edit - look at whole post please added more down below

What the minidump is pointing to is a windows core file that controls your network driver.
Though I can see how you thought it was graphics related as it's call ndis.sys ...looks like something display related but it's not.

First make sure the windows file is okay and not corrupt somehow by running this
SFC /SCANNOW Command - System File Checker
(it's quick and easy even if it doesn't change anything)

It would seem you have norton internet security installed. Make sure it's not accidentally blocking any system level processes (this can happen sometime and would explain your problem) ndis needs to be allowed.


Code:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001a7ac01, The address that the exception occurred at
Arg3: fffff8800cf56a18, Exception Record Address
Arg4: fffff8800cf56280, Context Record Address

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
ndis!ndisGetMiniportIndicateList+61
fffff880`01a7ac01 83c6ff add esi,0FFFFFFFFh

EXCEPTION_RECORD: fffff8800cf56a18 -- (.exr 0xfffff8800cf56a18)
ExceptionAddress: fffff88001a7ac01 (ndis!ndisGetMiniportIndicateList+0x0000000000000061)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800cf56280 -- (.cxr 0xfffff8800cf56280)
rax=fffffa800ab6d3b0 rbx=fffffa80084941a0 rcx=fffffa800a572e20
rdx=0000000000000001 rsi=000000000000000a rdi=0000000000000000
rip=fffff88001a7ac01 rsp=fffff8800cf56c50 rbp=0000000000000080
r8=fffff80003057401 r9=0000000000000000 r10=fffff80003052e80
r11=0000000000000000 r12=0000000000000000 r13=fffff88001a7a9e0
r14=0000000000000000 r15=0000000000000002
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
ndis!ndisGetMiniportIndicateList+0x61:
fffff880`01a7ac01 83c6ff add esi,0FFFFFFFFh
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031100e0
ffffffffffffffff

FOLLOWUP_IP:
ndis!ndisGetMiniportIndicateList+61
fffff880`01a7ac01 83c6ff add esi,0FFFFFFFFh

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88001a91568 to fffff88001a7ac01

STACK_TEXT:
fffff880`0cf56c50 fffff880`01a91568 : fffffa80`084941a0 00000000`00000080 fffffa80`073aa800 00000000`00000000 : ndis!ndisGetMiniportIndicateList+0x61
fffff880`0cf56c80 fffff880`01a7ab0c : 00000000`00010300 fffffa80`08495388 00000000`00000080 fffffa80`073aa850 : ndis!ndisPeriodicReceivesWorker+0x58
fffff880`0cf56cb0 fffff800`0317bbc6 : 00000000`00000000 fffffa80`0ab6d3b0 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x12c
fffff880`0cf56d40 fffff800`02eb6bc6 : fffff800`03052e80 fffffa80`0ab6d3b0 fffff800`03060c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0cf56d80 00000000`00000000 : fffff880`0cf57000 fffff880`0cf51000 fffff880`0cf56a00 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ndis!ndisGetMiniportIndicateList+61

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndis

IMAGE_NAME: ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18... Read more

http://www.sevenforums.com/bsod-help-support/171286-bsod-maybe-display-drivers-fault.html
Relevancy 63.64%

Hi all received a BSOD this morning Ran crash analyzer and it determined that the driver probably at fault is hardware disk I can post the full analysis but it's big Any one run into this before I just want to be sure it's not a hardware issues i e my drive Code Dump File - - dmp Crash Time AM Bug Check String SYSTEM THREAD is - The at BSOD fault driver hardware_disk CI.dll probably EXCEPTION NOT HANDLED Bug Check BSOD CI.dll - The driver probably at fault is hardware_disk Code x e Parameter ffffffff c Parameter fffff cf e Parameter fffff Parameter fffff e Caused By Driver CI dll Caused By Address CI dll e File Description Product Name Company File Version Processor x Crash Address CI dll e BSOD CI.dll - The driver probably at fault is hardware_disk Stack Address Stack Address Stack Address Computer Name Full Path C Windows Minidump - - dmp Processors Count Major Version Minor Version Dump File Size SYSTEM THREAD EXCEPTION NOT HANDLED e This is a very common bugcheck Usually the exception address pinpoints the driver function that caused the problem Always note this address as well as the link date of the driver image that contains this address Arguments Arg ffffffffc The exception code that was not handled Arg fffff cf e The address that the exception occurred at Arg fffff Exception Record Address Arg fffff e Context Record Address

A:BSOD CI.dll - The driver probably at fault is hardware_disk

I should also mention, I will fire up Hiren's Boot CD tonight and run some physical hard drive tests. I also recently removed the Intel Rapid Storage driver to try to isolate some issues. Doesn't look like it helped much.

http://www.sevenforums.com/bsod-help-support/259002-bsod-ci-dll-driver-probably-fault-hardware_disk.html
Relevancy 63.21%

I have an ADSL modem router combo device ZyXel Prestige HW- Recently I found that the LAN ports are no longer functioning properly It took a long time to arrive at this diagnosis because my second rig -- an dead, fault ghosts? LAN Router Solved: ports or hardware ancient AMD K -III was is connecting just fine Later it turned Solved: Router LAN ports dead, hardware fault or ghosts? out it is in fact the only computer that CAN connect It is a hardware level problem I suspect because the port indicator leds will not light up when a cable is plugged in The client computer will behave as if the cable is unplugged First I thought one particular port was broken but I ve connected the AMD rig to all ports for testing and sure enough it works on all of them Any other rig that I connect will stay on a perpetual cycle of trying to obtain an IP address and never getting it Yes I have tried switching cables rebooting clients AND the router etc The wireless is working just as well as it ever did nbsp

Relevancy 62.78%

I'm having Windows 7? BSOD in to fault Vista driver due a little trouble with my computer It jams during games the sound loops the screen freezes and then the computer will restart I had some trouble with this before but it was solved by buying a GOOD PSU instead of a crappy cheap one But this time I have Windows Ultimate GB ram KVR D N Processor E Intel Dual-Core GPU Sapphire ATI HD MB MSI BSOD due to Vista driver fault in Windows 7? Neo FR These are the Debug files I got Code SYSTEM SERVICE EXCEPTION b An exception happened while executing a system service routine Arguments Arg c Exception code that caused the bugcheck Arg fffff f ce Address of the exception record for the exception that caused the bugcheck Arg fffff eb Address of the context record for the exception that caused the bugcheck Arg zero Debugging Details ------------------ Debugger could not find nt in module list module list might be corrupt error x EXCEPTION CODE NTSTATUS xc - The instruction at x lx referenced memory at x lx The memory could not be s FAULTING IP fffff f ce b mov rcx qword ptr rcx h CONTEXT fffff eb -- cxr xfffff eb Unable to read context Win error n CUSTOMER CRASH COUNT DEFAULT BUCKET ID VISTA DRIVER FAULT BUGCHECK STR x B CURRENT IRQL LAST CONTROL TRANSFER from fffff c aa a to fffff c a c STACK TEXT fffff b cc fffff c aa a cd a fffffa c fffff e c xfffff c a c fffff b cc cd a fffffa c fffff e c fffff df e xfffff c aa a fffff b cc fffffa c fffff e c fffff df e fffff c x cd a fffff b cc fffff e c fffff df e fffff c fa xfffffa c fffff b cc fffff df e fffff c fa d xfffff e c fffff b cc fffff df e fffff c fa d fa x fffff b cc fffff c fa d fa xfffff df e fffff b cc fa d fa fffffa c xfffff c fffff b cc d fa fffffa c c c x fa fffff b cca fa fffffa c c c fffff c x d fffff b cca fffffa c c c fffff c ea db b x fa fffff b ccb fffffa c c c fffff c ea db b fffff b x fffff b ccb c c fffff c ea db b fffff b fffffa c xfffffa c fffff b ccc fffff c ea db b fffff b fffffa c x c c fffff b ccc ea db b fffff b fffffa c d c b xfffff c fffff b ccd fffff b fffffa c d c b d c ed xea db b fffff b ccd fffffa c d c b d c ed fffff c a xfffff b fffff b cce d c b d c ed fffff c a fffff b xfffffa c STACK COMMAND kb SYMBOL NAME ANALYSIS INCONCLUSIVE FOLLOWUP NAME MachineOwner MODULE NAME Unknown Module IMAGE NAME Unknown Image DEBUG FLR IMAGE TIMESTAMP BUCKET ID CORRUPT MODULELIST Followup MachineOwner Code DRIVER IRQL NOT LESS OR EQUAL d An attempt was made to access a pageable or completely invalid address at an interrupt request level IRQL that is too high This is usually caused by drivers using improper addresses If kernel debugger is available get stack backtrace Arguments Arg fffff cd c memory referenced Arg IRQL Arg value read operation write operation Arg fffff c address which referenced memory Debugging Details ------------------ Debugger could not find nt in module list module list might be corrupt error x WRITE ADDRESS unable to get nt MmSpecialPoolStart unable to get nt MmSpecialPoolEnd unable to get nt MmPoolCodeStart unable to get nt MmPoolCodeEnd fffff cd c CURRENT IRQL FAULTING IP fffff c CUSTOMER CRASH COUNT DEFAULT BUCKET ID VISTA DRIVER FAULT BUGCHECK STR xD LAST CONTROL TRANSFER from fffff c c to fffff c cf STACK TEXT fffff b c b fffff c c a fffff cd c xfffff c cf fffff b c c a fffff cd c fffff c xfffff c c fffff b c c fffff cd c fffff c xa fffff b c d fffff c xfffff cd c fffff b c d fffff c x fffff b c e fffff c x fffff b c e xfffff c STACK COMMAND kb SYMBOL NAME ANALYSIS INCONCLUSIVE FOLLOWUP NAME MachineOwner MODULE NAME Unknown Module IMAGE NAME Unknown Image DEBUG FLR IMAGE TIMESTAMP BUCKET ID CORRUPT MODULELIST Followup MachineOwner Code IRQL NOT LESS OR EQUAL a An attempt was made to access a pageable or completely invalid address at an interrupt request level IRQL that is too high This is usually caused by drivers using improper addresses If a kernel debugger is available get the stack backtrace Arguments Arg fffffa aedf memory referenced Arg IRQL ... Read more

A:BSOD due to Vista driver fault in Windows 7?

The logs show that kernel corruption has occurred.

Follow these instructions --> http://www.techsupportforum.com/1871981-post2.html

http://www.techsupportforum.com/forums/f299/bsod-due-to-vista-driver-fault-in-windows-7-a-434480.html
Relevancy 62.78%

Hey guys Recently got my new computer and it is fault? ntoskrnl.exe Daily driver BSOD, amazing Only problem is that or Daily BSOD, ntoskrnl.exe driver fault? times a day i get a BSOD I checked the Minidump files and it s saying something about VISTA DRIVER FAULT and ntoskrnl exe driver fault This is what the Dump File reads Code Loading Dump File C Users Nico Desktop - - dmp Mini Kernel Dump File Only registers and stack trace are available Symbol search path is Invalid Symbol loading may be unreliable without a symbol search path Use symfix to have the debugger Daily BSOD, ntoskrnl.exe driver fault? choose a symbol path After setting your symbol path use reload to refresh symbol locations Executable search path is Symbols can not be loaded because symbol path is not initialized The Symbol Path can be set by using the NT SYMBOL PATH environment variable using the -y lt symbol path gt argument when starting the debugger using sympath and sympath Unable to load image SystemRoot system ntoskrnl exe Win error n WARNING Unable to verify timestamp for ntoskrnl exe ERROR Module load completed but symbols could not be loaded for ntoskrnl exe Windows Kernel Version MP procs Free x Product WinNt suite TerminalServer SingleUserTS Personal Built by amd fre win gdr - Machine Name Kernel base xfffff a e PsLoadedModuleList xfffff c be Debug session time Sat Oct UTC System Uptime days Symbols can not be loaded because symbol path is not initialized The Symbol Path can be set by using the NT SYMBOL PATH environment variable using the -y lt symbol path gt argument when starting the debugger using sympath and sympath Unable to load image SystemRoot system ntoskrnl exe Win error n WARNING Unable to verify timestamp for ntoskrnl exe ERROR Module load completed but symbols could not be loaded for ntoskrnl exe Loading Kernel Symbols Loading User Symbols Loading unloaded module list Bugcheck Analysis Use analyze -v to get detailed debugging information BugCheck A b fffff a ddaa Kernel symbols are WRONG Please fix symbols to do analysis Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files such as the public OS symbols do not contain the required information Contact the group that provided you with these symbols if you need this command to work Type referenced nt KPRCB Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files such as the public OS symbols do not contain the required information Contact the group that provided you with these symbols if you need this command to work Type referenced nt KPRCB Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files such as the public OS symbols do not contain the required information Contact the group that provided you with these symbols if you need this command to work Type referenced nt KPRCB Probably caused by ntoskrnl exe nt fdaa Followup MachineOwner --------- kd gt analyze -v Bugcheck Analysis IRQL NOT LESS OR EQUAL a An attempt was made to access a pageable or completely invalid address at an interrupt request level IRQL that is too high This is usually caused by drivers using improper addresses If a kernel debugger is available get the stack backtrace Arguments Arg b memory referenced Arg IRQL Arg bitfield bit value read operation write operation bit value not an execute operation execute operation only on chips which support this level of status Arg fffff a ddaa address which referenced memory Debugging Details ------------------ Kernel symbols are WRONG Please fix symbols to do analysis Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have ful... Read more

A:Daily BSOD, ntoskrnl.exe driver fault?

Tell us when you get these BSODs, i.e., randomly or are you doing something specific at the time.

You have errors 0x3B and two 0xA but they only cite Windows OS drivers and these are usually too general to be of much diagnostic help.

By the way, I noticed your system hardware (nice set-up; love to hear your feed back on that 635 processor) and you are running 6 gigs of RAM. Try running with just 4 gigs. Do you gain stability?
 

http://www.techspot.com/community/topics/daily-bsod-ntoskrnl-exe-driver-fault.154313/
Relevancy 62.78%

Hey guys Recently got fault? Daily driver ntoskrnl.exe BSOD, my new computer and it is amazing Only problem is that or times a day i get a BSOD I checked the Minidump files and it's saying something about VISTA DRIVER FAULT and ntoskrnl exe driver fault This is what the Dump File reads Code Loading Dump File C Users Daily BSOD, ntoskrnl.exe driver fault? Nico Desktop - - dmp Mini Kernel Dump File Only registers and stack trace are available Symbol search path is Invalid Symbol loading may be unreliable without a symbol search path Use symfix to have the debugger choose a symbol path After setting your symbol path use reload to refresh symbol locations Executable search path is Symbols can not be loaded because symbol path is not initialized The Symbol Path can be set by using the NT SYMBOL PATH environment variable using the -y lt symbol path gt argument when starting the debugger using sympath and sympath Unable to load image SystemRoot system ntoskrnl exe Win error n WARNING Unable to verify timestamp for ntoskrnl exe ERROR Module load completed but symbols could not be loaded for ntoskrnl exe Windows Kernel Version MP procs Free x Product WinNt suite TerminalServer SingleUserTS Personal Built by amd fre win gdr - Machine Name Kernel base xfffff a e PsLoadedModuleList xfffff c be Debug session time Sat Oct UTC System Uptime days Symbols can not be loaded because symbol path is not initialized The Symbol Path can be set by using the NT SYMBOL PATH environment variable using the -y lt symbol path gt argument when starting the debugger using sympath and sympath Unable to load image SystemRoot system ntoskrnl exe Win error n WARNING Unable to verify timestamp for ntoskrnl exe ERROR Module load completed but symbols could not be loaded for ntoskrnl exe Loading Kernel Symbols Loading User Symbols Loading unloaded module list Bugcheck Analysis Use analyze -v to get detailed debugging information BugCheck A b fffff a ddaa Kernel symbols are WRONG Please fix symbols to do analysis Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files such as the public OS symbols do not contain the required information Contact the group that provided you with these symbols if you need this command to work Type referenced nt KPRCB Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files such as the public OS symbols do not contain the required information Contact the group that provided you with these symbols if you need this command to work Type referenced nt KPRCB Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files such as the public OS symbols do not contain the required information Contact the group that provided you with these symbols if you need this command to work Type referenced nt KPRCB Probably caused by ntoskrnl exe nt fdaa Followup MachineOwner --------- kd gt analyze -v Bugcheck Analysis IRQL NOT LESS OR EQUAL a An attempt was made to access a pageable or completely invalid address at an interrupt request level IRQL that is too high This is usually caused by drivers using improper addresses If a kernel debugger is available get the stack backtrace Arguments Arg b memory referenced Arg IRQL Arg bitfield bit value read operation write operation bit value not an execute operation execute operation only on chips which support this level of status Arg fffff a ddaa address which referenced memory Debugging Details ------------------ Kernel symbols are WRONG Please fix symbols to do analysis Your debugger is not using the correct symbols In order for this command to work properly your symbol path must point to pdb files that have full type information Certain pdb files su... Read more

A:Daily BSOD, ntoskrnl.exe driver fault?

  
Quote: Originally Posted by SunDown


Hey guys, Recently got my new computer, and it is amazing! Only problem is that 2 or 3 times a day i get a BSOD...

I checked the Minidump files and it's saying something about VISTA_DRIVER_FAULT and ntoskrnl.exe driver fault.

This is what the Dump File reads:


Code:
Loading Dump File [C:\Users\Nico\Desktop\100210-21122-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c5be50
Debug session time: Sat Oct 2 15:59:55.289 2010 (UTC + 1:00)
System Uptime: 0 days 4:09:36.710
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2b, 2, 0, fffff80002a6ddaa}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** **... Read more

http://www.sevenforums.com/bsod-help-support/115491-daily-bsod-ntoskrnl-exe-driver-fault.html
Relevancy 62.35%

Hello everybody, while I was playing music on my computer I had a BSOD. This BSOD(Bad Pool Header)has affected me when gaming too.

I do not know what to do I really would appreciate all the help I could get.

Here you will find my dmp file uploaded to my skydrive.

https://onedrive.live.com/redir?resi...int=file%2cdmp

A:BSOD Bad Pool Header (Driver at fault- audiodg.exe)

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

http://www.sevenforums.com/bsod-help-support/364107-bsod-bad-pool-header-driver-fault-audiodg-exe.html