Overclock.net › Forums › Video Games › PC Gaming › Blue screen upon loading Battlelog only? (Solved)
New Posts  All Forums:Forum Nav:

Blue screen upon loading Battlelog only? (Solved)

post #1 of 8
Thread Starter 
Ok, so this started happening earlier today, and now, I can't play BF3 online at all. EVERY time I load up the battlelog site, after signing in, just as the page is about to finish loading (any page), I get a BSOD. I have tried it in IE and Chrome, both do it. I made a system image a couple of days ago, and tried restoring via that. I also uninstalled Chrome, the BF3 plug in, Origin and BF3. Up reinstallation, same problem. Any ideas? The blue screen reads:

DRIVER_IRQL_NOT_EQUAL_NOR_SOMETHING

And then does the physical memory dump.

Only thing that has changed is I transferred my components to a new case. I did that two nights ago. It's worked fine up untill this afternoon. I can run 3dMark 11, go to any other webpage, do basically ANYTHING else on the computer, except load up battlelog.

Thanks.

Edit: Problem solved thanks to E-Peen! USB 3.0 controller.
Edited by Reloaded83 - 4/30/12 at 9:04am
post #2 of 8
Hi smile.gif

Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.

If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.
post #3 of 8
Thread Starter 
Minidump.zip 172k .zip file

Ok well I ran a debug and got this:
Warning: Long code and jibberish (Click to show)
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: fffffa8c07474c58, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006def51e, address which referenced memory


FAULTING_IP:
EtronXHCI+451e
fffff880`06def51e 418b8c818c000000 mov ecx,dword ptr [r9+rax*4+8Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff80003692229 to fffff80003692c80

STACK_TEXT:
fffff880`0d8f5c48 fffff800`03692229 : 00000000`0000000a fffffa8c`07474c58 00000000`00000002 00000000`00000000 : nt+0x7cc80
fffff880`0d8f5c50 00000000`0000000a : fffffa8c`07474c58 00000000`00000002 00000000`00000000 fffff880`06def51e : nt+0x7c229
fffff880`0d8f5c58 fffffa8c`07474c58 : 00000000`00000002 00000000`00000000 fffff880`06def51e ffffe0cb`6f87f90c : 0xa
fffff880`0d8f5c60 00000000`00000002 : 00000000`00000000 fffff880`06def51e ffffe0cb`6f87f90c 00000000`00000000 : 0xfffffa8c`07474c58
fffff880`0d8f5c68 00000000`00000000 : fffff880`06def51e ffffe0cb`6f87f90c 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
EtronXHCI+451e
fffff880`06def51e 418b8c818c000000 mov ecx,dword ptr [r9+rax*4+8Ch]

SYMBOL_NAME: EtronXHCI+451e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: EtronXHCI

IMAGE_NAME: EtronXHCI.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

I was directed to check my drivers. So I looked in device manager, and I have a ? for Other Devices and it's for the SM Bus Controller. So, I went to the ASRock website to download the Intel chipset drivers, as from what I read that's what it refers to, and when I went to open the drivers, it blue screened again. The most recent dump file in the zip is of that crash. Thanks!
post #4 of 8
1. All are D1 bugchecks with the culprit listed as EtronXHCI.sys (Etron USB 3.0 Extensible Host Controller Driver). Uninstall this driver temporarily for troubleshooting reasons as it's OEM (on the disc) and not available for update on Etron's site.

2. dtsoftbus01.sys is listed in your loaded drivers list, this is Daemon Tools and is a very popular cause of BSODs, especially in Win7. Please fully uninstall Daemon Tools. Optional virutalization programs aside from Daemon Tools that also don't use sptd.sys as well are: Power ISO, ImgBurn, etc.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\BSOD\Downloads\043012-16723-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\MS 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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03616000 PsLoadedModuleList = 0xfffff800`0385a650
Debug session time: Mon Apr 30 03:24:14.531 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:39.811
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8c07474c58, 2, 0, fffff88006def51e}

Unable to load image \SystemRoot\System32\Drivers\EtronXHCI.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EtronXHCI.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
Probably caused by : EtronXHCI.sys ( EtronXHCI+451e )

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

2: 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: fffffa8c07474c58, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006def51e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c4100
 fffffa8c07474c58 

