BSOD - Infrequent, browsing mostly. IRQL_NOT_LESS_OR_EQUAL

This single crash is inconclusive I am afraid.

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

Oh right , I see. Sorry about that. I'll wait till I have a second crash then, I've done plenty of waiting I can stand to wait a bit longer :)

When that happens, should I post in this thread again with the updated report & app result, or would you rather I made a new one?

Edit: I'll prob wait till i have 3, if that will be more helpful. I guess I could start leaving my computer on desktop all day to see if I can 'encourage' some more BSOD's, or would that be a bad idea, because they might not be 'genuine'?

Yeoman said:

Oh right , I see. Sorry about that. I'll wait till I have a second crash then, I've done plenty of waiting I can stand to wait a bit longer :)

When that happens, should I post in this thread again with the updated report & app result, or would you rather I made a new one?

Edit: I'll prob wait till i have 3, if that will be more helpful. I guess I could start leaving my computer on desktop all day to see if I can 'encourage' some more BSOD's, or would that be a bad idea, because they might not be 'genuine'?

Im sorry you have to wait but sometimes it crashes so fast there isnt time to write the problem to the DMP.

When you get the next one post it here. All we really need is the new DMP file. The other things you collected will remain the same.

If you want to speed the process, do what you do when it crashes (ie if it crashes in a game, play that game)

Okidoke, that makes sense.
I'll try letting my pc stay on more, since there is no obvious specific task that causes the BSOD's.

Thanks for your prompt replies. See you in a week or less hopefully. :)


Dan,

Yeoman said:

Okidoke, that makes sense.
I'll try letting my pc stay on more, since there is no obvious specific task that causes the BSOD's.

Thanks for your prompt replies. See you in a week or less hopefully. :)


Dan,

Good job and good luck Dan. Keep us in the loop

Sorry for the long gap between posts, I've been snowed under with uni stuff, and was waiting for a 'clear patch'.

