Resolved - Initializing Error

[Wells 1st MRB]

Name: Renee Wells

Rank: Sergeant Major

Type of issue: (Software, Hardware, Steam, Not sure) Not sure

Brief Description of Issue: Computer screen showed "blue screen of death" and after restarting, computer will not go past "initializing" phase.

***Medical Supply Staff ONLY Below this line***

Current Status: Resolved

Researching

Pending Reply

Resolved

Unresolved

Main Technician: T. Heresy

Supporting Technician: M. Hess

Edited April 24, 2014 by Hess 1st MRB

[Lafy BAR]

That image looks like a failing graphics card. You could use speedfan or GPU-Z to check what temp your video card is running. The problem may only show up when the card gets hot. If that's the case, you can check the fan and heatsink to see that they aren't clogged with dust or you can lower the clock speed of the video card to try to reduce the temp. Otherwise it looks like you'll be needing a new video card soon.

[Holland 1st MRB]

The error you posted for us on the blue screen refers to a problem;

  Quote

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.

Since you only have one processor installed, this indicates a problem with one of the following;

A driver that, when run, freezes up your CPU.

Overheating to an extreme degree.

Hardware malfunction.

From what I've researched, this problem appears to crop up commonly on 64-bit versions of windows, and is most associated with a bad core on the CPU. Some BIOS setups allow you to disable individual cores. That may be something to look into.

It seems you have multiple problems at work here, as the above should take care of the bluescreen, but not the initializing screen, or the purple colours.

As Lafy indicated, the off-colour loading screens are likely a result of a failing graphics card, though you should follow his suggestions in his post above to test it.

The initializing screen will take a little more research before I can help you further on that one. The Marvel 88se91xx is a host controller for connection of SATA or PATA to a PCIe host. This indicated to me the problem is with the BIOS setup, or with the controller on your motherboard itself.

[Wells 1st MRB]

Since I disabled the SATA 3 in BIOS, there is no more initializing screen. I will continue monitoring for issues on startup, but so far so good.

*edit: Also, in reference to the pink picture I posted above, I didn't mention that once this pink screen occurs the computer freezes and does not unlock from that screen without a reboot.

Edited April 8, 2014 by Wells 1st MRB

[Heresy 1st MRB]

You could update the following dirvers here for your EVGA 131-GT-E767-TR motherboard to see if this helps. If updating the drivers (although they are from 2011) do not help I would tend to think that there is something wrong with your motherboard. There may have been a Windows update that updated your stock motherboard drivers and could explain why you are now seeing this issue.

https://www.evga.com/support/download/default.aspx

11-27-2011Chipset Driver9.3.0.1019131-GT-E767Win8/Win7/Vista/XP Download View

7-29-2011Sata 610.0.0.1042131-GT-E767Win8/Win7/Vista/XP Download

6-08-2011RAID10.6.0.1002131-GT-E767Win8/Win7/Vista/XP Download

Please confirm that your video card drivers are up to date as well.

Also it seems that you had at least one dump file. Please post the latest one you see there (I think 1-14-14).

Edited April 8, 2014 by Heresy 1st MRB

[Heresy 1st MRB]

Hi Wells,

Were you able to update the drivers by chance?

[Wells 1st MRB]

All drivers are up-to-date. The dump file I uploaded to google docs:

https://docs.google.com/file/d/0B74lzcxVXaS...Xd1ZHBGLXM/edit

[Heresy 1st MRB]

