Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Win 7 --- Driver_IRQL_Not_Less_Or_EQUAL

12 Jan 2012   #31
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by jo15765 View Post
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.
Is the firmware up to date on the drive?


My System SpecsSystem Spec
.
12 Jan 2012   #32
jo15765

Ultimate 64x
 
 

I have no idea, how would I check the firmware?
My System SpecsSystem Spec
12 Jan 2012   #33
writhziden

Windows 7 Home Premium 64 Bit
 
 

  1. Click Start Menu
  2. Click My Computer/Computer
  3. Right click your CD/DVD/Blu-Ray drive
  4. Click Properties
  5. Click the Hardware tab
  6. Type DVD/CD-ROM drives should have a name associated with it
  7. Type that name here and I will try to find a firmware update for you (I will need the full name including the model number if applicable)
My System SpecsSystem Spec
.

12 Jan 2012   #34
jo15765

Ultimate 64x
 
 

It shows All disk Drives
Optiarc DVD RW AD-7710H DVD/CD Rom Drive
Toshiba MK6476GSXN Disk Drives
My System SpecsSystem Spec
12 Jan 2012   #35
writhziden

Windows 7 Home Premium 64 Bit
 
 

Unfortunately, there are no new firmware updates for your device. I am out of ideas as to how to fix your problem at the moment. Run Driver Verifier as before, but do not include tap0901.sys as a driver to be verified as we know Windows 7 does not like it and you need it.
My System SpecsSystem Spec
12 Jan 2012   #36
jo15765

Ultimate 64x
 
 

They actually just released an updated version to my VPN Software so maybe that will correct the issue with that specific one. I will run driver verifier again, and hopefully this will correct it. Can you provide me with the directions on how to do that again?
My System SpecsSystem Spec
12 Jan 2012   #37
writhziden

Windows 7 Home Premium 64 Bit
 
 

To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
My System SpecsSystem Spec
16 Jan 2012   #38
jo15765

Ultimate 64x
 
 

