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: BSOD playing Total War Rome II, error 0x00000101

13 Sep 2013   #1

Microsoft Windows 7 Ultimate 64 bits 7601 Multiprocessor Free Service Pack 1
 
 
BSOD playing Total War Rome II, error 0x00000101

Hello to everyone in SevenForums, this is my first post in this forum but itīs not the first time Iīve seeked help for windows related problems here. So just let me express my gratitude to you all.

Now Iīll proceed explaining my most recents troubles. Everytime I try playing TWRII, usually after 10~15 min of running, my computer gets this BSOD. This also happens with games like Assassinīs Creed III or, but less frequently, Metro 2033. In other games, like Shogun II: Fall of the samurai or Elder Scroll V, it doesnīt happen.

Bluescreenview shows me that the Bc Code is 0x00000101, and sometimes it is caused by driver:

a) atikmdag.sys( Adress: atikmdag.sys+825a3)-----> For this, according to some advices given to similar cases in this forum if Iīm not mistaken, I uninstalled amd catalyst driver with amd_cleanup_utility_1.2.1.0. Then reinstalled the latest amd catalyst driver(13-4_win7_win8_64_dd_ccc_whql.exe) but didnīt install catalyst control center. After doing this I tried to play again and the result was getting the same BOSD after 10~15 min, but now the driver at fault was:

B) ntoskrnl.exe( Adress: ntoskrnl.exe+72f40)------> And since this happened I decided to post in the forum .

The info required is uploaded in a .zip file like requested in the forum rules. I decided to ask for help since I believe it was better to present my problem and specific information.

Well, thanks to everyone who reads this post and I hope someone helps me resolve this. Any help will be most appreciated.

My specs are:
MB: P8P67-M PRO (BIOS: 37.01)
CPU: i5-2500k
RAM: Corsair Vengeance CMZ8GX3M2A1600C9 (2X 4GB)
GPU: AMD RADEON HD 6850 (XFX)
OS: Windows 7 ultimate 64 (6.1, compilation 7601)

If any information is missing pleaselet me know and I add it.

Thanks again. Arsene.

My System SpecsSystem Spec
.

14 Sep 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Hi arsene.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know about the wattage of the PSU.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
______________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88003365180, 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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003365180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Rome2.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0d432678 fffff800`02ed388a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03365180 : nt!KeBugCheckEx
fffff880`0d432680 fffff800`02e85ae7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`00040004 : nt! ?? ::FNODOBFM::`string'+0x4e5e
fffff880`0d432710 fffff800`033fa895 : fffff800`03420460 fffff880`0d4328c0 fffff800`03420460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0d432810 fffff800`02e78493 : fffffa80`0699c220 fffff880`0d432af8 00000000`00000000 fffff8a0`11df9000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0d432840 fffff800`02e82c59 : 00000000`000004c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0d4329d0 fffff800`031762be : fffff880`0d432b00 fffffa80`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x69
fffff880`0d432a70 fffff800`02e7b1d3 : fffffa80`06e13b50 00000000`000004c4 fffff880`0d432ab8 fffffa80`0699c220 : nt!NtWaitForSingleObject+0xde
fffff880`0d432ae0 00000000`73b12e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`11e9ed08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b12e09


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
My System SpecsSystem Spec
18 Sep 2013   #3

Microsoft Windows 7 Ultimate 64 bits 7601 Multiprocessor Free Service Pack 1
 
 

Sorry, my mistake, donīt know how to delete posts and this was repetition.
My System SpecsSystem Spec
.


18 Sep 2013   #4

Microsoft Windows 7 Ultimate 64 bits 7601 Multiprocessor Free Service Pack 1
 
 

Hi Arc.

First of all, thanks for replying. I really appreciate your guidance.

So, Iīve cleared the CMOs. Iīve runned all the tests and uploaded the results in the tests.zip file.

Anyway, Iīll summarize some of the results here:

1.- About Speccy, in the zip file I uploaded two screenshots, one showing the summary under regular conditions( using firefox, aimp) and a second one taken while playing Rome II. I guessed that would be useful.

2.- My PSU is a Sentey SDP750-SS (750W). And the eXtreme Power Suplpy Calculator recommended a 351W PSU, so mine should be ok. (Thereīs a .pdf file with the results in the zip file).

3.-I runned Memtest86+ v.4.20 for 18 hours and the results were 15 passes and 0 errors. (Thereīs a snapshot in the zip file).

4.- I stressed my video card with FurMark 1.11.0 (Resolution 1920x1080, no fullscreen, with the following settings checked: Dynamic background, Burn-in, Xtreme burn-in and Post-FX) just like the tutorial stated. I did it for 30 minutes, the temperature remained between 65~66 °C, being 66 the maximun. It showed no artifacts or errors of any kind. (The screenshot I uploaded in the zip file shows the test at minute 12, I meant to take another one at minute 30 but messed that up and the screenshot wasnīt taken, but the temperature remained stable at 65°C)

5.- Finally I stressed the CPU with Prime 95 v279 for 2hours nad 20 minutes. It didnīt reported any errors. In addition to that I used RealTemp 3.70 to check the temperatures, the maximun per core were: 75°C, 78°C,79°C, 76°C. And the average, this is my appreciation, were: 72°C, 75°C, 76°c, 73°C. (The test results are in the zip file)

In the test.zip there are five folders, each containiing the results or snaoshots of their respective tests.

Well, thatīs everything Iīve tested so far, I hoped everything was done according to the instructions, if thereīs anything wrong please tell me and Iīll do it again.

Thanks for everything again. Iīm waiting to read your opinion, Arc, and the opinions or advices of anyone in the forum who wants to help me.

Bye. Arsene.




Quote   Quote: Originally Posted by Arc View Post
Hi arsene.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know about the wattage of the PSU.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
______________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88003365180, 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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003365180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Rome2.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0d432678 fffff800`02ed388a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03365180 : nt!KeBugCheckEx
fffff880`0d432680 fffff800`02e85ae7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`00040004 : nt! ?? ::FNODOBFM::`string'+0x4e5e
fffff880`0d432710 fffff800`033fa895 : fffff800`03420460 fffff880`0d4328c0 fffff800`03420460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0d432810 fffff800`02e78493 : fffffa80`0699c220 fffff880`0d432af8 00000000`00000000 fffff8a0`11df9000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0d432840 fffff800`02e82c59 : 00000000`000004c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0d4329d0 fffff800`031762be : fffff880`0d432b00 fffffa80`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x69
fffff880`0d432a70 fffff800`02e7b1d3 : fffffa80`06e13b50 00000000`000004c4 fffff880`0d432ab8 fffffa80`0699c220 : nt!NtWaitForSingleObject+0xde
fffff880`0d432ae0 00000000`73b12e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`11e9ed08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b12e09


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
My System SpecsSystem Spec
18 Sep 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

