 | Game fails to start after 2.0.5(1) | Category: Technical SupportMay-14-2014 5:46 PM PDT (9 years ago)  |
| Had no issues prior to 2.0.5 - RoS splash screen hits and sits. If you try to click on it, this is the message that comes up. Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: Diablo III.exe Application Version: 2.0.5.24017 Application Timestamp: 53716af7 Hang Signature: 25f9 Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Hang Signature 1: 25f91793459d4159f7b37efc3fda940a Additional Hang Signature 2: f8e3 Additional Hang Signature 3: f8e37304730cbbc70f513b6316330ad0 Additional Hang Signature 4: 25f9 Additional Hang Signature 5: 25f91793459d4159f7b37efc3fda940a Additional Hang Signature 6: f8e3 Additional Hang Signature 7: f8e37304730cbbc70f513b6316330ad0 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Here is my D3debug file User defined symbols path: H:\Diablo III 2014.05.14 19:44:52.563273300 Diablo III Release (No Assertions) running under Windows 7-64 SP1 (Version 6.1.7601) 2014.05.14 19:44:52.563789300 <BUILD>2.0.5.24017 (98453-1233810)</BUILD> 2014.05.14 19:44:52.564264300 Cheats: DISABLED 2014.05.14 19:44:52.564854300 CPU Vendor: GenuineIntel 2014.05.14 19:44:52.565328600 CPU Details: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz 2014.05.14 19:44:52.565838300 CPU Processors: 1 2014.05.14 19:44:52.566337600 CPU Cores: 4 2014.05.14 19:44:52.566786300 CPU Threads: 8 2014.05.14 19:44:52.567294300 8172.14 MB of total physical memory 2014.05.14 19:44:52.567766300 OS Language: English 2014.05.14 19:44:52.568201600 Application Path: H:\Diablo III\ 2014.05.14 19:44:52.570695300 --- OS memory stats ----- 2014.05.14 19:44:52.571286000 Virtual size: 520.95 Mb 2014.05.14 19:44:52.571785600 Total free: 3558.84 Mb 2014.05.14 19:44:52.572255300 Largest free block: 2047.69 Mb 2014.05.14 19:44:52.572797600 --- OS memory stats end----- 2014.05.14 19:44:52.573359000 --- Main memory stats --- 2014.05.14 19:44:52.573909300 Total size: 400.00 Mb 2014.05.14 19:44:52.574444000 Total free: 365.73 Mb 2014.05.14 19:44:52.574998000 Largest free block: 365.72 Mb 2014.05.14 19:44:52.575518000 Total small size: 32.00 Mb 2014.05.14 19:44:52.576018300 Total small free: 31.90 Mb 2014.05.14 19:44:52.576585000 Largest small free block: 31.88 Mb 2014.05.14 19:44:52.577108600 --- Main memory stats end --- 2014.05.14 19:44:52.577647600 ---------------------------------------------- 2014.05.14 19:44:52.578182000 Command Line: OnlineService.SSO=true -launch -uid diablo3_enus 2014.05.14 19:44:52.578730300 Monitor BPP: 32 2014.05.14 19:44:52.579251300 Lowest monitor BPP: 32 2014.05.14 19:44:52.899838000 Clock freq = 3320380 2014.05.14 19:44:52.900812300 WinSock started successfully! 2014.05.14 19:44:52.901639000 Adjusted initial working directory: H:\Diablo III 2014.05.14 19:44:52.902241300 Detecting first installed locale. 2014.05.14 19:44:52.902832600 Detected: enUS 2014.05.14 19:44:52.921061600 Agent is successfully started or running already. 2014.05.14 19:44:56.615142600 AgentManagerImpl::GetStatus - bResult: 1, StatusCode: 200 2014.05.14 19:44:56.615944600 Agent reported speed: 1552503 2014.05.14 19:44:56.616529600 Detecting installed locales: 2014.05.14 19:44:56.617119000 Found: enUS 2014.05.14 19:44:56.621566600 Agent selected locale: enUS 2014.05.14 19:44:56.622293300 FileSystemGetLocale, AgentSettings: 1 2014.05.14 19:44:56.622889000 FileSystemGetLocale, using agent locale: enUS 2014.05.14 19:44:56.623475600 FileSystemGetLocale, returned locale: enUS 2014.05.14 19:44:56.624598000 SNOFilesInitialize('Data_D3', PC, enUS) 2014.05.14 19:44:56.625449300 Initializing Streaming | ||
 | Game fails to start after 2.0.5(2) | May-14-2014 6:12 PM PDT (9 years ago) |
| Derpzilla, Can you post some information about your computer? You can find this information in the Direct X Diagnostic Tool: Click on Start Click on Run Type in: dxdiag (In Vista, type dxdiag in the search field) Hit Enter or OK Click on the Save All Information button at the bottom, and create a dxdiag text file, and copy and paste it ALL here. _________________________________________________________ I'm available in the forums Tuesday - Friday, 11 am - 8 pm Pacific Time Saturday 10 am - 7 pm Pacific Time Feedback? - https://www.surveymonkey.com/s/Omrakos | ||
