Problems with Random BSODs

#1
Hey all. I am curious to see if any one can help me with my problem. I have been having random BSODs that are unpredictable and that are quit often. The error message that I am having when i restart my computer is as follows;


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000005251
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF880049437CF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\022610-26531-01.dmp
C:\Users\Lordice\AppData\Local\Temp\WER-58421-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement

offline:
C:\Windows\system32\en-US\erofflps.txt



I really don't know what to make of this so if any one could help me out it would be greatly appreciated. Thanks!
 


Mitchell_A

Essential Member
#2
Hey, welcome to the forums :)
Could you post some system specs here for us, please?
 


#3
My system specs are as follows;

Biostar TP45D2-A7 motherboard
4 gigs of DDR2 (1066MHz)
GTX 275 video card
Intel Core 2 Duo CPU 2.4GHz
250GB Hard Drive
600GB Hard Drive
1Tera Hard Drive
 


ickymay

New Member
#4
My system specs are as follows;

Biostar TP45D2-A7 motherboard
4 gigs of DDR2 (1066MHz)
GTX 275 video card
Intel Core 2 Duo CPU 2.4GHz
250GB Hard Drive
600GB Hard Drive
1Tera Hard Drive
to gather more information on the crashes we need to analyze your BSOD dump files, please can you zip them and upload them here ?

to setup minidumps and stop the auto restart ...............
  1. Go to Start and type in sysdm.cpl and press Enter
  2. Click on the Advanced tab
  3. Click on the Startup and Recovery Settings button
  4. Ensure that Automatically restart is unchecked
  5. Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
  6. Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where to find the .dmp files afterwards !
  7. Click OK twice to exit the dialogs, then reboot for the changes to take effect.
 


#5
Ok i have it setup like u asked but i do not know where the file is located that you want me to upload.
 


ickymay

New Member
#6
Ok i have it setup like u asked but i do not know where the file is located that you want me to upload.
5. Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where to find the .dmp files afterwards !

that is most likely for you going to be C:\windows\Minidump .........

you will need to copy the file out into a place with less security and zip it then upload here :)

if these settings where not in place for your last crash you may well have to wait until your next crash before a file is generated in that folder ?
 


#7
Ok here are the minidumps.
 


Attachments

ickymay

New Member
#8
Ok here are the minidumps.
Oo well these 22 dumps all agree and point to one specific driver :razz:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5251, 2, 1, fffff88004e2d7cf}

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

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

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

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: 0000000000005251, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004e2d7cf, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb0e0
0000000000005251

CURRENT_IRQL: 2

FAULTING_IP:
WUSB54Gv4x64+2d7cf
fffff880`04e2d7cf c6401801 mov byte ptr [rax+18h],1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: chrome.exe

TRAP_FRAME: fffff80000ba27f0 -- (.trap 0xfffff80000ba27f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000005239 rbx=0000000000000000 rcx=fffffa8005065ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004e2d7cf rsp=fffff80000ba2980 rbp=0000000000000000
r8=fffffa80062e0e00 r9=0000000000000000 r10=fffffa800503aa80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04e2d7cf c6401801 mov byte ptr [rax+18h],1 ds:fe00:00000000`00005251=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cc4469 to fffff80002cc4f00