The last dump was pointing to your disk subsystem. After you changed your SATA setup you have been booting okay now right? Do you still have that issue when loading the Palermo map? Does it happen when you load Palermo locally (i.e. host it yourself)?

   Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

   Copyright (c) Microsoft Corporation. All rights reserved.

   

   

   Loading Dump File [C:\temp\011114-23400-01.dmp]

   Mini Kernel Dump File: Only registers and stack trace are available

   

   Symbol search path is: srv*c:\windows\Symbols*c:\symbols*C:\WINDOWS\Symbols\Itanium*C:\WINDOWS\Symbols_x86_Checked*c:\windows\symbols\*c:\msftpdbs*http://msdl.microsoft.com/download/symbols

   Executable search path is: 

   Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

   Product: WinNt, suite: TerminalServer SingleUserTS

   Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532

   Machine Name:

   Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`034926d0

   Debug session time: Sat Jan 11 09:13:53.824 2014 (UTC - 7:00)

   System Uptime: 0 days 20:29:59.839

   Loading Kernel Symbols

   ...............................................................

   ................................................................

   ................................

   Loading User Symbols

   Loading unloaded module list

   ......

   *******************************************************************************

   *                                                                             *

   *                        Bugcheck Analysis                                    *

   *                                                                             *

   *******************************************************************************

   

   Use !analyze -v to get detailed debugging information.

   

   BugCheck 7A, {20, ffffffffc000009d, fffffa80088707c8, 0}

   

   Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+50080 )

   

   Followup: MachineOwner

   ---------

   

   4: kd> !analyze -v

   *******************************************************************************

   *                                                                             *

   *                        Bugcheck Analysis                                    *

   *                                                                             *

   *******************************************************************************

   

   KERNEL_DATA_INPAGE_ERROR (7a)

   The requested page of kernel data could not be read in.  Typically caused by

   a bad block in the paging file or disk controller error. Also see

   KERNEL_STACK_INPAGE_ERROR.

   If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,

   it means the disk subsystem has experienced a failure.

   If the error status is 0xC000009A, then it means the request failed because

   a filesystem failed to make forward progress.

   Arguments:

   Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)

   Arg2: ffffffffc000009d, error status (normally i/o status code)

   Arg3: fffffa80088707c8, current process (virtual address for lock type 3, or PTE)

   Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

   

   Debugging Details:

   ------------------

   

   

   ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

   

   DISK_HARDWARE_ERROR: There was error with disk hardware

   

   BUGCHECK_STR:  0x7a_c000009d

   

   CUSTOMER_CRASH_COUNT:  1

   

   DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

   

   PROCESS_NAME:  System

   

   CURRENT_IRQL:  1

   

   LAST_CONTROL_TRANSFER:  from fffff800032b8c8c to fffff800032c4bc0

   

   STACK_TEXT:  

   fffff880`033d9818 fffff800`032b8c8c : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`088707c8 : nt!KeBugCheckEx

   fffff880`033d9820 fffff800`032adb97 : fffffa80`08870760 00000000`c000009d 00000000`00000000 fffffa80`088707f8 : nt! ?? ::FNODOBFM::`string'+0x50080

   fffff880`033d98e0 fffff800`032b75f7 : fffffa80`05b7e660 fffffa80`05b7e6b0 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57

   fffff880`033d9910 fffff800`032ba7fd : fffffa80`05b7e660 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7

   fffff880`033d9990 fffff800`032c70ea : 00000000`00000000 00000000`00000000 00000103`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd

   fffff880`033d9a20 fffff800`0325ba5f : fffffa80`00000002 fffff880`033d9d20 fffffa80`00000001 00000000`00000013 : nt!KeWaitForMultipleObjects+0x272

   fffff880`033d9ce0 fffff800`035612ea : fffffa80`05b7e660 0df90df9`38bc38bc 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf

   fffff880`033d9d40 fffff800`032b58e6 : fffff880`009b2180 fffffa80`05b7e660 fffff880`009bd0c0 cfa0cfa0`ab5aab5a : nt!PspSystemThreadStartup+0x5a

   fffff880`033d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

   

   

   STACK_COMMAND:  kb

   

   FOLLOWUP_IP: 

   nt! ?? ::FNODOBFM::`string'+50080

   fffff800`032b8c8c cc              int     3

   

   SYMBOL_STACK_INDEX:  1

   

   SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+50080

   

   FOLLOWUP_NAME:  MachineOwner

   

   MODULE_NAME: nt

   

   IMAGE_NAME:  ntkrnlmp.exe

   

   DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

   

   FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50080

   

   BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50080

   

   Followup: MachineOwner

   ---------

[Wells 1st MRB]

I've had no issues so far with my bootup (yay!). I'll continue monitoring for the DOD:S loading screen; it does not occur when I host Palermo.

[Heresy 1st MRB]

Are you getting that screen every time you load Palermo connected to a remote server, or just sometimes?

[Wells 1st MRB]

I don't believe it's only Palermo because I've been able to join the server on this map without any trouble. I've not had the pink screen while I'm in another server. In console, I have a lot of red typing showing up, but I'm not sure to what extent that's affecting my game.

[Heresy 1st MRB]

Have you seen the garbaled screen since you made the change to the SATA connections? What is the red text that you are seeing?

[Wells 1st MRB]

Yes, after I made the SATA changes I was playing DOD:S and the pink screen came up. I'll have to post the red text later tonight.

[Wells 1st MRB]

This is what my console reads when I join DoD:S:

Can't use cheat cvar c_maxdistance in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar c_mindistance in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar c_orthowidth in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar c_orthoheight in multiplayer, unless the server has sv_cheats set to 1.

Unknown command "sv_backspeed"

Not playing a local game.

Can't use cheat cvar fog_start in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar fog_end in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar fog_startskybox in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar fog_endskybox in multiplayer, unless the server has sv_cheats set to 1.

Can't use cheat cvar r_farz in multiplayer, unless the server has sv_cheats set to 1.

Network: IP 192.168.1.8, mode MP, dedicated No, ports 27015 SV / 27005 CL

Connecting to 8.6.77.142:27015...

Connected to 8.6.77.142:27015

Day of Defeat: Source

Map: dod_donner

Players: 1 / 32

Build: 1913431

Server Number: 1

