Assassin's Creed Brotherhood causing BSOD

ricanrivers · 04 May 2011

Hey guys,

I am definitely sure that Assassin's Creed is my BSODs. I read somewhere else on this site to update drivers. My Wireless 360 controller drivers are up to date as are my Nvidia GeForce GT 240 graphics card. Hopefully these dmp files can help someone figure out what is wrong with my computer.

Any help would be extremely useful and I would feel very appreciative.

wish · 05 May 2011

Hi,
It seems you have driver issues especially your Asus driver.

Code:

ASACPI.sys   Sun Mar 27 18:30:36 2005

Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download.
Select your motherboard's model, scroll down to Utilities category and find ATK0110 driver (could be part of PCProbe and AISuite.)

Also remove Daemon/Alcohol Software then remove the sptd driver with this tools:
DuplexSecure - Downloads

These drivers need to be updated:

Code:

RTL8187.sys  Thu Jun 25 23:22:49 2009 → Realtek networking driver
L1E62x64.sys Wed Jun 10 22:45:22 2009 →    Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller

Log

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Wed May  4 07:11:35.596 2011 (GMT-8)
System Uptime: 0 days 0:13:04.313
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffd88002fd6200, 2, 0, fffff80002c8814b}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )

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

3: 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: ffffd88002fd6200, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c8814b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb30e0
 ffffd88002fd6200 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+13b