I've had some more BSOD's since the last time i posted. Three to be precise. Two more IRQL_NOT_LESS_OR_EQUAL, and one Page_Fault_in_nonpaged_Area (that's the first time I had one of those, I had it whilst I was installing a computer game, but it installed fine on a second attempt.) I don't know if that is related to the problem that's been causing all the NOT_LESS_OR_EQUAL bluescreens, or not, but I thought I'd mention it.

I've attached a zip file containing the updated perfmon report and the other info gathering programme. I'll update the first post too, so there's no confusion.

All the information I placed in the first post is still relevant, and correct. My situation is still the same however, I travel to uni each week day, and occasionally at the week ends, I hope you'll bear with me, I'll be able to respond to any replies at uni, and to ask questions, but it might take me slightly longer to be able to follow any commands/ fixes.

Problem Devices:

Code:

Universal Serial Bus (USB) Controller	PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&108ABD8A&0&00E4	The drivers for this device are not installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&DDEC341&0&00E1	The drivers for this device are not installed.

Make sure you get the drivers from ASUS - Motherboards- ASUS P8P67 through OS: Windows 7 64bit under USB.


Also, it does not appear all Windows updates have been installed. Make sure you install all Windows updates including optional updates but excluding driver updates through Windows updates. Driver updates should be obtained from the manufacturer of the driver or from your motherboard support site.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Yeoman\Yeoman BSOD seven forums (second zip)\Windows_NT6_BSOD_jcgriff2\032912-14289-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a8650
Debug session time: Thu Mar 29 04:44:46.289 2012 (UTC - 6:00)
System Uptime: 0 days 3:32:54.476
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88003310000, 0, fffff800033307f4, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PfpFlushBuffers+294 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
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:
Arg1: fffff88003310000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033307f4, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003112100
 fffff88003310000 

FAULTING_IP: 
nt!PfpFlushBuffers+294
fffff800`033307f4 488b4d00        mov     rcx,qword ptr [rbp]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880087988a0 -- (.trap 0xfffff880087988a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000006007
rdx=fffff8a0033db178 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033307f4 rsp=fffff88008798a30 rbp=fffff88003310000
 r8=0000000000000001  r9=0000000000000717 r10=fffff8a0033d4000
r11=fffff8a0033da578 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!PfpFlushBuffers+0x294:
fffff800`033307f4 488b4d00        mov     rcx,qword ptr [rbp] ss:0018:fffff880`03310000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8d25c to fffff80002ee0d40

STACK_TEXT:  
fffff880`08798738 fffff800`02e8d25c : 00000000`00000050 fffff880`03310000 00000000`00000000 fffff880`087988a0 : nt!KeBugCheckEx
fffff880`08798740 fffff800`02edee6e : 00000000`00000000 fffff880`03310000 00000000`00002900 fffffa80`07aef000 : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`087988a0 fffff800`033307f4 : 00000000`00000656 fffffa80`00000716 00000000`00000000 fffffa80`08a8ae48 : nt!KiPageFault+0x16e
fffff880`08798a30 fffff800`03351e80 : fffffa80`0adcab01 00000000`00000080 fffffa80`06cef040 fffff800`03067da8 : nt!PfpFlushBuffers+0x294
fffff880`08798ad0 fffff800`0317af7a : ffffffff`ff676980 fffffa80`0adcab60 fffff880`08798c70 fffffa80`0adcab60 : nt!PfTLoggingWorker+0xe0
fffff880`08798c00 fffff800`02ed19c6 : fffff800`03055e80 fffffa80`0adcab60 fffff800`03063cc0 fffff880`01266384 : nt!PspSystemThreadStartup+0x5a
fffff880`08798c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PfpFlushBuffers+294
fffff800`033307f4 488b4d00        mov     rcx,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PfpFlushBuffers+294

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x50_nt!PfpFlushBuffers+294

BUCKET_ID:  X64_0x50_nt!PfpFlushBuffers+294

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Yeoman\Yeoman BSOD seven forums (second zip)\Windows_NT6_BSOD_jcgriff2\032412-29484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`0305c650
Debug session time: Sat Mar 24 06:28:41.842 2012 (UTC - 6:00)
System Uptime: 0 days 2:41:44.028
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffff, 2, 1, fffff80002ec5932}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

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: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, 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: fffff80002ec5932, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
 ffffffffffffffff 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ec5932 48890a          mov     qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  fffff88003d1a3a0 -- (.trap 0xfffff88003d1a3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003d1a5e0
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec5932 rsp=fffff88003d1a530 rbp=fffff88003d1a5c0
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8006bfe4b0
r11=fffff800030c9ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ec5932 48890a          mov     qword ptr [rdx],rcx ds:0202:ffffffff`ffffffff=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e942e9 to fffff80002e94d40

STACK_TEXT:  
fffff880`03d1a258 fffff800`02e942e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03d1a260 fffff800`02e92f60 : 00000000`00000000 fffffa80`0a0d6b60 ffffffff`fffffd80 fffffa80`0182cbe0 : nt!KiBugCheckDispatch+0x69
fffff880`03d1a3a0 fffff800`02ec5932 : 00000000`00000000 00000000`00000001 fffffa80`06cefc68 00000000`00000001 : nt!KiPageFault+0x260
fffff880`03d1a530 fffff800`02ea46cd : fffffa80`0182cbe0 00000000`00000000 fffff880`03d1a5c0 fffffa80`06cefb60 : nt!KxWaitForLockOwnerShip+0x12
fffff880`03d1a560 fffff800`02ec6ee7 : 00000000`00000000 fffff680`00038eb8 00000000`00000000 00000000`00000001 : nt!MiInsertPageInFreeOrZeroedList+0x55d
fffff880`03d1a670 fffff800`02ec6137 : 00000000`00000000 fffff680`00038fb0 fffffa80`09ee9b30 00000000`00000000 : nt!MiDeletePteRun+0x4ed
fffff880`03d1a820 fffff800`02e814bf : fffffa80`00000000 00000000`07370fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`03d1a9e0 fffff800`02e93fd3 : ffffffff`ffffffff 00000000`027fe720 00000000`027fe6e8 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`03d1aae0 00000000`773514fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`027fe658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773514fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ec5932 48890a          mov     qword ptr [rdx],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12

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

1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Antivirus Software... Drivers...
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...

When you have a chance, test for Windows corruption (not likely given this is a fairly fresh install, but sometimes installation DVDs can be faulty) and hardware problems:

• If you are overclocking any hardware, please stop.
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

I realize these are a lot of steps to do in your limited time, so do the best you can. Report back as you proceed, and whatever pace works for you, I'll be checking on the thread as you go, even if it takes a few weeks or more.

Thank you very much for your reply. I'm heading off to university shortly, I'll start on some of these things when I get back tonight, (I'll most likely do the drivers tonight, and windows update).

One thing I will briefly mention; I have afaik, downloaded and ran all the drivers for my motherboard previously. I believe I ran the USB driver twice, although it doesn't seem to have worked, but perhaps I did something incorrect. I'll double check later tonight ofc, and if I have no luck with the ones from the asus website, I could always see if there is something on the motherboard driver disk I've been missing on the website (although I understand using the manufacturers website is always recommended over the disk).

Thank you again, I'll repost later tonight, detailing what I have done, and anything else of interest.


Dan,

Alright, sounds good. There are two sets of drivers in the USB section of your motherboard support driver downloads. One is for the controllers, and the other is for the ports themselves. Is it possible you only installed one of these sets of drivers the first time?

Let us know if you need any help as you go. Best of luck!