Windows 7 Random bluescreens, can't understand the error

SneakyToe

New Member
Joined
Jul 24, 2011
Alirght, here's the thing.

The error started like 2 hours ago when I booted my computer which I used earlier today and it worked just fine.

I've tried reinstalling the OS, switching HDD, using 1 RAM that I know that works.
Though, it works in Safe Mode, which I think is very strange, I can't really understand the error, might be hardware but not sure. I formatted all the disks in-case if it were something with them but still bluescreens.

Computer Specs:
ATI Radeon HD 5770 1GB
Corsair 4GB RAM 1600MHz
Windows 7 64-bit ULTIMATE
ACE 500W
Samsung 500GB 7200RPM

The .dmp's is in a ZIP attached below, thankful for help!
 

Attachments

  • Temp.rar
    100.6 KB · Views: 177
Last edited:
SneakyToe;
Hello and welcome to the forums. It's Sunday and I suspect most of the real BSOD experts are resting up or otherwise occupied.
So....
Start with this
Update this driver for your Realtek Network Adapter
Rt64win7.sys 2/26/2009
Try here Realtek see if your card is listed, if not try Google, but you need to get that addressed first.
Other than that I didn't see any drivers that are likely suspects but I did notice you haven't updated to Sp1 yet or at least it doesn't appear so. So you might want to hit your new fresh install with that and while one of your BSODs did mention an issue with USBPort.sys, I don't suspect that is the actual issue however it may be a problem with something that's attached to one of your USB ports so you might want to remove any such devices for the time being.
DUMP:
Code:
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, fffffa8004a8b050}
[COLOR=#B22222][U][B]Probably caused by : USBPORT.SYS [/B][/U][/COLOR]( USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2 )
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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa8004a8b050, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0e0e0
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
+3038313630643062
fffffa80`04a8b050 0300            add     eax,dword ptr [rax]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff80000b9c7c0 -- (.trap 0xfffff80000b9c7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004a8b1a0
rdx=fffffa8004a8d280 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa8004a8b050 rsp=fffff80000b9c958 rbp=0000000000000000
 r8=fffffa8005bca610  r9=00000000ffffffff r10=0000000000000008
r11=fffff80000b9c930 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffffa80`04a8b050 0300            add     eax,dword ptr [rax] ds:0007:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800028d5ca9 to fffff800028d6740
STACK_TEXT:  
fffff800`00b9c678 fffff800`028d5ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c680 fffff800`028d4920 : fffffa80`05bca9a8 fffffa80`05bca610 fffffa80`0516cf30 fffff880`03e26876 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c7c0 fffffa80`04a8b050 : fffff880`03e4508e fffffa80`00000000 fffffa80`05bca610 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c958 fffff880`03e4508e : fffffa80`00000000 fffffa80`05bca610 00000000`00000000 fffffa80`05168770 : 0xfffffa80`04a8b050
fffff800`00b9c960 fffff800`028219ce : fffffa80`04f3d5b8 fffff800`0281efb9 00000000`00000002 00000000`de686e08 : USBPORT!USBPORT_Core_ProcessScatterGatherList+0x5b2
fffff800`00b9ca10 fffff800`0282213d : fffffa80`04a8b050 fffffa80`04c68040 fffffa80`0467fe00 00000000`00000000 : hal!HalpAllocateAdapterCallback+0x146
fffff800`00b9cab0 fffff800`0282171f : fffffa80`04f3d570 00000000`00000008 fffffa80`04c68040 fffffa80`05481160 : hal!HalAllocateAdapterChannel+0x101
fffff800`00b9caf0 fffff800`02821420 : fffffa80`04a8b050 00000000`00000008 fffffa80`000000a0 fffff880`03e46dd7 : hal!HalBuildScatterGatherList+0x2f3
fffff800`00b9cb60 fffff880`03e4552e : fffffa80`04a8b050 00000000`00000000 fffffa80`04a8bd20 fffffa80`05bca610 : hal!HalGetScatterGatherList+0x44
fffff800`00b9cbc0 fffff880`03e42e86 : fffffa80`052a23e0 fffffa80`04a8b050 fffff800`028213dc fffffa80`04a8b1a0 : USBPORT!USBPORT_Core_iMapTransfer+0x24a
fffff800`00b9cc40 fffff880`03e33f89 : fffffa80`04a8b050 00000000`00000000 fffffa80`04a8bd02 fffffa80`04a8bd20 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x296
fffff800`00b9cca0 fffff800`028e1bfc : fffff800`02a50e80 fffffa80`04a8bd20 fffffa80`04a8bd38 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ccd0 fffff800`028deeea : fffff800`02a50e80 fffff800`02a5ec40 00000000`00000000 fffff880`03e33db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_IP: 
USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
fffff880`03e4508e 8be8            mov     ebp,eax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME:  USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07
FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
Followup: MachineOwner
 
SneakyToe;
Hello and welcome to the forums. It's Sunday and I suspect most of the real BSOD experts are resting up or otherwise occupied.
So....
Start with this
Update this driver for your Realtek Network Adapter
Rt64win7.sys 2/26/2009
Try here Realtek see if your card is listed, if not try Google, but you need to get that addressed first.
Other than that I didn't see any drivers that are likely suspects but I did notice you haven't updated to Sp1 yet or at least it doesn't appear so. So you might want to hit your new fresh install with that and while one of your BSODs did mention an issue with USBPort.sys, I don't suspect that is the actual issue however it may be a problem with something that's attached to one of your USB ports so you might want to remove any such devices for the time being.
DUMP:
Code:
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, fffffa8004a8b050}
[COLOR=#B22222][U][B]Probably caused by : USBPORT.SYS [/B][/U][/COLOR]( USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2 )
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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa8004a8b050, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0e0e0
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
+3038313630643062
fffffa80`04a8b050 0300            add     eax,dword ptr [rax]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff80000b9c7c0 -- (.trap 0xfffff80000b9c7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004a8b1a0
rdx=fffffa8004a8d280 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa8004a8b050 rsp=fffff80000b9c958 rbp=0000000000000000
 r8=fffffa8005bca610  r9=00000000ffffffff r10=0000000000000008
r11=fffff80000b9c930 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffffa80`04a8b050 0300            add     eax,dword ptr [rax] ds:0007:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800028d5ca9 to fffff800028d6740
STACK_TEXT:  
fffff800`00b9c678 fffff800`028d5ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c680 fffff800`028d4920 : fffffa80`05bca9a8 fffffa80`05bca610 fffffa80`0516cf30 fffff880`03e26876 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c7c0 fffffa80`04a8b050 : fffff880`03e4508e fffffa80`00000000 fffffa80`05bca610 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c958 fffff880`03e4508e : fffffa80`00000000 fffffa80`05bca610 00000000`00000000 fffffa80`05168770 : 0xfffffa80`04a8b050
fffff800`00b9c960 fffff800`028219ce : fffffa80`04f3d5b8 fffff800`0281efb9 00000000`00000002 00000000`de686e08 : USBPORT!USBPORT_Core_ProcessScatterGatherList+0x5b2
fffff800`00b9ca10 fffff800`0282213d : fffffa80`04a8b050 fffffa80`04c68040 fffffa80`0467fe00 00000000`00000000 : hal!HalpAllocateAdapterCallback+0x146
fffff800`00b9cab0 fffff800`0282171f : fffffa80`04f3d570 00000000`00000008 fffffa80`04c68040 fffffa80`05481160 : hal!HalAllocateAdapterChannel+0x101
fffff800`00b9caf0 fffff800`02821420 : fffffa80`04a8b050 00000000`00000008 fffffa80`000000a0 fffff880`03e46dd7 : hal!HalBuildScatterGatherList+0x2f3
fffff800`00b9cb60 fffff880`03e4552e : fffffa80`04a8b050 00000000`00000000 fffffa80`04a8bd20 fffffa80`05bca610 : hal!HalGetScatterGatherList+0x44
fffff800`00b9cbc0 fffff880`03e42e86 : fffffa80`052a23e0 fffffa80`04a8b050 fffff800`028213dc fffffa80`04a8b1a0 : USBPORT!USBPORT_Core_iMapTransfer+0x24a
fffff800`00b9cc40 fffff880`03e33f89 : fffffa80`04a8b050 00000000`00000000 fffffa80`04a8bd02 fffffa80`04a8bd20 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x296
fffff800`00b9cca0 fffff800`028e1bfc : fffff800`02a50e80 fffffa80`04a8bd20 fffffa80`04a8bd38 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ccd0 fffff800`028deeea : fffff800`02a50e80 fffff800`02a5ec40 00000000`00000000 fffff880`03e33db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_IP: 
USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
fffff880`03e4508e 8be8            mov     ebp,eax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME:  USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07
FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_ProcessScatterGatherList+5b2
Followup: MachineOwner


Thankful for the answer, but sadly it didn't work.
Right when I loggon I get blue screen..

EDIT:

The error is gives me on the bluescreen is "MEMORY_MANAGEMENT"
 
Hi,

Could you grab cpu-z and post pics from each tab. Please include pics of each memory slot from within cpu-z too. Once we have these combined with your .dmp files will help us troubleshoot your problem.
 
Last edited:
Hi,

Could you grab cpu-z and post pics from each tab. Please include pics of each memory slot from within cpu-z too. Once we have these combined with your .dmp files will help us troubleshoot your problem.

Uploaded the screenies to mediafire, hopes that's OK. 50% of the tabs were just gray.. :s
Link Removed due to 404 Error
 
Ok, that doesn't help, cpu-z should show your memory timings. Could you post a pic of the spd tab if it actually shows something and isn't grayed out.
Lets try SPECCY and hope that has better luck showing the details fo your machine. Onces speccy is loaded if you go to file and save as text file. Attach the text file which will contain the info required. Find the serial for your windows in the text and remove it before posting though.
 
Ok, that doesn't help, cpu-z should show your memory timings. Could you post a pic of the spd tab if it actually shows something and isn't grayed out.
Lets try SPECCY and hope that has better luck showing the details fo your machine. Onces speccy is loaded if you go to file and save as text file. Attach the text file which will contain the info required. Find the serial for your windows in the text and remove it before posting though.

All the tabs in SPECCY gives me the error: "Cannot initialise SPC dll"
FYI, I'm running in safe-mode. Can't run it in normal boot.
 
Ok that's why they're not running properly. Have you downloaded the latest Realtek drivers and tried to install them in safe mode?
 
Ok that's why they're not running properly. Have you downloaded the latest Realtek drivers and tried to install them in safe mode?

Not sure if I did.. I downloaded the second in the list here.
And the name of my network adapter is: RTL8168
 
SpeelingHi SneakyToe.

You want this Realtek Driver:

Realtek PCIe GBE Family Controller v7.046


Think the Realtek site is playing up at the moment (as it does!!). If it is for you, try again later.

EDIT!! The item (2nd down) you indicated does in fact contain an updated driver that you required. My apologies. The download(s) I referenced are the usual choice as they are a smaller download.
 
Last edited:
Really? Was it a USB mouse? Was it a mouse driver issue, or something physically wrong with the device or interface cable?
 
I meant to post more info, turned out not to be the mouse. A few hours later the problem came back. A bios update and setting the voltage and timings manually seems to have fixed the OP's problems. The over laying problem only reared it's head when the OP started playing the game League of Legends. I apologize for my previous solved post, completely slipped my mind about editing it.

I took quite awhile to gather all the required info needed.
 
Back
Top Bottom