Overclock.net › Forums › Video Games › PC Gaming › Saint Rows 3 BSOD on launch
New Posts  All Forums:Forum Nav:

Saint Rows 3 BSOD on launch

post #1 of 22
Thread Starter 
i dont know if the BD cpu is the cause of it but i did alot of searching online and cant fine another guy with the same cpu that has the same problem... what can i do to get this game to run?

if i cant, anyone willing to trade me a Phenom II x6 for this ?
post #2 of 22
Hey vtech, it could possibly be, but can you please zip up and attach the DMP file you receive after BSODing from Saints Row? I'd like to take a look to see if we have any other options smile.gif
post #3 of 22
Thread Starter 
yea sure, just give me a min to save my work so it can BSOD with out me losing too much xD
post #4 of 22
No problem, take your time tongue.gif
post #5 of 22
Thread Starter 
ok here it is, sorry it took me a while to figure out how to get this dmp file u asked for tongue.gif 013012-17409-01.zip 23k .zip file
heres more info if it helps
Code:
Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.1.7600.2.0.0.256.1
  Locale ID:    1033

Additional information about the problem:
  BCCode:       101
  BCP1: 0000000000000021
  BCP2: 0000000000000000
  BCP3: FFFFF88002F64180
  BCP4: 0000000000000002
  OS Version:   6_1_7600
  Service Pack: 0_0
  Product:      256_1

Files that help describe the problem:
  C:\Windows\Minidump\013012-17409-01.dmp
  C:\Users\vforce1\AppData\Local\Temp\WER-19141-0.sysdata.xml