Attemped to precache unknown particle system "blood_impact_red_01"!

Attemped to precache unknown particle system "blood_impact_green_01"!

Attemped to precache unknown particle system "blood_impact_yellow_01"!

Attemped to precache unknown particle system "slime_splash_01"!

Attemped to precache unknown particle system "slime_splash_02"!

Attemped to precache unknown particle system "slime_splash_03"!

The server is using sv_pure 0. (Enforcing consistency for select files only)

#Game_connected

Error reading weapon data file for: weapon_ifm_steadycam

Compact freed 475136 bytes

Redownloading all lightmaps

*You will spawn as Rifleman

hostname: 1st Marine Raider Battalion - Camp Pendleton *Recruiting*

version : 1913431/24 1913431 secure

udp/ip : 8.6.77.142:27015 (public ip: 8.6.77.142)

map : dod_donner at: 0 x, 0 y, 0 z

players : 1 (32 max)

# userid name uniqueid connected ping loss state

# 3 "SgtMaj. R. Wells [1st MRB]" STEAM_0:1:23635753 00:33 71 0 active

[sM] Changing map to dod_sturm...

Day of Defeat: Source

Map: dod_sturm

Players: 1 / 32

Build: 1913431

Server Number: 2

Attemped to precache unknown particle system "blood_impact_red_01"!

Attemped to precache unknown particle system "blood_impact_green_01"!

Attemped to precache unknown particle system "blood_impact_yellow_01"!

Attemped to precache unknown particle system "slime_splash_01"!

Attemped to precache unknown particle system "slime_splash_02"!

Attemped to precache unknown particle system "slime_splash_03"!

env_cubemap used on world geometry without rebuilding map. . ignoring: maps/dod_sturm/stone/blendstonedirt001a_wvt_patch

env_cubemap used on world geometry without rebuilding map. . ignoring: wwii/windows/window05_diffuse

The server is using sv_pure 0. (Enforcing consistency for select files only)

#Game_connected

Error reading weapon data file for: weapon_ifm_steadycam

Compact freed 1118208 bytes

Redownloading all lightmaps

*You will spawn as Rifleman

[Hess]

Had you ever tried this?

Edited April 16, 2014 by Hess 1st MRB

[Wells 1st MRB]

No, how do I get to that screen?

[Hess]

1. First start Steam

2. Go to Library and rightclick on Day of Defeat Source

3. Press on properties and then open the SET LAUNCH OPTIONS..

4. Type in -autoconfig

5. Click Okay

6. Start DoD:S

[Wells 1st MRB]

Ok thanks, I'll try this out when I get home. Does this alter any custom files I have (e.g. for lerp/sprays/etc.)?

[Hess]

Alright:)

It won't. Autoconfig will fix your hardware DirectX level if it's wrong

Edited April 16, 2014 by Hess 1st MRB

[Heresy 1st MRB]

Good idea Hess. Technically the autoconfig option sets the video settings to their default level while it is set and should not remain in the startup parameters except for troubleshooting. It is worth it though to try running the game with this parameter to see if you do get this issue Wells. If that does solve the issue then we know your video settings need to be changed.

Reference https://support.steampowered.com/kb_article...1040-JWMT-2947:

-autoconfig - Restores video and performance settings to default for the current hardware detected. Ignores settings inside any .cfg files until this parameter is removed.

[Wells 1st MRB]

  McDowell 1st MRB said:

  Hess 1st MRB said:

Had you ever tried this?

For those that don't understand german that is the 'Launch Options' for DoD:S

Can be found by right-clicking on the game and going into properties and clicking 'SET LAUNCH OPTIONS...'

  Hess 1st MRB said:

1. First start Steam

2. Go to Library and rightclick on Day of Defeat Source

3. Press on properties and then open the SET LAUNCH OPTIONS..

4. Type in -autoconfig

5. Click Okay

6. Start DoD:S

Got it, thanks.

[Wells 1st MRB]

I ran the -autoconfig this evening. Haven't had any issues with the pink screen since I initially posted the picture. Should I be getting any messages or codes from running the autoconfig?

[Heresy 1st MRB]

  Wells 1st MRB said:

I ran the -autoconfig this evening. Haven't had any issues with the pink screen since I initially posted the picture. Should I be getting any messages or codes from running the autoconfig?

No you should not see any messages, it just sets your video settings to the default. You can take that off and then turn down the detail of your video settings by using the recommend video settings that are denoted by the asterisk (*). If you want to play around with it you can turn up individual settings until you find the one that is causing your issue.

[Heresy 1st MRB]

Hi Wells,

Just wondering if you had tried to change any of your video settings or if we should just go ahead and close this ticket now?

[Wells 1st MRB]

You can close the ticket. I've been messing with the video settings, but unable to test it for longer lengths of time. If I have another error I'll post a new thread. Thanks all

[Hess]

Alright then:)

I'll marking the ticket as resolved.