[lisahboone]

I am running Visat Home Premium 64bit SP1 on my new dell laptop [came already installed]. Everytime I try to update [I have it download and I install the updates] when the system re-boots it goes to the blue screen with the error 'IQRL_NOT_EQUAL' and does a dump and then when I restart after that I have to do a system restore to a point before the update for the system to boot properly. The automatic system repair works 10% of the time otherwise I have to F8 and system restoe. I am only doing the required updates - not the recommended. I have tried 1-2 at a time in lieu of the 15 now on my list. Same problem. HELP!!

[Advertisements]

Most often these sort of things are caused by outdated drivers.
Visit the Dell website here: http://support.dell..../...;l=en&s=gen

Enter your service tag number and select the proper OS.

Check the dates of the drivers there. Download and install anything that's dated after February of 2008.
Then try the updates again.

If it still Blue Screens on you, please provide us with the details of the BSOD event. More info on locating this stuff is in this post: http://www.bleepingc...tml#entry409491

[usasma]

Most often these sort of things are caused by outdated drivers.
Visit the Dell website here: http://support.dell..../...;l=en&s=gen

Enter your service tag number and select the proper OS.

Check the dates of the drivers there. Download and install anything that's dated after February of 2008.
Then try the updates again.

If it still Blue Screens on you, please provide us with the details of the BSOD event. More info on locating this stuff is in this post: http://www.bleepingc...tml#entry409491

[lisahboone]

I updated the bios and I thought it was working. I was able to run 2 of the updates but then the problem showed up again - it is possible that the 2 updates were not part of the problem.

the bsod reads:

IRQL_NOT_LESS_OR_EQUAL

0X0A
0X880
0X01
0XFFFFF80001C45D19

HELP!!!

[lisahboone]

Last error [just happened again]:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000880
BCP2: 000000000000000C
BCP3: 0000000000000001
BCP4: FFFFF80001C77D19
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

[usasma]

Let's try an analysis of the memory dump files. Follow the instructions at this link: http://usasma.vox.co...ed-02oct08.html Don't be dismayed by the amount of stuff there, just follow the steps one by one and it'll work just fine. Post back here with the results and we'll see what it says.

[lisahboone]

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols


Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.22291.amd64fre.vistasp1_ldr.081020-1655
Machine Name:
Kernel base = 0xfffff800`01c50000 PsLoadedModuleList = 0xfffff800`01e15db0
Debug session time: Wed Apr 15 22:05:08.492 2009 (GMT-5)
System Uptime: 0 days 0:00:34.210
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols

Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {880, c, 1, fffff80001c77d19}

*** ERROR: Module load completed but symbols could not be loaded for OA001Vid.sys
*** ERROR: Module load completed but symbols could not be loaded for OA001Ufd.sys
Probably caused by : OA001Vid.sys ( OA001Vid+100a2 )

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: 0000000000000880, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000001, 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: fffff80001c77d19, address which referenced memory

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


WRITE_ADDRESS: 0000000000000880

CURRENT_IRQL: c