CURRENT_IRQL:  2

FAULTING_IP: 
EtronXHCI+451e
fffff880`06def51e 418b8c818c000000 mov     ecx,dword ptr [r9+rax*4+8Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  audiodg.exe

TRAP_FRAME:  fffff8800d8f5d90 -- (.trap 0xfffff8800d8f5d90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000002fffffffd rbx=0000000000000000 rcx=0000000000000024
rdx=00000000000000c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006def51e rsp=fffff8800d8f5f20 rbp=fffffa8007473360
 r8=0000000000000000  r9=fffffa8007474bd8 r10=0000000000000000
r11=00000000000000c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
EtronXHCI+0x451e:
fffff880`06def51e 418b8c818c000000 mov     ecx,dword ptr [r9+rax*4+8Ch] ds:fffffa8c`07474c58=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003692229 to fffff80003692c80

STACK_TEXT:  
fffff880`0d8f5c48 fffff800`03692229 : 00000000`0000000a fffffa8c`07474c58 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d8f5c50 fffff800`03690ea0 : fffff880`0d8f5f78 fffff8a0`02ca4830 fffffa80`06e3f660 fffffa80`07473360 : nt!KiBugCheckDispatch+0x69
fffff880`0d8f5d90 fffff880`06def51e : fffff880`0d8f6220 00000000`00010000 00000000`00000000 fffff800`036ad1bb : nt!KiPageFault+0x260
fffff880`0d8f5f20 fffff880`0d8f6220 : 00000000`00010000 00000000`00000000 fffff800`036ad1bb 00000000`00000000 : EtronXHCI+0x451e
fffff880`0d8f5f28 00000000`00010000 : 00000000`00000000 fffff800`036ad1bb 00000000`00000000 fffffa80`064c9bc0 : 0xfffff880`0d8f6220
fffff880`0d8f5f30 00000000`00000000 : fffff800`036ad1bb 00000000`00000000 fffffa80`064c9bc0 00000000`00000000 : 0x10000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
EtronXHCI+451e
fffff880`06def51e 418b8c818c000000 mov     ecx,dword ptr [r9+rax*4+8Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  EtronXHCI+451e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: EtronXHCI

IMAGE_NAME:  EtronXHCI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d433943

FAILURE_BUCKET_ID:  X64_0xD1_EtronXHCI+451e

BUCKET_ID:  X64_0xD1_EtronXHCI+451e

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

post #5 of 8
Thread Starter 
Ok.

I uninstalled the sm bus controller, and was able to install the Intel driver. After doing that, I was able to load into battlelog.

I have also done what you said to do e-peen. Thank you very much! Seems to be fine now, will fully test once BF3 is done re-downloading. Also going to try battlelog in Chrome.

Edit: Ok so I was able to load into it on IE, but not on Chrome. BSOD again. Uninstalling etron now.

Ok uninstalling that seems to have fixed it. I'm on Battlelog on Chrome right now.

So what does this mean? The Etron controller is for the front USB 3.0 port. It's where I plug my contoller into. It is set up with a USB 3.0 pass-through; so it goes out the back and into a 3.0 connected on the MB. Does that mean something is wrong with that port or something?
Edited by Reloaded83 - 4/30/12 at 1:19am
post #6 of 8
Quote:
Originally Posted by Reloaded83 View Post

The Etron controller is for the front USB 3.0 port. It's where I plug my contoller into. It is set up with a USB 3.0 pass-through; so it goes out the back and into a 3.0 connected on the MB. Does that mean something is wrong with that port or something?

It could be, but it also could be an issue with how the controller settings / USB settings are setup in the BIOS. I'd double check to make sure everything is as intended.
post #7 of 8
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

It could be, but it also could be an issue with how the controller settings / USB settings are setup in the BIOS. I'd double check to make sure everything is as intended.

Ok will do. BF3 downloaded, and it is indeed working just fine now after doing what you said. thumb.gifbiggrin.gif

I'll take a look at the bios this evening. Thanks again!!!
post #8 of 8
My pleasure, let me know if you have any issues.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: PC Gaming
Overclock.net › Forums › Video Games › PC Gaming › Blue screen upon loading Battlelog only? (Solved)