BSOD Win 7 --- Driver_IRQL_Not_Less_Or_EQUAL

Is tap0901.sys, OpenVPN driver or COMODO, needed?

I don't have a clue what tap0901.sys is nor COMODO --- OpenVPN yes I need that one to remote into Work.

jo15765 said:

I don't have a clue what tap0901.sys is nor COMODO --- OpenVPN yes I need that one to remote into Work.

OpenVPN is tap0901.sys, so I guess we'll have to leave that as is. Driver Verifier was not happy with it.

Are you still having blue screen crashes after the steps we have followed?

Yeppers, still the same BSOD! I am running the Windows_NT6_BSOD tool that you linked me to now, but it is taking quite some time to run for some reason. I am attaching my Health Report now for review.

Looks like the BSOD tool just got hung up, I cancelled it and re-ran and it was done in a flash. Here is that outcome as well.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jo15765\Windows_NT6_BSOD_jcgriff2\011012-23712-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03093670
Debug session time: Tue Jan 10 20:17:39.184 2012 (UTC - 7:00)
System Uptime: 0 days 18:30:43.479
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+6436666136633265
00000000`00000000 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff80000b9c740 -- (.trap 0xfffff80000b9c740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80000b9c801 rbx=0000000000000000 rcx=fffffa80060cd618
rdx=fffff80000b9c8d8 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff80000b9c8d0 rbp=0000000000000000
 r8=fffff80000b9c8d0  r9=0000000000000000 r10=0000000000000000
r11=000000005e040600 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eca1e9 to fffff80002ecac40

FAILED_INSTRUCTION_ADDRESS: 
+6436666136633265
00000000`00000000 ??              ???

STACK_TEXT:  
fffff800`00b9c5f8 fffff800`02eca1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`00b9c600 fffff800`02ec8e60 : fffffa80`08608810 00000000`00000000 fffffa80`0552f410 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c740 00000000`00000000 : 00000000`00000200 00000000`5e040600 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02ec8e60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260

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

Inconclusive, unfortunately. Let's proceed to the next step. Check for viruses.

Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
Download the Fakerean removal tool but do not run it yet.
Start your computer in Safe Mode
Unzip VIPRE Rescue and let it run.
Run a full scan with Malwarebytes.
Run the fakerean removal tool.

Vipre Rescue ran and found no errors.
Malwarebytes ran and found no errors.
The Fakerean tool, when I opened it, it opened a command prompt and then said it needs to reboot my computer, I allowed it to reboot. Haven't had a chance to try to burn a cd/dvd again, but this tool maybe ran for 5 seconds. Is that normal for this tool?

jo15765 said:

Vipre Rescue ran and found no errors.
Malwarebytes ran and found no errors.
The Fakerean tool, when I opened it, it opened a command prompt and then said it needs to reboot my computer, I allowed it to reboot. Haven't had a chance to try to burn a cd/dvd again, but this tool maybe ran for 5 seconds. Is that normal for this tool?

The fakerean tool cleans out the OS 2012 virus and then puts any moved system files and users files back where they belong. It is very fast. More than likely, you did not have any problems, and will not see a change from it.

If you still have blue screen crashes after doing the virus scans, run Windows updates and install all Windows updates that have not yet been installed.

All Windows Updates have been installed. I install them automatically, as well as manually check once a week (and I acutally checked last night).

I will attempt to burn again this afternoon and keep my fingers crossed that no BSOD will appear!

jo15765 said:

All Windows Updates have been installed. I install them automatically, as well as manually check once a week (and I acutally checked last night).

I will attempt to burn again this afternoon and keep my fingers crossed that no BSOD will appear!

What program do you use to do your burning? You may consider uninstalling that program and installing it again as it could be causing the blue screen crashes due to corrupted install files.

I normally will use Windows DVD Maker but I have some videos from my iphone that are mp4 that Windows DVD Maker does not support, so I was trying to use ConvertXToDVD since it's an all in one conversion/burning app that will take it through the entire process for me.

I have also tried using DVDFab, oneClickDVDCopy, 123 CopyDVD, DVD Cloner...quite an extensive amount, I will download the trial version and try to burn if it causes a BSOD I uninstall and move onto the next. All except DVDFab, I have the paid version of this product and it also causes a BSOD, even contacted there support team, and they were unable to provide a resolutoin as to what is causing the BSOD or a workaround on how to use there product and not cuase a BSOD.