FAULTING_IP:
nt!KiUnwaitThread+19
fffff800`01c77d19 48099180000000 or qword ptr [rcx+80h],rdx

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffffa60005e4670 -- (.trap 0xfffffa60005e4670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa60005e4828 rbx=0000000000000000 rcx=0000000000000800
rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001c77d19 rsp=fffffa60005e4800 rbp=fffffa600398eb60
r8=0000000000000000 r9=fffffa600398eb58 r10=fffffa6003c1d090
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiUnwaitThread+0x19:
fffff800`01c77d19 48099180000000 or qword ptr [rcx+80h],rdx ds:00000000`00000880=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ca2eae to fffff80001ca3110

STACK_TEXT:
fffffa60`005e4528 fffff800`01ca2eae : 00000000`0000000a 00000000`00000880 00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx
fffffa60`005e4530 fffff800`01ca1d8b : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000800 : nt!KiBugCheckDispatch+0x6e
fffffa60`005e4670 fffff800`01c77d19 : 00000000`00000000 00000000`00000004 ffffffff`c00002d3 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`005e4800 fffff800`01ca956e : 00000000`00000800 fffffa60`0398eb60 00000000`00000000 fffff800`01dca4c0 : nt!KiUnwaitThread+0x19
fffffa60`005e4830 fffffa60`03c1d0a2 : 00000000`00000000 00000000`00000000 00000000`c0000200 fffffa80`00000000 : nt!KeSetEvent+0x5ee
fffffa60`005e48a0 fffff800`01d702da : fffffa80`0a632790 fffff800`01d4df01 fffffa80`04cf8010 fffffa80`066a3a30 : OA001Vid+0x100a2
fffffa60`005e48d0 fffff800`01ca5485 : fffffa80`04cf8010 fffffa80`066a3b01 fffffa80`066a3b88 fffffa60`027e702a : nt!PopRequestCompletion+0x4a
fffffa60`005e4910 fffffa60`027e514a : 00000000`00000000 00000000`00000000 fffffa80`04cf82d8 fffffa60`027e2c61 : nt!IopfCompleteRequest+0x315
fffffa60`005e49d0 fffffa60`027f1892 : fffffa80`04cf8010 fffffa80`066a6b88 fffffa80`066a3b80 fffffa80`066a3b88 : usbccgp!DispatchPdoPower+0x21e
fffffa60`005e4a10 fffffa60`027dd67c : fffffa80`066a3b88 fffffa80`066a6b88 fffffa80`066a3b80 fffffa80`04cf8010 : usbccgp!USBC_Power+0xd6
fffffa60`005e4a50 fffff800`01d5ebe2 : fffffa80`066a3a30 fffffa80`04cf8201 fffffa80`04cf8000 fffffa80`04cf8010 : usbccgp!USBC_Dispatch+0x250
fffffa60`005e4ac0 fffffa60`02e35798 : fffffa80`066a5980 fffffa80`04cf82d8 fffffa80`04cf8010 00000000`00000000 : nt!IopPoHandleIrp+0x32
fffffa60`005e4af0 fffffa60`02e35b00 : fffffa80`04cf82d8 fffffa80`066a56d0 00000000`00000000 00000000`00000000 : ks!CKsDevice::DispatchDeviceSetPowerIrp+0x1b8
fffffa60`005e4b50 fffff800`01d5ebe2 : fffffa80`00000001 fffffa80`04cf8010 fffffa80`04cf8320 fffffa80`066ba190 : ks!CKsDevice::DispatchPower+0x134
fffffa60`005e4ba0 fffffa60`03c5c43e : fffffa80`04cf8010 fffffa80`04cf8320 fffffa80`066ba190 fffffa80`03cb4720 : nt!IopPoHandleIrp+0x32
fffffa60`005e4bd0 fffff800`01d5ebe2 : fffffa80`04cf8010 fffffa80`04cf8320 fffffa80`065f0440 fffffa80`04cf8010 : OA001Ufd+0x143e
fffffa60`005e4c10 fffffa60`02f9b8f0 : 00000000`00000001 fffffa80`04b75050 ffff96b8`754d12c4 fffffa60`005efcc0 : nt!IopPoHandleIrp+0x32
fffffa60`005e4c40 fffff800`01d6dfea : 00000000`00000001 00000000`00000000 00200045`00000000 fffffa80`066a3680 : ksthunk!CKernelFilterDevice::DispatchIrp+0x230
fffffa60`005e4ca0 fffff800`01ec6b9f : 00690020`004e0049 fffffa80`03cb4720 00000000`00000080 00650072`00500001 : nt!PopIrpWorker+0x3ca
fffffa60`005e4d50 fffff800`01cde406 : fffffa60`005ec180 fffffa80`03cb4720 fffffa80`03cb5040 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`005e4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
OA001Vid+100a2
fffffa60`03c1d0a2 4883c428 add rsp,28h

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: OA001Vid+100a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: OA001Vid

IMAGE_NAME: OA001Vid.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48d37128

FAILURE_BUCKET_ID: X64_0xA_OA001Vid+100a2

BUCKET_ID: X64_0xA_OA001Vid+100a2

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

[usasma]

Do you have a Creative camera installed on the system?
I'd suggest going to Start...Control Panel...Programs...Uninstall a program.
In the list there, right click on the Creative Camera software and select "Uninstall"

Once you're sure that the problem has been solved, then you can download a new copy of the software from the manufacturer's website and install it on your system according to the instructions.

[lisahboone]

That did it!!!!! I have sucessfully downloaded and updated the 20 windows updates that were in the update queue. I disabled the camera in Device Manager and uninstalled the software as I do not plan to use the camera at this stage of usage of the laptop. I also took it out of the windows startup program list.

THANKS FOR ALL THE HELP!!!!!!!!!

[usasma]

Glad to hear that it worked. Thanks for letting us know - it'll help others who come looking for help with a similar problem!

[CincyJohn]

I have the EXACT same condition reported above. Called Dell and they claim they can't help b/c I bought the Dell Studio 1537 at Best Buy

Anyhow, great instructions above...I tried to follow the links and the BSOD diagnosis but when I try to open the .dmp file, Windbg popup says "Access is Denied" and something about contact file owner or administrator! So I can't follow the rest of the diagnostic steps.

Sorry, new at Vista and need help b/c any update results in 20 min of BSOD restarts before spontaneously going to Step 3 of 3 update screen.

Any help is appreciated greatly!

Edited by CincyJohn, 18 August 2009 - 08:02 PM.

[CincyJohn]

Scratch that...fixed the Access is Denied issue (disabled User Access Control to fix).
Got the report...same OA001Vid issue as above. Report looks the exact same.


Couldn't find a creative camera installed at first, but used the Dell link above to find a critical update from Mar 08 for the Dell Webcam! Installed the driver and all is well. Updates install fine with no BSOD. Would have never guessed an issue with the webcam driver (never use webcam).

Will have to bookmark this thread...great info/advice.

THANK YOU!!!

Edited by CincyJohn, 18 August 2009 - 10:23 PM.