BSODs on new computer build

mgorman87 · 28 Mar 2011

Please enable driver verifier
Driver Verifier - Enable and Disable

Code:

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


Loading Dump File [C:\Users\Mike\Downloads\bsod reports\Windows_NT6_BSOD_jcgriff2\032811-15958-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090e90
Debug session time: Sun Mar 27 10:16:56.481 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:55.011
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002eabd47}

Probably caused by : ntkrnlmp.exe ( nt!KeSetEventBoostPriority+3f )

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

2: 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: 0000000000000000, 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: fffff80002eabd47, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc0e8
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEventBoostPriority+3f
fffff800`02eabd47 f00fba2907      lock bts dword ptr [rcx],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003185720 -- (.trap 0xfffff88003185720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800991e4b8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eabd47 rsp=fffff880031858b0 rbp=fffffa8006b0fb60
 r8=0000000000000000  r9=0000000000000000 r10=fffff800030fe800
r11=0000000000001000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeSetEventBoostPriority+0x3f:
fffff800`02eabd47 f00fba2907      lock bts dword ptr [rcx],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecabe9 to fffff80002ecb640

STACK_TEXT:  
fffff880`031855d8 fffff800`02ecabe9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`031855e0 fffff800`02ec9860 : fffff8a0`01bd8808 fffff8a0`01bd8800 00000000`00000000 fffff880`02f64180 : nt!KiBugCheckDispatch+0x69
fffff880`03185720 fffff800`02eabd47 : 00000000`0019c6b1 00000000`00000246 fffff880`03185978 00000001`00000001 : nt!KiPageFault+0x260
fffff880`031858b0 fffff800`02ecdc3f : 00000000`00000001 00000000`00001000 00000000`00000000 00000000`00000000 : nt!KeSetEventBoostPriority+0x3f
fffff880`03185920 fffff800`02edf7fc : fffffa80`0991e440 00000000`00000001 fffff880`02f647f0 fffff8a0`01bd8808 : nt!ExpReleaseResourceForThreadLite+0x2bf
fffff880`03185980 fffff800`02eb128b : fffffa80`0a4edd80 fffff880`03185aa8 00000000`00000001 fffffa80`0a4edd80 : nt!CcUnpinFileDataEx+0x1ac
fffff880`03185a00 fffff800`02f0d12b : 00000000`00003ade fffff880`03185c58 00000000`00001000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0x8f
fffff880`03185a50 fffff800`02f109c6 : fffffa80`0a4f0fc8 00000000`00000001 fffffa80`00000001 00000000`00001000 : nt!CcFlushCache+0x64b
fffff880`03185b50 fffff800`02f11388 : fffff880`00000000 fffff880`03185c58 fffffa80`0a5900d0 fffff800`030ca178 : nt!CcWriteBehind+0x1c6
fffff880`03185c00 fffff800`02ed5a21 : fffffa80`06abb530 fffff800`031c1f01 fffff800`030ca180 fffffa80`00000000 : nt!CcWorkerThread+0x1c8
fffff880`03185cb0 fffff800`03168cce : 00000000`00000000 fffffa80`06b0fb60 00000000`00000080 fffffa80`06a1a040 : nt!ExpWorkerThread+0x111
fffff880`03185d40 fffff800`02ebcfe6 : fffff880`02f64180 fffffa80`06b0fb60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03185d80 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`03184cb0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeSetEventBoostPriority+3f
fffff800`02eabd47 f00fba2907      lock bts dword ptr [rcx],7

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeSetEventBoostPriority+3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f

BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f

Followup: MachineOwner

BDL101 · 29 Mar 2011

after turning on Driver Verifier my comp has only BSODed twice in the same situation - right before i type my password at start up. i have restarted my comp since a few times and there was no BSOD.

i kept my comp on all day to see if the Driver Verifier brought about any BSODs but other than the couple BSODs on start up there has been nothing.

hope this report shows something

thanks!

BDL101 · 30 Mar 2011

got another BSOD today while on the internet (driver verifier still on)

thanks

Jonathan_King · 31 Mar 2011

Hello,

It does seem as if hardware is the cause here. Go ahead and turn off driver verifier for now.

From the dumps I see your RAM is running at 800MHz, which is below the 2000(O.C.)/1600/1333/1066 guidelines for the motherboard. However, I don't know exactly what speed it is reporting; should I double that number because it's DDR3? If I did, that would put us at 1600MHz, the advertized speed of your RAM, and solidly within the acceptable speeds for your board.

I expect the latter is the case, but just to confirm, could you post a screenshot of the SPD tabs of one of your sticks? See here: CPUID - System & hardware benchmark, monitoring, reporting

The hardware will be tougher to diagnose, seeing as you've passed the tests we recommend already. I believe we are down to swapping out known-good components. We might as well start with the PSU; could you borrow one rated 500W or higher? Your current PSU is very good, though like any PSU it can fail.

Try running Furmark: Video Card - Stress Test with Furmark

If you can borrow a different video card, that would be great.

...Summary of the dumps:

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 30 08:53:51.845 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:52.000
*** ERROR: Module load completed but symbols could not be loaded for luafv.sys
Probably caused by : luafv.sys ( luafv+1988 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_VRF_BAD_IP_luafv+1988
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

BDL101 · 31 Mar 2011

Hi Jonathan_King, thanks for having a look!

ok driver verifier is off.

yes my RAM is DDR3 and i previously manually set it at 1600mhz in my bios. CPUID screen shot attached.

Ran Furmark for 20mins. there were no artifacts. it maxed out at 93c and averaged at 92c throughout the test. it usually idles around 40c.

unfortunately my last computers PSU died but ill see if my friend has a 500w PSU or not.

my old GPU is really old so not sure if it will work on this system and not sure if it was blown out when my last PSU blew. its a Radeon X850 XT 256MB. is that worth trying? not sure if my friends has anything better as his system is as old as my last one.

i think in general finding parts to swap in is going to be difficult. is that the only way to find a solution?

on a side note my comp hasn't BSODed today - it seems as if they are becoming less frequent oddly enough. also, so far my comp has never once BSODed while i play Battlefield Bad Company 2 on max visual settings - dont know if that says anything.

thanks for the help!

Jonathan_King · 31 Mar 2011

The key here is different, not necessarily better. Go ahead and try the old GPU; if it uses less power, it may even help us. If the card itself is bad, hopefully we will be able to spot that in the new BSODs you'll be getting.

BDL101 · 04 Apr 2011

hi,
it was a while before i had a chance to attempt switching GPU for my old GPU. when i went to do it i realized that it was not compatible with my board - not pci express. wrong slot shape all together. also my friend doesn't not have a large enough power supply and his card is too old as well. basically i have no way of switching in known working components so im at a bit of a loss if that is the last option for finding out the cause of these BSODs.

The BSODs are really infrequent now. maybe 1 ever 2-3 days at random times. i've only had 2 since my last post. once while shutting down and once while watching a movie and its been 2 days since the last one i think.

the reports are attached (driver verifier is off and nothing has change in my comp - software or hardware wise.)

thanks!

Jonathan_King · 05 Apr 2011

Call around to the local computer shops in your areas; ask about the return policies. Perhaps they would let you borrow a PSU and return it if that doesn't do the trick for you.

Do you have any USB devices attached?

...Summary of the dumps:

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Apr  3 07:43:13.881 2011 (UTC - 4:00)
System Uptime: 0 days 0:51:57.411
Probably caused by : portcls.sys ( portcls!CIrpStream::ReleaseUnmappingIrp+47 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_portcls!CIrpStream::ReleaseUnmappingIrp+47
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 31 19:26:28.697 2011 (UTC - 4:00)
System Uptime: 0 days 5:29:01.836
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

BDL101 · 05 Apr 2011

the only usb devices attached are my keyboard and mouse.
ill have a call around for parts.

thanks for the continued help.