BSOD sometime on my system

Dave76 said:

Let's take a look at the BIOS voltage settings for your RAM.

Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.

Let us know if you have any questions.

Hello Dave76 !

I attached a jpg of my BIOS Voltage, thank for helping me too...

Don't forget that I didnt put back my 2 other memory module...

Hello writhziden, did you clean our thread, it seem to miss some post ??

Also, this morning I got another BSOD while playing a Flash Game (CityVille) on Facebook with Google Chrome

Here the dmp file...thanks

There was a server crash, so we are running from a backup, I believe. Many threads are missing posts or missing entirely if they were new.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\030112-36816-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03051670
Debug session time: Thu Mar  1 04:50:26.336 2012 (UTC - 7:00)
System Uptime: 0 days 11:26:22.193
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {fffff8e002f639bc, 2, 1, fffff80002fb7fa2}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15 )

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

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffff8e002f639bc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80002fb7fa2, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExFreePoolWithTag+212
fffff800`02fb7fa2 ff411c          inc     dword ptr [rcx+1Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff88002f929e0 -- (.trap 0xfffff88002f929e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000005fffffffa0 rbx=0000000000000000 rcx=fffff8e002f639a0
rdx=fffff88002f63180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb7fa2 rsp=fffff88002f92b70 rbp=0000000000000000
 r8=000000000000d430  r9=0000000000000000 r10=fffff80002e0c000
r11=000000000000054e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExFreePoolWithTag+0x212:
fffff800`02fb7fa2 ff411c          inc     dword ptr [rcx+1Ch] ds:fffff8e0`02f639bc=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e881e9 to fffff80002e88c40

STACK_TEXT:  
fffff880`02f92898 fffff800`02e881e9 : 00000000`0000000a fffff8e0`02f639bc 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f928a0 fffff800`02e86e60 : 00000000`00000000 fffff880`00f2a051 fffffa80`046177e0 fffffa80`08bcba00 : nt!KiBugCheckDispatch+0x69
fffff880`02f929e0 fffff800`02fb7fa2 : fffffa80`03fb0820 fffff880`00f1dc9b fffffa80`04e12240 fffffa80`04618701 : nt!KiPageFault+0x260
fffff880`02f92b70 fffff800`02e75491 : fffffa80`046095c0 fffffa80`05368050 fffffa80`73556f49 fffff800`02fb7fbd : nt!ExFreePoolWithTag+0x212
fffff880`02f92c20 fffff800`02e8c021 : fffffa80`04618913 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x61
fffff880`02f92c60 fffff880`04013631 : fffffa80`05368050 fffffa80`04617600 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02f92d50 fffff880`04013b0f : fffffa80`07decc02 fffffa80`04618720 00000000`ffffffff fffffa80`05368eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f92e30 fffff880`0401166f : fffffa80`05368eb0 fffffa80`053681a0 fffffa80`05369050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f92e90 fffff880`04002f89 : fffffa80`05368050 00000000`00000000 fffffa80`05368e02 fffffa80`05368eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f92ed0 fffff800`02e940ac : fffff880`02f63180 fffffa80`05368eb0 fffffa80`05368ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f92f00 fffff800`02e8b765 : 00000000`00000000 fffffa80`0458ab60 00000000`00000000 fffff880`04002db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f92fb0 fffff800`02e8b57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`07de3e20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15
fffff880`04013631 440fb6db        movzx   r11d,bl

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xC5_2_USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15

BUCKET_ID:  X64_0xC5_2_USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15

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

Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\022812-24554-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`03046670
Debug session time: Tue Feb 28 21:10:56.303 2012 (UTC - 7:00)
System Uptime: 0 days 1:00:16.160
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\NuidFltr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NuidFltr.sys
*** ERROR: Module load completed but symbols could not be loaded for NuidFltr.sys
Probably caused by : NuidFltr.sys ( NuidFltr+2899 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6462366164323833
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c368 -- (.exr 0xfffff80000b9c368)
ExceptionAddress: fffff88000ebc6eb (Wdf01000!FxObjectHandleGetPtrQI+0x000000000000003b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c410 -- (.trap 0xfffff80000b9c410)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000ee80b0 rbx=0000000000000000 rcx=fffffa80071ecb30
rdx=fffff80000b9c5f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000ebc6eb rsp=fffff80000b9c5a0 rbp=0000057ffad68188
 r8=0000057ff8e134c8  r9=0000000000001030 r10=0000000000000000
r11=fffff80000b9c608 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
Wdf01000!FxObjectHandleGetPtrQI+0x3b:
fffff880`00ebc6eb ff5028          call    qword ptr [rax+28h] ds:fffff880`00ee80d8=0049004300410052
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e755fe to fffff80002e7dc10

STACK_TEXT:  
fffff800`00b9b448 fffff800`02e755fe : fffffa80`50646641 fffff800`000001a4 fffff800`00b9bbc0 fffff800`02ea9830 : nt!KeBugCheck
fffff800`00b9b450 fffff800`02ea94fd : fffff800`0308771c fffff800`02fc4c30 fffff800`02e01000 fffff800`00b9c368 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b480 fffff800`02ea82d5 : fffff800`02fc80fc fffff800`00b9b4f8 fffff800`00b9c368 fffff800`02e01000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b4b0 fffff800`02eb9361 : fffff800`00b9c368 fffff800`00b9bbc0 fffff800`00000000 00000000`00001030 : nt!RtlDispatchException+0x415
fffff800`00b9bb90 fffff800`02e7d2c2 : fffff800`00b9c368 fffffa80`071ecb30 fffff800`00b9c410 0000057f`f8e134c8 : nt!KiDispatchException+0x135
fffff800`00b9c230 fffff800`02e7bbca : fffff800`02e01000 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c410 fffff880`00ebc6eb : 00000000`00000000 fffffa80`071eb820 fffffa80`071f14d0 fffffa80`071eba00 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c5a0 fffff880`00e8543f : 00000000`00000000 fffffa80`071eba05 fffffa80`071ecea0 fffff880`09a40660 : Wdf01000!FxObjectHandleGetPtrQI+0x3b
fffff800`00b9c610 fffff880`0597b899 : 00000000`00000000 0000057f`f8e134c8 0000057f`f8e134c8 fffff880`00e9ff38 : Wdf01000!imp_WdfDeviceGetIoTarget+0x7f
fffff800`00b9c650 00000000`00000000 : 0000057f`f8e134c8 0000057f`f8e134c8 fffff880`00e9ff38 fffff800`00b9c6d8 : NuidFltr+0x2899


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NuidFltr+2899
fffff880`0597b899 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  NuidFltr+2899

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NuidFltr

IMAGE_NAME:  NuidFltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9f9308

FAILURE_BUCKET_ID:  X64_0x1E_0_NuidFltr+2899

BUCKET_ID:  X64_0x1E_0_NuidFltr+2899

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

1. Points to USB devices...
2. Points to your mouse... Hmm... deja vu!

Start with the steps in USB Driver - General Fix for Problems.
Then use hard reset to resolve hardware and software issues (works on all computers, not just HP Pavilions) to reset your USB ports. They may have entered a power state to protect the system from a surge and need to be reset.

Hello writhziden,

I'm checking your tutorial about the "General Fix of USBDriver"

I was removing all my USB hardware from usb port and my computer close.. I was thinking I touch the power cord but no... it create a dump file, you can check it...

Also, in the tutorial it say, plug a wired mouse and keyboard , I can plug a keyboard wired I have the hole in the back of my computer but I can't for a mouse.. Idon't have any green hole for it..... should I stay connected my wireless hardware (mouse and kb) and do what they say in the tutorial ?

Humm do I really need to make the usb tutorial... and delete the INFCACHE.1 file since I got a clean install of Win 7....

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\030212-19219-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
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`03052670
Debug session time: Fri Mar  2 17:11:06.213 2012 (UTC - 7:00)
System Uptime: 1 days 12:19:02.070
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88000fb76eb, fffff880033a0ef8, fffff880033a0750}

Unable to load image \SystemRoot\system32\DRIVERS\point64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for point64.sys
*** ERROR: Module load completed but symbols could not be loaded for point64.sys
Probably caused by : point64.sys ( point64+186a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000fb76eb, The address that the exception occurred at
Arg3: fffff880033a0ef8, Exception Record Address
Arg4: fffff880033a0750, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Wdf01000!FxObjectHandleGetPtrQI+3b
fffff880`00fb76eb ff5028          call    qword ptr [rax+28h]

EXCEPTION_RECORD:  fffff880033a0ef8 -- (.exr 0xfffff880033a0ef8)
ExceptionAddress: fffff88000fb76eb (Wdf01000!FxObjectHandleGetPtrQI+0x000000000000003b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880033a0750 -- (.cxr 0xfffff880033a0750)
rax=fffff88000fe30b0 rbx=fffffa800717cb30 rcx=fffffa800717cb30
rdx=fffff880033a1180 rsi=0000057ff8e834c8 rdi=0000000000001000
rip=fffff88000fb76eb rsp=fffff880033a1130 rbp=0000057ff8e864c8
 r8=0000057ff8e834c8  r9=0000000000001000 r10=fffff80002e0d000
r11=fffff880033a1198 r12=fffffa8007179b50 r13=fffffa8007179b50
r14=fffff88000fdc800 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Wdf01000!FxObjectHandleGetPtrQI+0x3b:
fffff880`00fb76eb ff5028          call    qword ptr [rax+28h] ds:002b:fffff880`00fe30d8=0049004300410052
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
 ffffffffffffffff 

FOLLOWUP_IP: 
point64+186a
fffff880`0463e86a ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88000fb700c to fffff88000fb76eb

STACK_TEXT:  
fffff880`033a1130 fffff880`00fb700c : 0000057f`f8e834c8 00000000`00000000 fffffa80`07516010 fffffa80`07159600 : Wdf01000!FxObjectHandleGetPtrQI+0x3b
fffff880`033a11a0 fffff880`0463e86a : 00000000`00000000 fffff880`046441a0 fffffa80`07179e70 fffffa80`00000028 : Wdf01000!imp_WdfObjectDelete+0x88
fffff880`033a11f0 00000000`00000000 : fffff880`046441a0 fffffa80`07179e70 fffffa80`00000028 fffffa80`07179b30 : point64+0x186a


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  point64+186a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: point64

IMAGE_NAME:  point64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd37e38

STACK_COMMAND:  .cxr 0xfffff880033a0750 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_point64+186a

BUCKET_ID:  X64_0x7E_point64+186a

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

Microsoft IntelliPoint Filter Driver caused the latest crash. These are starting to point to a mouse related issue. Can you try a different mouse?

And yes, I would still proceed with the steps even though it is a clean install to make sure we are thorough.

I think the crash is when I unplug my Wieless receiver for my Mouse and Keyboard (but not sure) and I plug it to another USB Port... right now I have only this plugged in one USB Port..