fffff800`02c8814b 488b42f8        mov     rax,qword ptr [rdx-8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  newsLeecher.ex

TRAP_FRAME:  fffff8800881e900 -- (.trap 0xfffff8800881e900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffd88002fd6208 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8814b rsp=fffff8800881ea90 rbp=fffff88002fd6208
 r8=ffffffffffffffff  r9=0000000000000064 r10=fffff88002fd3180
r11=00000000002f7a00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiInsertTimerTable+0x13b:
fffff800`02c8814b 488b42f8        mov     rax,qword ptr [rdx-8] ds:ffffd880`02fd6200=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7aca9 to fffff80002c7b740

STACK_TEXT:  
fffff880`0881e7b8 fffff800`02c7aca9 : 00000000`0000000a ffffd880`02fd6200 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0881e7c0 fffff800`02c79920 : fffffa80`058f4c20 fffffa80`058f4c20 fffff800`00001f80 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0881e900 fffff800`02c8814b : 00000000`00000000 00000000`00000000 00000008`00000001 fffff880`02f63180 : nt!KiPageFault+0x260
fffff880`0881ea90 fffff800`02c82af2 : fffffa80`058f4b60 fffffa80`058f4b60 00000000`00000000 00000000`00000003 : nt!KiInsertTimerTable+0x13b
fffff880`0881eaf0 fffff800`02c8497a : 00000000`00000000 fffff800`02c84802 00000000`00000064 00000000`00000287 : nt!KiCommitThreadWait+0x332
fffff880`0881eb80 fffff800`02f73e0e : fffffa80`058f4b60 00000000`fff56000 00000000`09faf100 00000000`00000064 : nt!KeDelayExecutionThread+0x186
fffff880`0881ebf0 fffff800`02c7a993 : 00000000`000011b0 fffff880`0881eca0 ffffffff`ffffd8f0 00000000`fff56000 : nt!NtDelayExecution+0x59
fffff880`0881ec20 00000000`736c2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`09faf0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x736c2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+13b
fffff800`02c8814b 488b42f8        mov     rax,qword ptr [rdx-8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+13b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b

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

SmurofNeves · 05 May 2011

I think he uses the daemon to mount his ISO's.. Do you crack your software & games.?

sandamine · 05 May 2011

um guys could anyone of you take a look at my bsod please i keep coming back to check for replies
https://www.sevenforums.com/crashes-d...help-bsod.html

ricanrivers · 05 May 2011

@wish thanks for such a quick reply. The imbedded links were a beautiful touch. Thanks so much. Will and try and update more of my drivers. I am at square one since (I just reformatted into a fresh OS from previous BSODs I had) and that is why I have been using Daemon tools. If you want to help me figure out why that OS crashed just tell me if you are up for the challenge I have about 20+ dmp files for that nightmare.

I will re-post with my results soon.

@SmurofNeves I do create backups of my already owned games and in no way promote pirating

But yes I am using Daemon, I have a TB HD and its easier than re-burning them onto discs. If there is some other alternative I am definitely open for suggestions because I always feared that DTLite would mess with my computer (making it believe hardware is there when it is not immediate way to get some familiar BSODs)

Thanks for all the responses I just found this site and I love it!!!

wish · 05 May 2011

Yes do the update as I mention before and post back with the result.
Then for replacement of Daemon, you may use MagicIso since it doesn't use sptd driver.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

ricanrivers · 05 May 2011

Hey everyone wish was right on the money! I updated the drivers on my graphics card, mobo, and wireless adapters. Problem solved this thread can be closed now.

I will switch out to MagicIso soon. Thanks for all the help 1up to wish.

wish · 06 May 2011

Glad it worked and have a nice day

ricanrivers · 08 May 2011

So, have some BSOD I assume it is from remnants of Daemon tools, but I did remove it and have been using magic iso.

This time it is happening when I am playing through Portal 2 (great game). Could this be a SPTD issue?

dmps attached.

wish · 09 May 2011

Yes I still see sptd is on your system.
Have you uninstall it with the tools that I gave before?
DuplexSecure - Downloads (choose uninstall not install)

Then one dump file, point to graphic driver error, so it's better to reinstall your VGA driver.
Use driversweeper to remove current driver then download and install a fresh copy.
Guru3D - Driver Sweeper
Drivers - Download NVIDIA Drivers

Another dump point to Realtek NIC driver. Have you installed the latest update of that driver?

Also install SP1:
Learn how to install Windows 7 Service Pack 1 (SP1)

Then we'll see how it goes.

Log

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50
Debug session time: Sun May  8 18:57:27.024 2011 (GMT-8)
System Uptime: 0 days 0:04:43.351
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8a008390aa0, 0, fffff88014bb305b, 7}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd8a008390aa0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88014bb305b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f10e0
 ffffd8a008390aa0 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`14bb305b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88004a7e740 -- (.trap 0xfffff88004a7e740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd8a008390aa0 rbx=0000000000000000 rcx=fffff8a00265ba80
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88014bb305b rsp=fffff88004a7e8d0 rbp=000000000000beb1
 r8=fffffa8008908440  r9=fffff88004a7e901 r10=0000000000000000
r11=fffffa80081ae2d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b:
fffff880`14bb305b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp ds:0002:ffffd8a0`08390aa0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f38849 to fffff80002eb9740

STACK_TEXT:  
fffff880`04a7e5d8 fffff800`02f38849 : 00000000`00000050 ffffd8a0`08390aa0 00000000`00000000 fffff880`04a7e740 : nt!KeBugCheckEx
fffff880`04a7e5e0 fffff800`02eb782e : 00000000`00000000 fffff8a0`084392b0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`04a7e740 fffff880`14bb305b : fffff8a0`08313860 fffff880`14bb2d4b 00000000`000000ae 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`04a7e8d0 fffff880`14bb08af : 00000000`00000000 fffffa80`054b4470 00000000`000000ae fffffa80`054b6d58 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b
fffff880`04a7e910 fffff880`14bca65d : 00000000`00000000 fffff8a0`0274ac90 fffffa80`00000000 fffffa80`0830a600 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`04a7eae0 fffff880`14bca398 : fffff880`02f67f40 fffff880`14bc9d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04a7ecd0 fffff880`14bc9e96 : 00000000`00000000 fffffa80`0909ea50 00000000`00000080 fffffa80`081ae2d0 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04a7ed00 fffff800`0315c7c6 : 00000000`02a3524a fffffa80`081af620 fffffa80`0538a040 fffffa80`081af620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04a7ed40 fffff800`02e97c26 : fffff880`02f63180 fffffa80`081af620 fffff880`02f6dfc0 aa473a34`00483700 : nt!PspSystemThreadStartup+0x5a
fffff880`04a7ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`14bb305b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

Followup: MachineOwner
---------
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03050e50
Debug session time: Sun May  8 07:21:29.419 2011 (GMT-8)
System Uptime: 1 days 7:18:00.519
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd880052332cf, 8, ffffd880052332cf, 7}

Unable to load image \SystemRoot\system32\DRIVERS\RTL8187.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL8187.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8187.sys

Could not read faulting driver name
Probably caused by : RTL8187.sys ( RTL8187+54b99 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd880052332cf, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: ffffd880052332cf, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bb0e0
 ffffd880052332cf 

FAULTING_IP: 
+64b4952f03bddac8
ffffd880`052332cf ??              ???

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800317ea80 -- (.trap 0xfffff8800317ea80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000027 rbx=0000000000000000 rcx=fffffa800806d090
rdx=fffffa8007b28200 rsi=0000000000000000 rdi=0000000000000000
rip=ffffd880052332cf rsp=fffff8800317ec10 rbp=00000000dce38c2b
 r8=fffffa8007b28200  r9=0000000000000000 r10=fffff88002f643c0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ffffd880`052332cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f02849 to fffff80002e83740

STACK_TEXT:  
fffff880`0317e918 fffff800`02f02849 : 00000000`00000050 ffffd880`052332cf 00000000`00000008 fffff880`0317ea80 : nt!KeBugCheckEx
fffff880`0317e920 fffff800`02e8182e : 00000000`00000008 fffffa80`083570ae fffffa80`05f96900 fffffa80`0806d000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`0317ea80 ffffd880`052332cf : fffffa80`00000027 fffff880`05267b99 fffffa80`00000004 fffff800`030285a0 : nt!KiPageFault+0x16e
fffff880`0317ec10 fffffa80`00000027 : fffff880`05267b99 fffffa80`00000004 fffff800`030285a0 00000000`00000001 : 0xffffd880`052332cf
fffff880`0317ec18 fffff880`05267b99 : fffffa80`00000004 fffff800`030285a0 00000000`00000001 fffffa80`081bbe80 : 0xfffffa80`00000027
fffff880`0317ec20 fffffa80`00000004 : fffff800`030285a0 00000000`00000001 fffffa80`081bbe80 fffffa80`081bbe80 : RTL8187+0x54b99
fffff880`0317ec28 fffff800`030285a0 : 00000000`00000001 fffffa80`081bbe80 fffffa80`081bbe80 fffff880`0521f575 : 0xfffffa80`00000004
fffff880`0317ec30 00000000`00000001 : fffffa80`081bbe80 fffffa80`081bbe80 fffff880`0521f575 fffffa80`083570ae : nt!ExWorkerQueue
fffff880`0317ec38 fffffa80`081bbe80 : fffffa80`081bbe80 fffff880`0521f575 fffffa80`083570ae fffff800`030285a0 : 0x1
fffff880`0317ec40 fffffa80`081bbe80 : fffff880`0521f575 fffffa80`083570ae fffff800`030285a0 fffffa80`05385b60 : 0xfffffa80`081bbe80
fffff880`0317ec48 fffff880`0521f575 : fffffa80`083570ae fffff800`030285a0 fffffa80`05385b60 00000000`00000000 : 0xfffffa80`081bbe80
fffff880`0317ec50 fffffa80`083570ae : fffff800`030285a0 fffffa80`05385b60 00000000`00000000 fffffa80`081bbe80 : RTL8187+0xc575
fffff880`0317ec58 fffff800`030285a0 : fffffa80`05385b60 00000000`00000000 fffffa80`081bbe80 fffff800`0317d943 : 0xfffffa80`083570ae
fffff880`0317ec60 fffffa80`05385b60 : 00000000`00000000 fffffa80`081bbe80 fffff800`0317d943 fffffa80`08030050 : nt!ExWorkerQueue
fffff880`0317ec68 00000000`00000000 : fffffa80`081bbe80 fffff800`0317d943 fffffa80`08030050 fffffa80`05385b60 : 0xfffffa80`05385b60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTL8187+54b99
fffff880`05267b99 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  RTL8187+54b99

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTL8187

IMAGE_NAME:  RTL8187.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b1f6af7

FAILURE_BUCKET_ID:  X64_0x50_RTL8187+54b99

BUCKET_ID:  X64_0x50_RTL8187+54b99

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