New
#1
New computer BSOD IQRL_NOT_LESS_OR_EQUAL 0x0000000a
So, my fiance orders a new computer from HP and it comes in with a broken screen. We get a replacement and everything seems fine until the wonderful BSOD happens. Now I am trying to find a solution for this so we do not have to deal with customer support, shipping, transferring Norton, and the entire exchange process all over again. There are a few issues I am wondering about. (I have attached, hopefully in the correct way, the files requested in the "How to post a BSOD". Attachment 182523
Attachment 182524)
Her operating system came pre-installed on the computer, and we received the computer this past Friday. The OS is Windows 7 Home Premium. When I look at system properties it says the OS is 64-bit. However, when I have been looking for the issues within the system's files I see a whole lot of Win32 and a lot of ......(x86). All of these (to me) indicate 32-bit operations. Yet when I ran windows update it searched for updates for x64. I don't know if this could be part of the issue with the blue screens.
The blue screen seems to happen when I wake the computer up or when there is an internet issue.
This error appears in the event viewer A LOT! : "Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file."
I have no idea what this means or if it is related to our problems.
I found the bugcheck file in event viewer which reads:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000001400000013, 0x0000000000000002, 0x0000000000000000, 0xfffff80002c96745). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110611-21216-01.
Please ask if you need any more information. A quick fix would be wonderful since my fiance is a teacher and really needs a smooth functioning computer and we've had to deal with a two week delay because of the first exchange process. Thank you all for your help!
Ben