EDIT: this was when i tried to run in DX9 mode, but both mode are basically the same and BSODs on me ..... i wasted 60 bucks on this and cant even play it...
Edited by vtech1 - 1/30/12 at 2:39pm
post #6 of 22
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`06a4ad28 fffff800`0307b443 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`06a4ad30 fffff800`030d75f7 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffffa80`06ee9650 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`06a4adc0 fffff800`0301e895 : fffff800`03043460 fffff880`06a4af70 fffff800`03043460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`06a4aec0 fffff800`030cb3f3 : 00000000`3165ec88 fffff800`03247e80 fffff800`03247e80 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`06a4aef0 fffff800`030dce00 : fffff8a0`00000000 fffff800`00000001 00000000`00000000 fffff8a0`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`06a4b080 fffff800`030e7061 : fffff900`c3ee1000 00000000`00000002 00000000`00000001 fffff960`0027666c : nt!KeFlushMultipleRangeTb+0x260
fffff880`06a4b150 fffff800`030fa0fb : 00000000`00000002 fffff880`06a4b2c0 fffff900`c3ee1000 fffff800`00000001 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`06a4b260 fffff800`031feceb : 00000000`00001230 00000000`00001230 00000000`00000021 fffff800`033aa5be : nt!MiAllocatePagedPoolPages+0x4bb
fffff880`06a4b380 fffff800`030e1860 : 00000000`00001230 fffff880`046d9cc0 00000000`00000021 fffff800`033a618e : nt!MiAllocatePoolPages+0x8e2
fffff880`06a4b4d0 fffff800`03201bfe : 00000000`00000000 00000000`00000000 00000000`00000020 fffff880`046d9cc0 : nt!ExpAllocateBigPool+0xb0
fffff880`06a4b5c0 fffff960`001a28ed : 00000000`00002d78 00000000`00000000 00000000`00000000 fffff960`001b40d1 : nt!ExAllocatePoolWithTag+0x82e
fffff880`06a4b6b0 fffff960`001a3e0f : 00000000`00000001 fffff880`06a4b848 00000000`00000001 fffff960`001b4302 : win32k!AllocateObject+0xdd
fffff880`06a4b6f0 fffff960`00179f2f : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`06a4b7e0 fffff960`00190bc4 : 00000000`01010084 fffff900`c223f660 00000000`00000000 00000000`0000002c : win32k!GreCreateDIBitmapReal+0x533
fffff880`06a4b910 fffff960`00192be6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!InternalGetIconInfo+0x174
fffff880`06a4ba00 fffff800`030ce153 : fffffa80`08c2d060 00000000`0246ecb8 fffff880`06a4bac8 00000000`00090d99 : win32k!NtUserGetIconInfo+0x182
fffff880`06a4bab0 00000000`779d462a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0246ec98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779d462a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

Possible causes of this specific BSOD bugcheck:

- BIOS inconfiguration
- driver causing processor deadlock
- hardware fault (temp, voltage, dust, RFI, etc...)
- *Possible CPU fault

Since this was a rather inconclusive DMP file, the first thing I would recommend is enabling Driver Verifier. All of the instructions to enable it and disable it are on that page. Driver Verifier will hopefully provide a better answer as to what may be causing this. If you enable Driver Verifier and you get caught in a constant BSOD loop before booting into Windows, simply boot into Safe Mode and disable it there.

Also, I just thought I'd note that I took a quick search to see if anyone else is having this issue, and someone noted that a BIOS update solved their issue, and SR3 no longer causes BSODs. So, if we get through a bunch of tests first and nothing is working, that is what I would recommend. I would not recommend rushing straight to a BIOS update, but of course.. that's your choice.
post #7 of 22
I had the same exact problem. I have a gigabyte board and would get a BSOD whenever I started the game. I updated to the beta bios for my board and it worked. However, if there is an overclock the game will freeze about 3-5 minutes in. I hope that helps! Good luck!
$ 150 FX-8150
(20 items)
 
  
CPUMotherboardGraphicsGraphics
FX-8150 GIGABYTE GA-970A-UD3 XFX RADEON HD 6970 MSI R6850 (MS-V244) 
RAMHard DriveHard DriveHard Drive
Kingston 9905403-400.A00LF4 (4 x 2) Hitachi HDS5C3020ALA632 Hitachi HD T721010SLA360 Samsung 830 64gb 
Optical DriveOptical DriveCoolingOS
HL-DT-ST BD-RE WH12LS30 ATAPI iHAS324 B CORSAIR CWCH50 Water Cooler Windows 7 Ultimate Service Pack 1 
MonitorMonitorMonitorKeyboard
Asus VE276 ASUS VS Series VS247H-P ASUS VS Series VS247H-P Logitech 
PowerCaseMouseAudio
antec earthwatts ea-650 nzxt phantom black and green Logitech  Asus Xonar DG 
  hide details  
Reply
$ 150 FX-8150
(20 items)
 
  
CPUMotherboardGraphicsGraphics
FX-8150 GIGABYTE GA-970A-UD3 XFX RADEON HD 6970 MSI R6850 (MS-V244) 
RAMHard DriveHard DriveHard Drive
Kingston 9905403-400.A00LF4 (4 x 2) Hitachi HDS5C3020ALA632 Hitachi HD T721010SLA360 Samsung 830 64gb 
Optical DriveOptical DriveCoolingOS
HL-DT-ST BD-RE WH12LS30 ATAPI iHAS324 B CORSAIR CWCH50 Water Cooler Windows 7 Ultimate Service Pack 1 
MonitorMonitorMonitorKeyboard
Asus VE276 ASUS VS Series VS247H-P ASUS VS Series VS247H-P Logitech 
PowerCaseMouseAudio
antec earthwatts ea-650 nzxt phantom black and green Logitech  Asus Xonar DG 
  hide details  
Reply
post #8 of 22
Thread Starter 
lol even if a bios update was available for my mobo (WHICH IT AINT!!!!!) i still probably wouldn't risk an entire system for 1 game... let me try that thing u suggested, but after i enable it whats next?
post #9 of 22
Quote:
Originally Posted by vtech1 View Post

lol even if a bios update was available for my mobo (WHICH IT AINT!!!!!) i still probably wouldn't risk an entire system for 1 game... let me try that thing u suggested, but after i enable it whats next?


Sorry about that. I've never had an ASRock board before, but on my gigabyte it was simple. It had an "@Bios" feature that did the work for me. BD also has this issue with another game but I can't remember.
$ 150 FX-8150
(20 items)
 
  
CPUMotherboardGraphicsGraphics
FX-8150 GIGABYTE GA-970A-UD3 XFX RADEON HD 6970 MSI R6850 (MS-V244) 
RAMHard DriveHard DriveHard Drive
Kingston 9905403-400.A00LF4 (4 x 2) Hitachi HDS5C3020ALA632 Hitachi HD T721010SLA360 Samsung 830 64gb 
Optical DriveOptical DriveCoolingOS
HL-DT-ST BD-RE WH12LS30 ATAPI iHAS324 B CORSAIR CWCH50 Water Cooler Windows 7 Ultimate Service Pack 1 
MonitorMonitorMonitorKeyboard
Asus VE276 ASUS VS Series VS247H-P ASUS VS Series VS247H-P Logitech 
PowerCaseMouseAudio
antec earthwatts ea-650 nzxt phantom black and green Logitech  Asus Xonar DG 
  hide details  
Reply
$ 150 FX-8150
(20 items)
 
  
CPUMotherboardGraphicsGraphics
FX-8150 GIGABYTE GA-970A-UD3 XFX RADEON HD 6970 MSI R6850 (MS-V244) 
RAMHard DriveHard DriveHard Drive
Kingston 9905403-400.A00LF4 (4 x 2) Hitachi HDS5C3020ALA632 Hitachi HD T721010SLA360 Samsung 830 64gb 
Optical DriveOptical DriveCoolingOS
HL-DT-ST BD-RE WH12LS30 ATAPI iHAS324 B CORSAIR CWCH50 Water Cooler Windows 7 Ultimate Service Pack 1 
MonitorMonitorMonitorKeyboard
Asus VE276 ASUS VS Series VS247H-P ASUS VS Series VS247H-P Logitech 
PowerCaseMouseAudio
antec earthwatts ea-650 nzxt phantom black and green Logitech  Asus Xonar DG 
  hide details  
Reply
post #10 of 22
Quote:
Originally Posted by vtech1 View Post

but after i enable it whats next?

Just use your computer regularly until you BSOD... or... force it by starting saints row! tongue.gif

Post the verified enabled dump here as well afterwards smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: PC Gaming
Overclock.net › Forums › Video Games › PC Gaming › Saint Rows 3 BSOD on launch