All the tests are successfully passed.

Now let us know how it is running there.
My System SpecsSystem Spec
18 Sep 2013   #6

Microsoft Windows 7 Ultimate 64 bits 7601 Multiprocessor Free Service Pack 1
 
 

Hi Arc,

First of all thaks for your guidance. Iīm glad all the test were ook.

Well, today iīve tried playing Rome II twice and in both occassions my pc just stopped working, the image just freezes, it keeps showing whatever the games was showing at the moment, and doesnīt play any sound. Nothing responds, not any command. The weird thing is that it doesnīt show any BSOD, and after 5 minutes I decided to turn off the PC.

I donīt have any dump file to show you. Any ideas?.

Thanks you, Arc.

Bye. Arsene.


Quote   Quote: Originally Posted by Arc View Post
All the tests are successfully passed.

Now let us know how it is running there.
My System SpecsSystem Spec
19 Sep 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

I have asked for some more help.
My System SpecsSystem Spec
19 Sep 2013   #8

Desk1 8 Pro / Desk2 7 Home Prem / Laptop 8.1 Pro all 64bit
 
 

Hello Artsene now assuming this PSU is not new but in any case that in itself does not men it is not malfunctioning the one thing you haven't tried I see is the PSU test.

See these two

PSU - Jump Start
then this
PSU - Test DC Output Voltage

Now just keep in mind that correct volts does not mean correct or sufficient current (amps therefore watts) Fro example a car might have 12-13v at the terminals but turn the engine over and it might not have enough charge (amps on tap) to do that and power up the ignition.

PS I meant to add DO NOT under any circumstances interfere with the PSU by trying to look inside by dismantling it.
My System SpecsSystem Spec
19 Sep 2013   #9

Microsoft Windows 8.1 Pro 64-bit
 
 

Does event viewer say anything about errors? Event Viewer - Open and Use in Windows 7

Extra
Reading and understanding event viewer to track down slow boot times: Use Windows 7 Event Viewer to track down issues that cause slower boot times - TechRepublic
My System SpecsSystem Spec
19 Sep 2013   #10

Microsoft Community Contributor Award Recipient

Windows 7 Ultimate SP1 X64 (Windows 8.1, Linux Mint, Windows XP and others in VM)
 
 

arsene, It would help us to help you if you would fill out your system specs. System Info - See Your System Specs
We will need to know what hardware you have. Fill them out as completely as possible. To see what we'd like, at the bottom left of this post, click 'My System Specs' and you will see mine. Also, please go into bios and look at the hardware monitor and give us the readings of your +12V, +5V and +3.3V.
Also, if you are overclocking anything please set it back to default levels.
My System SpecsSystem Spec
Reply

 BSOD playing Total War Rome II, error 0x00000101




Thread Tools



Similar help and support threads for2: BSOD playing Total War Rome II, error 0x00000101
Thread Forum
Solved BSOD playing Total War: Rome 2, error 0x124 BSOD Help and Support
BSOD after Total War Rome II install BSOD Help and Support
BSOD playing a battle in Rome 2 total war BSOD Help and Support
BSOD playing Total war Rome 2, 0x124 BSOD Help and Support
BSOD playing battlefield 3, error 0x00000101 BSOD Help and Support
BSOD playing Battlefield 3, error 0x00000101 BSOD Help and Support
BSOD while playing Battlefield 3, error 0x00000101 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 01:08 AM.
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