Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Playing Star Wars the old republic. Getting various BSODs.


10 Feb 2012   #1

Windows 7 Ultimate
 
 
Playing Star Wars the old republic. Getting various BSODs.

Currently playing Starwars : The old republic on a built system.

Windows 7 Ultimate x64 retail version
AMD phenom II x4 925 processor 2.80MHZ
8 Gigs Ram

Age of system is is about 1 month old. Never reinstalled OS.


as stated in my title. i get various BSODs while playing the game. i have updated all drivers. Currently using ATI Radeon 4300/4500 series video card. The strange thing is on my old Machine a Windows Vista Home OEM install, i never had an issue with BSODs while playing the game, only when i got this Machine Prebuilt did i get it. Now i am using the same video card that i had in my Vista machine in my New Windows 7 machine.

Any help will be appreciated. If any new info is needed please let me know.

My System SpecsSystem Spec
.

11 Feb 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [E:\BSODDmpFiles\Nonesovile06\Windows_NT6_BSOD_jcgriff2\021012-13875-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`02a4f000 PsLoadedModuleList = 0xfffff800`02c94670 Debug session time: Fri Feb 10 12:05:45.952 2012 (GMT-7) System Uptime: 0 days 2:41:02.233 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffe98008528010, 2, 1, fffff80002a0a68b} Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Rt64win7.sys *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys Probably caused by : Rt64win7.sys ( Rt64win7+11738 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffe98008528010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002a0a68b, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfe100 ffffe98008528010 CURRENT_IRQL: 0 FAULTING_IP: hal!HalBuildScatterGatherList+25f fffff800`02a0a68b 830b01 or dword ptr [rbx],1 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: θΜ TRAP_FRAME: fffff880067b5f90 -- (.trap 0xfffff880067b5f90) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000000a0 rbx=0000000000000000 rcx=00000000000000a0 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a0a68b rsp=fffff880067b6120 rbp=0000000000000085 r8=0000000000000af0 r9=0000000000000085 r10=fffffa8007337af8 r11=0000000000000085 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc hal!HalBuildScatterGatherList+0x25f: fffff800`02a0a68b 830b01 or dword ptr [rbx],1 ds:0005:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002acb1e9 to fffff80002acbc40 STACK_TEXT: fffff880`067b5e48 fffff800`02acb1e9 : 00000000`0000000a ffffe980`08528010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`067b5e50 fffff800`02ac9e60 : 00000000`00000002 00000000`0000dba4 00000000`00000001 ffffe980`08528010 : nt!KiBugCheckDispatch+0x69 fffff880`067b5f90 fffff800`02a0a68b : fffffa80`09315e80 fffffa80`09315f60 fffffa80`0736b7d0 00000000`00000000 : nt!KiPageFault+0x260 fffff880`067b6120 fffff880`014517c1 : fffffa80`09315e80 fffffa80`09315d50 fffffa80`000000a0 00000000`00018c58 : hal!HalBuildScatterGatherList+0x25f fffff880`067b6190 fffff880`04811738 : fffffa80`082cb1a0 00000000`00000000 fffffa80`0851a9f0 fffffa80`09315d50 : ndis!NdisMAllocateNetBufferSGList+0x181 fffff880`067b6230 fffffa80`082cb1a0 : 00000000`00000000 fffffa80`0851a9f0 fffffa80`09315d50 ffffe980`08528010 : Rt64win7+0x11738 fffff880`067b6238 00000000`00000000 : fffffa80`0851a9f0 fffffa80`09315d50 ffffe980`08528010 00000000`000001c0 : 0xfffffa80`082cb1a0 STACK_COMMAND: kb FOLLOWUP_IP: Rt64win7+11738 fffff880`04811738 ?? ??? SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: Rt64win7+11738 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Rt64win7 IMAGE_NAME: Rt64win7.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a718af3 FAILURE_BUCKET_ID: X64_0xA_Rt64win7+11738 BUCKET_ID: X64_0xA_Rt64win7+11738 Followup: MachineOwner ---------
  2. Loading Dump File [E:\BSODDmpFiles\Nonesovile06\Windows_NT6_BSOD_jcgriff2\021012-13078-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`02a4f000 PsLoadedModuleList = 0xfffff800`02c94670 Debug session time: Fri Feb 10 07:27:27.014 2012 (GMT-7) System Uptime: 0 days 6:24:18.295 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002da7da8, fffff88003bddf00, 0} Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+48 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002da7da8, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88003bddf00, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!MiRelocateImageAgain+48 fffff800`02da7da8 f0480fba2e00 lock bts qword ptr [rsi],0 CONTEXT: fffff88003bddf00 -- (.cxr 0xfffff88003bddf00) rax=fffffa800787cbb0 rbx=ffffffffffffffff rcx=fffffa80084f38b0 rdx=fffffa800972d4d1 rsi=ffff2fa000c0c370 rdi=fffffa800787cb60 rip=fffff80002da7da8 rsp=fffff88003bde8e0 rbp=0000000000000080 r8=fffffa800972d4d0 r9=fffff88003bde718 r10=fffffa8006cb0c40 r11=fffff88003bde900 r12=fffffa80084f38b0 r13=fffffa80071e1b40 r14=fffff8a000297e70 r15=fffff8a000297e70 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!MiRelocateImageAgain+0x48: fffff800`02da7da8 f0480fba2e00 lock bts qword ptr [rsi],0 ds:002b:ffff2fa0`00c0c370=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002da7da8 STACK_TEXT: fffff880`03bde8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x48 FOLLOWUP_IP: nt!MiRelocateImageAgain+48 fffff800`02da7da8 f0480fba2e00 lock bts qword ptr [rsi],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiRelocateImageAgain+48 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff88003bddf00 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiRelocateImageAgain+48 BUCKET_ID: X64_0x3B_nt!MiRelocateImageAgain+48 Followup: MachineOwner ---------
  1. Due to your Realtek network driver. Realtek. Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
  2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
  • If you are overclocking any hardware, please stop.


  • Update your Realtek driver using the link to the driver site: Realtek.


  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).


  • Re-install the game. The process name is gibberish, which could mean you have a corrupted installation of the game or corrupted files in general.


  • Due to the possibility of corrupted files, run the following two checks for corruption.
    1. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
    2. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
My System SpecsSystem Spec
Reply

 Playing Star Wars the old republic. Getting various BSODs.




Thread Tools



Similar help and support threads for2: Playing Star Wars the old republic. Getting various BSODs.
Thread Forum
Solved BSOD when launching Star Wars: The Old Republic BSOD Help and Support
Frequent BSOD playing Star Wars:The Old Republic BSOD Help and Support
BSOD playing League of Legends and Star Wars the Old Republic BSOD Help and Support
BSOD playing Star Wars: The Old Republic BSOD Help and Support
BSOD / System crash / reboot playing Star wars the old republic BSOD Help and Support
Solved BSOD playing Star Wars: The Old Republic, random reboots 0x00000024 BSOD Help and Support
Solved BSoD playing Star Wars the Old republic BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:23 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33