I re-ran verifier and still same BSOD when attempting to burn...attached is log files.
My System SpecsSystem Spec
16 Jan 2012   #39
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jo15765\Windows_NT6_BSOD_jcgriff2\011312-20935-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`02e63000 PsLoadedModuleList = 0xfffff800`030a8670 Debug session time: Fri Jan 13 05:54:57.841 2012 (UTC - 7:00) System Uptime: 0 days 9:15:40.152 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D5, {fffff98008224f40, 0, fffff88005a35419, 0} Unable to load image \SystemRoot\system32\DRIVERS\tap0901.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for tap0901.sys *** ERROR: Module load completed but symbols could not be loaded for tap0901.sys Could not read faulting driver name Probably caused by : tap0901.sys ( tap0901+3419 ) Followup: MachineOwner --------- 2: 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: fffff98008224f40, memory referenced Arg2: 0000000000000000, value 0 = read operation, 1 = write operation Arg3: fffff88005a35419, 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 fffff80003112100 fffff98008224f40 FAULTING_IP: tap0901+3419 fffff880`05a35419 83bb9002000000 cmp dword ptr [rbx+290h],0 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: fffff880033b6400 -- (.trap 0xfffff880033b6400) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000001c rbx=0000000000000000 rcx=00000000000000a8 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88005a35419 rsp=fffff880033b6590 rbp=fffff880033b66c0 r8=0000000000000000 r9=fffffa8006b79cb0 r10=0000000000000001 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy tap0901+0x3419: fffff880`05a35419 83bb9002000000 cmp dword ptr [rbx+290h],0 ds:00000000`00000290=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e8b9fc to fffff80002edfc40 STACK_TEXT: fffff880`033b6298 fffff800`02e8b9fc : 00000000`00000050 fffff980`08224f40 00000000`00000000 fffff880`033b6400 : nt!KeBugCheckEx fffff880`033b62a0 fffff800`02eddd6e : 00000000`00000000 fffff980`08224f40 00000000`00000000 fffff980`08224cb0 : nt! ?? ::FNODOBFM::`string'+0x4611f fffff880`033b6400 fffff880`05a35419 : 00000000`00000000 fffff880`016ea62d 00000000`00000000 fffff880`033b6600 : nt!KiPageFault+0x16e fffff880`033b6590 00000000`00000000 : fffff880`016ea62d 00000000`00000000 fffff880`033b6600 15400001`59b40500 : tap0901+0x3419 STACK_COMMAND: kb FOLLOWUP_IP: tap0901+3419 fffff880`05a35419 83bb9002000000 cmp dword ptr [rbx+290h],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: tap0901+3419 FOLLOWUP_NAME: MachineOwner MODULE_NAME: tap0901 IMAGE_NAME: tap0901.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ade24e5 FAILURE_BUCKET_ID: X64_0xD5_VRF_tap0901+3419 BUCKET_ID: X64_0xD5_VRF_tap0901+3419 Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jo15765\Windows_NT6_BSOD_jcgriff2\011512-60575-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`02e60000 PsLoadedModuleList = 0xfffff800`030a5670 Debug session time: Sun Jan 15 21:00:52.176 2012 (UTC - 7:00) System Uptime: 0 days 0:00:46.488 Loading Kernel Symbols ............................................................... ................................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {5, 2, 0, fffff80002ef25b5} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 0: 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: 0000000000000005, 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: fffff80002ef25b5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310f100 0000000000000005 CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+ae5 fffff800`02ef25b5 488b09 mov rcx,qword ptr [rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: ffffffffffffff89 TRAP_FRAME: fffff880033c4130 -- (.trap 0xfffff880033c4130) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff880033c4508 rbx=0000000000000000 rcx=0000000000000005 rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ef25b5 rsp=fffff880033c42c0 rbp=0000000000000000 r8=fffff880033c43c8 r9=fffff880033c43c0 r10=0000000000000002 r11=fffff80002ef1ad0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!IopCompleteRequest+0xae5: fffff800`02ef25b5 488b09 mov rcx,qword ptr [rcx] ds:00000000`00000005=???????????????? Resetting default scope LOCK_ADDRESS: fffff800030dbb80 -- (!locks fffff800030dbb80) Resource @ nt!PiEngineLock (0xfffff800030dbb80) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0xfffff800030dbb80 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff80002edc1e9 to fffff80002edcc40 STACK_TEXT: fffff880`033c3fe8 fffff800`02edc1e9 : 00000000`0000000a 00000000`00000005 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`033c3ff0 fffff800`02edae60 : fffff6fc`000189c8 fffff800`02efa7ef 00000000`00000000 fffff980`04424ea0 : nt!KiBugCheckDispatch+0x69 fffff880`033c4130 fffff800`02ef25b5 : fffffa80`051ff680 fffff800`02edf4da ffff0800`00000011 00000000`00000000 : nt!KiPageFault+0x260 fffff880`033c42c0 fffff800`02ed02f7 : 00000000`00000001 00000000`00000000 fffff880`033c4400 fffff800`00000000 : nt!IopCompleteRequest+0xae5 fffff880`033c4390 fffff800`02ee213d : fffffa80`051ff680 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7 fffff880`033c4410 fffff800`02ee474f : 00000000`00000103 fffff800`02ec49cb fffff980`00000000 00000000`00000103 : nt!KiCommitThreadWait+0x3dd fffff880`033c44a0 fffff800`03139122 : fffffa80`09dc5b00 00000000`00000000 fffff880`033c4500 fffffa80`09cf7100 : nt!KeWaitForSingleObject+0x19f fffff880`033c4540 fffff800`032968e4 : fffffa80`051d4184 00000000`00000000 fffffa80`051cfd00 00000000`00120010 : nt! ?? ::NNGAKEGL::`string'+0x180ec fffff880`033c45b0 fffff800`032c761f : fffffa80`09dc4880 fffffa80`051d4010 fffff8a0`008f2770 fffffa80`051d4010 : nt!IopQueryLegacyBusInformation+0x64 fffff880`033c4660 fffff800`032c8aa2 : fffffa80`051d3390 fffffa80`051d4010 00000000`00000001 fffffa80`051cfd00 : nt!PipCallDriverAddDevice+0x76f fffff880`033c4810 fffff800`032c8f3c : fffff800`030d9500 00000000`00000000 00000000`00000001 fffff800`03146814 : nt!PipProcessDevNodeTree+0x2b2 fffff880`033c4a80 fffff800`02fd98c2 : 00000001`00000003 fffff800`0307d2b8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c fffff880`033c4ad0 fffff800`02ee7001 : fffff800`02fd95c0 fffff8a0`005e3701 fffff800`0307d200 fffff8a0`0024b090 : nt!PnpDeviceActionWorker+0x302 fffff880`033c4b70 fffff800`03177fee : 00000000`00000000 fffffa80`051ff680 00000000`00000080 fffffa80`051e8040 : nt!ExpWorkerThread+0x111 fffff880`033c4c00 fffff800`02ece5e6 : fffff880`031d7180 fffffa80`051ff680 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033c4c40 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`033c4290 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02edae60 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_0xA_VRF_nt!KiPageFault+260 BUCKET_ID: X64_0xA_VRF_nt!KiPageFault+260 Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jo15765\Windows_NT6_BSOD_jcgriff2\011612-30950-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`02e52000 PsLoadedModuleList = 0xfffff800`03097670 Debug session time: Mon Jan 16 17:50:16.288 2012 (UTC - 7:00) System Uptime: 0 days 0:00:25.599 Loading Kernel Symbols ............................................................... ................................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {5, 2, 0, fffff80002ee45b5} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 1: 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: 0000000000000005, 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: fffff80002ee45b5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003101100 0000000000000005 CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+ae5 fffff800`02ee45b5 488b09 mov rcx,qword ptr [rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: ffffffffffffff89 TRAP_FRAME: fffff880033bd130 -- (.trap 0xfffff880033bd130) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff880033bd508 rbx=0000000000000000 rcx=0000000000000005 rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ee45b5 rsp=fffff880033bd2c0 rbp=0000000000000000 r8=fffff880033bd3c8 r9=fffff880033bd3c0 r10=0000000000000002 r11=fffff80002ee3ad0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!IopCompleteRequest+0xae5: fffff800`02ee45b5 488b09 mov rcx,qword ptr [rcx] ds:00000000`00000005=???????????????? Resetting default scope LOCK_ADDRESS: fffff800030cdb80 -- (!locks fffff800030cdb80) Resource @ nt!PiEngineLock (0xfffff800030cdb80) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0xfffff800030cdb80 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff80002ece1e9 to fffff80002ecec40 STACK_TEXT: fffff880`033bcfe8 fffff800`02ece1e9 : 00000000`0000000a 00000000`00000005 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`033bcff0 fffff800`02ecce60 : fffff6fc`00018958 fffff800`02eec7ef 00000000`00000000 fffff980`03754ea0 : nt!KiBugCheckDispatch+0x69 fffff880`033bd130 fffff800`02ee45b5 : fffffa80`051ebb60 fffff800`02ed14da ffff0800`00000011 00000000`00000000 : nt!KiPageFault+0x260 fffff880`033bd2c0 fffff800`02ec22f7 : 00000000`00000001 00000000`00000000 fffff880`033bd400 fffff800`00000000 : nt!IopCompleteRequest+0xae5 fffff880`033bd390 fffff800`02ed413d : fffffa80`051ebb60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7 fffff880`033bd410 fffff800`02ed674f : 00000000`00000103 fffff800`02eb69cb fffff980`00000000 00000000`00000103 : nt!KiCommitThreadWait+0x3dd fffff880`033bd4a0 fffff800`0312b122 : fffffa80`0991d000 00000000`00000000 fffff880`033bd500 fffffa80`09926300 : nt!KeWaitForSingleObject+0x19f fffff880`033bd540 fffff800`032888e4 : fffffa80`05e51a04 00000000`00000000 fffffa80`05e4e6a0 00000000`00120010 : nt! ?? ::NNGAKEGL::`string'+0x180ec fffff880`033bd5b0 fffff800`032b961f : fffffa80`093fd290 fffffa80`05e51890 fffff8a0`008fc380 fffffa80`05e51890 : nt!IopQueryLegacyBusInformation+0x64 fffff880`033bd660 fffff800`032baaa2 : fffffa80`05e51b10 fffffa80`05e51890 00000000`00000001 fffffa80`05e4e6a0 : nt!PipCallDriverAddDevice+0x76f fffff880`033bd810 fffff800`032baf3c : fffff800`030cb500 00000000`00000000 00000000`00000001 fffff800`03138814 : nt!PipProcessDevNodeTree+0x2b2 fffff880`033bda80 fffff800`02fcb8c2 : 00000001`00000003 fffff800`0306f2b8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c fffff880`033bdad0 fffff800`02ed9001 : fffff800`02fcb5c0 fffff8a0`005f0501 fffff800`0306f200 fffff8a0`0022a1f0 : nt!PnpDeviceActionWorker+0x302 fffff880`033bdb70 fffff800`03169fee : 00000000`00000000 fffffa80`051ebb60 00000000`00000080 fffffa80`051cc040 : nt!ExpWorkerThread+0x111 fffff880`033bdc00 fffff800`02ec05e6 : fffff880`031d7180 fffffa80`051ebb60 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033bdc40 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd290 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02ecce60 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_0xA_VRF_nt!KiPageFault+260 BUCKET_ID: X64_0xA_VRF_nt!KiPageFault+260 Followup: MachineOwner ---------
What do you use for backing up your computer? When did you last update the BIOS and/or Chipset drivers for your computer?

The BIOS update would be on the Toshiba support site. The latest Chipset drivers you should check on Intel. Let Intel determine the right updates through the Intel® Driver Update Utility.
My System SpecsSystem Spec
16 Jan 2012   #40
jo15765

Ultimate 64x
 
 

Below are updates from the link you provided...should I install them all?
Graphics Driver
Intel Chipset Software Installation Utility
Audio Driver
Wireless Network
Wired Networking
My System SpecsSystem Spec
Reply

 BSOD Win 7 --- Driver_IRQL_Not_Less_Or_EQUAL




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD driver_irql_not_less_or_equal
Hello! I've had it once before and it was McAffe's fault. It came back and I'm not sure what it is now. Besides this issue, my computer also randomly turns off by itself sometimes with no error messages, I think they're related. I updated my system specs and am posting the kernel dump (is that...
BSOD Help and Support
BSOD Driver_IRQL_not_less_or_equal
Hi Guys i need help on my BSOD attachment is the minidump you guys needed Thanks for the Help Regards Kang
BSOD Help and Support
Bsod, driver_irql_not_less_or_equal
Hello again WSF I got two BSOD's within a 2 hour interval (both dumps attached) Unfortunately I did not have DriverVerifier enabled on either of them, but I have enabled it now so if any further BSOD occur (wich I strongly expect) it will upload the dumps. Any help is much appreciated. ...
BSOD Help and Support
BSOD - driver_irql_not_less_or_equal
I am having frequent BSOD with irql message - please see the attached PERF- html and minidump info System specifics- Windows professional 64 bit 2 years old OEM installed from thinkpad. Appreciate any help. Thanks
BSOD Help and Support
Bsod: Driver_irql_not_less_or_equal
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Additional information about the problem: BCCode: d1 BCP1: 0000000000000028 BCP2: 0000000000000002 BCP3: 0000000000000000
BSOD Help and Support
BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL, Help please.
Good evening to you all! :D Greetings aside; my computer has been crashing a lot recently, After a fresh install of Windows 7 Ultimate (x64 bit). I get a: DRIVER_IRQL_NOT_LESS_OR_EQUAL (BC Code d1) often and also IRQL_NOT_LESS_OR_EQUAL (BC Code a) every now and again I generally get the...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 02:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App