New
#1
BSOD Windows 7 Home Premium 64Bit
Hi I get random BSOD no idea why sometimes the computer won't have any for 1-2 weeks then randomly in a blue moon i'll get them please help me
BSOD Windows 7 Home Premium 64Bit
-
-
New #2
These two blamed on your USBPORT.SYS. I would run system file check to verify and repair and read this USB Driver - General Fix for Problems
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052911-28203-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;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16792.amd64fre.win7_gdr.110408-1633 Machine Name: Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50 Debug session time: Sat May 28 22:03:50.812 2011 (GMT-4) System Uptime: 0 days 0:41:13.000 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} Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_RecordOcaTransferData+53 ) 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: +5d35952f0379dda8 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff80000ba2ae8 -- (.exr 0xfffff80000ba2ae8) ExceptionAddress: fffff88003e53467 (USBPORT!USBPORT_Core_RecordOcaTransferData+0x0000000000000053) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff80000ba2b90 -- (.trap 0xfffff80000ba2b90) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80056520a0 rbx=0000000000000000 rcx=fffffa800565d050 rdx=00000000000003e8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88003e53467 rsp=fffff80000ba2d20 rbp=000000000000001f r8=fffffa8003f22c00 r9=0000000000000000 r10=0000000000000000 r11=fffffa800565d1a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc USBPORT!USBPORT_Core_RecordOcaTransferData+0x53: fffff880`03e53467 884344 mov byte ptr [rbx+44h],al ds:6500:00000000`00000044=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002eb142e to fffff80002eb96d0 STACK_TEXT: fffff800`00ba1bd8 fffff800`02eb142e : 00000000`00000000 fffffa80`056011a0 fffff800`00ba2350 fffff800`02ee66ec : nt!KeBugCheck fffff800`00ba1be0 fffff800`02edf49d : fffff800`030c7b7c fffff800`03001e3c fffff800`02e49000 fffff800`00ba2ae8 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`00ba1c10 fffff800`02ee6b10 : fffff800`03008a38 fffff800`00ba1c88 fffff800`00ba2ae8 fffff800`02e49000 : nt!RtlpExecuteHandlerForException+0xd fffff800`00ba1c40 fffff800`02ef3a6f : fffff800`00ba2ae8 fffff800`00ba2350 fffff800`00000000 fffffa80`0565d050 : nt!RtlDispatchException+0x410 fffff800`00ba2320 fffff800`02eb8d42 : fffff800`00ba2ae8 fffffa80`03f22c00 fffff800`00ba2b90 fffffa80`0565d050 : nt!KiDispatchException+0x16f fffff800`00ba29b0 fffff800`02eb6e9f : fffff800`00ba2b90 fffffa80`0565d002 fffffa80`0565d000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2 fffff800`00ba2b90 fffff880`03e53467 : fffffa80`05e66010 fffffa80`0565d1a0 fffffa80`03f22e00 fffffa80`05c0b8a0 : nt!KiInvalidOpcodeFault+0x11f fffff800`00ba2d20 fffff880`03e4ef03 : fffffa80`0565d1a0 fffffa80`0565d050 fffffa80`03f22c00 fffffa80`0565d1a0 : USBPORT!USBPORT_Core_RecordOcaTransferData+0x53 fffff800`00ba2d50 fffff880`03e4fab7 : fffffa80`03f22c02 fffffa80`05e50260 00000000`ffffffff fffffa80`0565dea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x33f fffff800`00ba2e30 fffff880`03e4d64f : fffffa80`0565dea8 fffffa80`0565d1a0 fffffa80`0565e040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7 fffff800`00ba2e90 fffff880`03e3ef89 : fffffa80`0565d050 00000000`00000000 fffffa80`0565de02 fffffa80`0565dea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3 fffff800`00ba2ed0 fffff800`02ec4c0c : fffff800`03033e80 fffffa80`0565dea8 fffffa80`0565dec0 00000000`0000fffe : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff800`00ba2f00 fffff800`02ebf865 : 00000000`00000000 fffffa80`03b83b60 00000000`00000000 fffff880`03e3edb0 : nt!KiRetireDpcList+0x1bc fffff800`00ba2fb0 fffff800`02ebf67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`03199b70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: USBPORT!USBPORT_Core_RecordOcaTransferData+53 fffff880`03e53467 884344 mov byte ptr [rbx+44h],al SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: USBPORT!USBPORT_Core_RecordOcaTransferData+53 FOLLOWUP_NAME: MachineOwner MODULE_NAME: USBPORT IMAGE_NAME: USBPORT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07 FAILURE_BUCKET_ID: X64_0x1E_USBPORT!USBPORT_Core_RecordOcaTransferData+53 BUCKET_ID: X64_0x1E_USBPORT!USBPORT_Core_RecordOcaTransferData+53 Followup: MachineOwner ---------
-
New #3
Found 2 crashes 3 days apart in the provided info.
Before I go any further here, could I ask what usb devices are connected to this computer?
as even though the system is blaming the usbport.sys on both crashes this is a core file and I doubt the actual cause.
At any rate the most obvious problem pointed too here appears to be memory corruption, the best way to test that is with memtest86 by allowing it to run overnight or for 5-7 passes.
RAM - Test with Memtest86+ <---tutorial on using memtest
at first glance the crash seems to be indicating memory corruption though making that the first best step just to ensure this isn't a hardware problem.
Code:DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: fffffa801f7fd68c, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88003e2d452, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f20e0 fffffa801f7fd68c CURRENT_IRQL: 2 FAULTING_IP: USBPORT!USBPORT_IsrDpc+156 fffff880`03e2d452 8a93ec04001a mov dl,byte ptr [rbx+1A0004ECh] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0xD1 PROCESS_NAME: javaw.exe TRAP_FRAME: fffff88002f92d10 -- (.trap 0xfffff88002f92d10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa800580d0c0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88003e2d452 rsp=fffff88002f92ea0 rbp=fffffa80057fd050 r8=fffffa80057fd1a0 r9=fffff78000000320 r10=fffffa8004e3d060 r11=00000000c3c32270 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc USBPORT!USBPORT_IsrDpc+0x156: fffff880`03e2d452 8a93ec04001a mov dl,byte ptr [rbx+1A0004ECh] ds:5380:00000000`1a0004ec=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002eb9c69 to fffff80002eba700 STACK_TEXT: fffff880`02f92bc8 fffff800`02eb9c69 : 00000000`0000000a fffffa80`1f7fd68c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`02f92bd0 fffff800`02eb88e0 : 00000000`00000000 fffffa80`057fd1a0 ffffffff`fffffff7 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`02f92d10 fffff880`03e2d452 : fffffa80`057fd1a0 00000000`00000000 00000000`00000000 00000000`07fb4000 : nt!KiPageFault+0x260 fffff880`02f92ea0 fffff800`02ec5c0c : fffff880`02f63180 fffffa80`057fd050 fffffa80`057fe178 00000000`00000000 : USBPORT!USBPORT_IsrDpc+0x156 fffff880`02f92f00 fffff800`02ec0865 : fffff8a0`0a5a4c32 fffffa80`04e3d060 00000000`00000000 fffff880`03e2d2fc : nt!KiRetireDpcList+0x1bc fffff880`02f92fb0 fffff800`02ec067c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`08732be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !USBPORT 8 errors : !USBPORT (fffff88003e2d447-fffff88003e2d47f) fffff88003e2d440 44 6c 6b 48 89 4a 18 *4c 89 7a 08 48 8b 83 08 *45 DlkH.J.L.z.H...E fffff88003e2d450 00 00 8a 93 ec 04 00 *1a 4c 8b 80 d0 02 00 00 *61 ........L......a fffff88003e2d460 ea 02 80 e2 01 4d 85 *c8 74 16 48 8b 8b 00 04 *61 .....M..t.H....a fffff88003e2d470 00 41 ff d0 49 b9 20 *1b 00 00 80 f7 ff ff 8b *11 .A..I. ......... MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
-
New #4
-
New #5
the system file check as suggested above my post by zigzag is also very quick to do and couldn't hurt anything.
-
-
New #7
Ok completed the scan and....
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>
-
New #8
in that case proceed with the memory check overnight, after we've either confirmed or eliminated it as the problem we can continue from there.
-
New #9
-
New #10
Ok I ran the memory test overnight and I got 406 errors...
So I have a memory issue what do you guys recomend?
Quote
Related Discussions