STACK_TEXT:
fffff800`00ba26a8 fffff800`02cc4469 : 00000000`0000000a 00000000`00005251 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba26b0 fffff800`02cc30e0 : fffffa80`04919b60 fffffa80`059d3e70 fffffa80`049196e0 fffff800`02cd0326 : nt!KiBugCheckDispatch+0x69
fffff800`00ba27f0 fffff880`04e2d7cf : fffffa80`05066000 fffffa80`04b751a0 fffffa80`0503aa80 fffffa80`059d3e70 : nt!KiPageFault+0x260
fffff800`00ba2980 fffffa80`05066000 : fffffa80`04b751a0 fffffa80`0503aa80 fffffa80`059d3e70 fffffa80`05066000 : WUSB54Gv4x64+0x2d7cf
fffff800`00ba2988 fffffa80`04b751a0 : fffffa80`0503aa80 fffffa80`059d3e70 fffffa80`05066000 fffff880`03c01f4e : 0xfffffa80`05066000
fffff800`00ba2990 fffffa80`0503aa80 : fffffa80`059d3e70 fffffa80`05066000 fffff880`03c01f4e fffffa80`04fe3cf0 : 0xfffffa80`04b751a0
fffff800`00ba2998 fffffa80`059d3e70 : fffffa80`05066000 fffff880`03c01f4e fffffa80`04fe3cf0 00000000`00005239 : 0xfffffa80`0503aa80
fffff800`00ba29a0 fffffa80`05066000 : fffff880`03c01f4e fffffa80`04fe3cf0 00000000`00005239 fffffa80`051c0050 : 0xfffffa80`059d3e70
fffff800`00ba29a8 fffff880`03c01f4e : fffffa80`04fe3cf0 00000000`00005239 fffffa80`051c0050 fffff880`04e2da1a : 0xfffffa80`05066000
fffff800`00ba29b0 fffff880`04e2d96a : fffffa80`05052000 fffffa80`059d2b90 fffffa80`04fe3cf0 fffff880`04f8448f : USBPORT!MPf_SubmitTransfer+0x96
fffff800`00ba2a00 fffffa80`05052000 : fffffa80`059d2b90 fffffa80`04fe3cf0 fffff880`04f8448f fffffa80`062e0f50 : WUSB54Gv4x64+0x2d96a
fffff800`00ba2a08 fffffa80`059d2b90 : fffffa80`04fe3cf0 fffff880`04f8448f fffffa80`062e0f50 fffffa80`059d2b90 : 0xfffffa80`05052000
fffff800`00ba2a10 fffffa80`04fe3cf0 : fffff880`04f8448f fffffa80`062e0f50 fffffa80`059d2b90 00000000`00000008 : 0xfffffa80`059d2b90
fffff800`00ba2a18 fffff880`04f8448f : fffffa80`062e0f50 fffffa80`059d2b90 00000000`00000008 fffffa80`051c0050 : 0xfffffa80`04fe3cf0
fffff800`00ba2a20 fffffa80`04fe3cf0 : 00000000`00000000 fffff880`00ed922b 0000057f`fa62c188 0000057f`fa6c0ad8 : hidusb!HumReadReport+0x13f
fffff800`00ba2a70 00000000`00000000 : fffff880`00ed922b 0000057f`fa62c188 0000057f`fa6c0ad8 fffffa80`062e0ef8 : 0xfffffa80`04fe3cf0


STACK_COMMAND: kb

FOLLOWUP_IP:
WUSB54Gv4x64+2d7cf
fffff880`04e2d7cf c6401801 mov byte ptr [rax+18h],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME: WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb

FAILURE_BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

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

0: kd> lmvm WUSB54Gv4x64
start end module name
fffff880`04e00000 fffff880`04e52000 WUSB54Gv4x64 T (no symbols)
Loaded symbol image file: WUSB54Gv4x64.sys
Image path: \SystemRoot\system32\DRIVERS\WUSB54Gv4x64.sys
Image name: WUSB54Gv4x64.sys
Timestamp: Wed Dec 27 09:41:31 2006 (45923FCB)
CheckSum: 00053254
ImageSize: 00052000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
this driver is the problem
WUSB54Gv4x64.sys WUSB54Gv4x64.sys+2d7cf fffff880`04e00000 fffff880`04e52000 0x00052000 0x45923fcb 27/12/2006 09:41:31
is a component of your Ralink 802.11 USB Wireless Adapter and definately needs updating ?

you also have three other drivers that you need to try updating
RTCore64.sys fffff880`06540000 fffff880`06546000 0x00006000 0x42941d90 25/05/2005 06:39:12
VMNetSrv.sys fffff880`0fe87000 fffff880`0fe9c000 0x00015000 0x45b74b9a 24/01/2007 12:05:46
amnpqjyn.SYS fffff880`0fe43000 fffff880`0fe87000 0x00044000 0x4936cd87 03/12/2008 18:18:47
RTCore64.sys is possibly a driver in this tool EVGA precision ?
VMNetSrv.sys is a Virtual Machine Network Service ?
amnpqjyn.SYS I have no idea ??

what AntiVirus and or third party firewall are you using ?
 


#9
I am using Avast Antivirus.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top