Can't currently play. Anyone have any solutions?
Posted by3 years ago
- Diablo 2 Crashes On Startup Computer
- Diablo 2 Crash On Startup
- Diablo 2 Crashes On Startup Windows 7
Archived
I must say, between the constant gamepad/gaming mouse drivers no longer working every update, and other little things, I am not enjoying the Windows 10 experience.
UPDATE: figured it out. For some reason the windows update made it so I can't go full-screen without crashing. Windowed Fullscreen, however, still works just fine, for some reason. Managed to get a couple rifts in and like 10 paragon levels, so not a complete waste of the night...
12 comments
Hi!
I installed Diablo 2 on my new rig that is running Windows 7 and I would like to share with you how I fixed several issues I had with it.
Installation went fine. And I chose the standard Video Config which is: Direct3D. I didn´t install any patches becouse my main role was to play singleplayer.
So when I tried to launch the game the screen went black for a couple of seconds and then dissapeard. Nothing else happened. Then when I opened Task manager th process was still running so I killed it. Then came my first solution that didnt result very good...I changed the video option to Direct Draw. I also changed it to comptability to Windows XP(Service Pack 3) and ticked Disable Desktop Composition. I ran the game and surprisinly it ran. I watched the intro movie but when I came to the menu all the colours where screwed up. So I went back to Direct3D and then downloaded the patch(1.12). Now the game works flawlessly, well kind of.... Becouse I noticed a important thing, the game was using 30-50% of CPU load! I still havent come to a fix to it yet. But here is what I have come up to while reading other formums: that the game uses the 'old' programming way that consumes loads of CPU and almost none of GPU. The forum had a much more detaild explanation you can search it if you want: Diablo 2 CPU. And another big fix:
When you exit the game you notice that windows has turned to Windows 7 basic(no aero), you wait and aero still dosent show up. I concluded that the process still is running so I killed it. While killing the process I noticed that there were 2 rundll32.exe running. Usually there is only 1 unless you have a program that is really using it. It used 15% CPU power + 200mb ram. so I killed it and finally aero + CPU + RAM came back how they were before.
Hope this helped a little.
Erik Jansson
I installed Diablo 2 on my new rig that is running Windows 7 and I would like to share with you how I fixed several issues I had with it.
Installation went fine. And I chose the standard Video Config which is: Direct3D. I didn´t install any patches becouse my main role was to play singleplayer.
So when I tried to launch the game the screen went black for a couple of seconds and then dissapeard. Nothing else happened. Then when I opened Task manager th process was still running so I killed it. Then came my first solution that didnt result very good...I changed the video option to Direct Draw. I also changed it to comptability to Windows XP(Service Pack 3) and ticked Disable Desktop Composition. I ran the game and surprisinly it ran. I watched the intro movie but when I came to the menu all the colours where screwed up. So I went back to Direct3D and then downloaded the patch(1.12). Now the game works flawlessly, well kind of.... Becouse I noticed a important thing, the game was using 30-50% of CPU load! I still havent come to a fix to it yet. But here is what I have come up to while reading other formums: that the game uses the 'old' programming way that consumes loads of CPU and almost none of GPU. The forum had a much more detaild explanation you can search it if you want: Diablo 2 CPU. And another big fix:
When you exit the game you notice that windows has turned to Windows 7 basic(no aero), you wait and aero still dosent show up. I concluded that the process still is running so I killed it. While killing the process I noticed that there were 2 rundll32.exe running. Usually there is only 1 unless you have a program that is really using it. It used 15% CPU power + 200mb ram. so I killed it and finally aero + CPU + RAM came back how they were before.
Hope this helped a little.
Erik Jansson
HomeMainstreamHow to Fix Diablo 3 Crashes, Freezes, Downloader Problems & More
Finally, the great day has come! Diablo 3 was finally released and probably millions of people all over the world are playing Blizzard’s action RPG. However, it’s not all perfect when it comes to playing Diablo 3 as there are many people who are reporting game crashes and freezes and even problems with the Diablo 3 downloader and Battle.net server. I am here to try and help you get past all these problems and make sure that you have what it takes to fully experience Diablo 3.
So let’s turn this into an epic article with full Diablo 3 Crashes and Errors fixes! Just please make sure you check out the entire article before trying a solution – one of the ones listed here might look more likely to work for you than the others!
1. First of all, there are a ton of graphic cards that are not supported by the Diablo 3 game. So if you have one of the blacklisted video cards, you will not be able to play Diablo 3 and it will keep crashing or give you an error message. Check out the official post on the Diablo 3 forums to see what are the graphic cards that are not supported by Diablo 3.
2. There is also a list of programs that somehow manages to interfere with Diablo 3 and make it crash. Therefore, the best thing for you to do would be to turn off all background programs when playing the game, but if you don’t want to turn them all off, make sure you turn off the following:
• Mumble
• XFire
• EVGA Precision
• Airfoil by Rogue Amoeba
• MSI Afterburner
• Dxtory
• RadeonPro
• Taksi
• XFire
• EVGA Precision
• Airfoil by Rogue Amoeba
• MSI Afterburner
• Dxtory
• RadeonPro
• Taksi
3. For people who can’t launch the game or are having other various problems, I managed to find a solution for this in the forums and it appears that 90% of the people who tried it have managed to fix the problems they had. So it’s a MUST TRY! Here is what you should do:
Got to Start -> Type “Services” -> press enter OR select “Services” from the program list -> look for “Secondary Logon” -> click on it -> if it’s set to disabled, set it to automatic -> click “start the service” to the left -> try to download the game again using the Diablo-III-Setup-enUS.exe WITHOUT compatibility mode or admin mode.
If that doesn’t work, try with admin enabled; if still not working, try again with compatibility mode (XP Service Pack 2) enabled.
4. How to fix Diablo 3 Installer Problems
Many users are complaining that they encounter all sorts of problems when they are trying to install or download the game: either they get stuck at 41% (most of the users) or even at 1%. The solution here would be that of trying to re-download the game and hope for the best. If you keep getting the disk has ejected error message, you can only hope that Blizzard will fix that soon.
Or, if you have the patience, just do as one person suggests on the official forums: “I found no solution, I just kept launching the downloader again and again until I finally had all the files and I was able to install the game fine. Just keep relaunching when it crashes.”
5. ATI Cards can cause crashes
It appears that those who have the latest Catalyst 12.4 drivers encounter a heap of problems and crashes in Diablo 3, especially for the ATI Radeon HD 2400, 2600, 2900, 3400, 3600 and 4500 graphics cards. The solution is simple: download the 12.4a update that was just released by ATI and you’re ready to go!
It appears that those who have the latest Catalyst 12.4 drivers encounter a heap of problems and crashes in Diablo 3, especially for the ATI Radeon HD 2400, 2600, 2900, 3400, 3600 and 4500 graphics cards. The solution is simple: download the 12.4a update that was just released by ATI and you’re ready to go!
6. How to fix Error 108 in Diablo 3
You may be able to fix this by running the downloader and pointing it to the same saved location so that it may scan and download any missing files. This error usually appears to those who have downloaded the game completely but somehow some files ended up missing or corrupt.
You may be able to fix this by running the downloader and pointing it to the same saved location so that it may scan and download any missing files. This error usually appears to those who have downloaded the game completely but somehow some files ended up missing or corrupt.
Right now, these are the Diablo 3 crashes, freezes and error fixes that I can share with you. If you have any problems, please post a comment in the section below. Also, it would be even better if you had a solution to any of these problems, as it would certainly help a ton of players.
SPECIAL OFFER! Are you interested in learning how to speed level in Diablo 3? We have the best guide here (click to visit!)
Updated to 10.6.8 through Software Update last weekend, and Diablo II will no longer even open. It worked absolutely fine right up until the update. Can anyone help me fix this? Thanks so much!
Diablo 2 Crashes On Startup Computer
Here's the full crash report I get:
Process: Diablo II [725]
Path: /Applications/Diablo II Folder/Diablo II (Carbon)
Identifier: com.blizzard.Diablo2
Version: 1.10 (1.10)
Code Type: PPC (Translated)
Parent Process: launchd [114]
Date/Time: 2011-07-02 16:53:07.438 -0400
OS Version: Mac OS X 10.6.8 (10K540)
Report Version: 6
Interval Since Last Report: 60810 sec
Crashes Since Last Report: 5
Per-App Interval Since Last Report: 5 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: 68259B56-BDDB-40E4-8F6A-6F8FB83D05E9
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 LaunchCFMApp 0xb80c5640 0xb8000000 + 808512
1 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487
2 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496
3 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791
4 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455
Thread 1:
0 libSystem.B.dylib 0x80142afa mach_msg_trap + 10
1 libSystem.B.dylib 0x80143267 mach_msg + 68
2 LaunchCFMApp 0xb819440f CallPPCFunctionAtAddressInt + 206231
3 libSystem.B.dylib 0x80170259 _pthread_start + 345
4 libSystem.B.dylib 0x801700de thread_start + 34
Thread 2:
0 LaunchCFMApp 0xb815acc0 spin_lock_wrapper + 90152
1 LaunchCFMApp 0xb8179c5b CallPPCFunctionAtAddressInt + 97763
2 LaunchCFMApp 0xb80c6b13 0xb8000000 + 813843
3 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487
4 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496
5 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791
6 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455
Thread 3:
0 LaunchCFMApp 0xb815a8ff spin_lock_wrapper + 89191
1 LaunchCFMApp 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 LaunchCFMApp 0xb80c6b13 0xb8000000 + 813843
3 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487
4 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496
5 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791
6 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455
Thread 4:
0 LaunchCFMApp 0xb815a8ff spin_lock_wrapper + 89191
1 LaunchCFMApp 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 LaunchCFMApp 0xb80c6b13 0xb8000000 + 813843
3 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487
4 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496
5 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791
6 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455
Thread 5:
0 LaunchCFMApp 0xb815aa8b spin_lock_wrapper + 89587
1 LaunchCFMApp 0xb818c3eb CallPPCFunctionAtAddressInt + 173427
2 LaunchCFMApp 0xb818eeec CallPPCFunctionAtAddressInt + 184436
3 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523
4 ??? 0x8aacc406 0 + 2326578182
Thread 6:
0 LaunchCFMApp 0xb815a93a spin_lock_wrapper + 89250
1 LaunchCFMApp 0xb8176f67 CallPPCFunctionAtAddressInt + 86255
2 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523
3 ??? 0x8ac7d0b6 0 + 2328350902
Thread 7:
0 LaunchCFMApp 0xb815aa8b spin_lock_wrapper + 89587
1 LaunchCFMApp 0xb818c3eb CallPPCFunctionAtAddressInt + 173427
2 LaunchCFMApp 0xb818eeec CallPPCFunctionAtAddressInt + 184436
3 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523
4 ??? 0x8aacc406 0 + 2326578182
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xb80bfca8 ecx: 0x00000000 edx: 0x00000000
edi: 0x80a051c8 esi: 0x8a028d80 ebp: 0xb7fffa08 esp: 0xb7fffa00
ss: 0x0000001f efl: 0x00010206 eip: 0xb80c5640 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x80000000 - 0x8005dff7 com.apple.framework.IOKit 2.0 (???) <3DABAB9C-4949-F441-B077-0498F8E47A35> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x8007d000 - 0x800e7fe7 libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0x80142000 - 0x802e9ff7 libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
0x8036b000 - 0x804e6fe7 com.apple.CoreFoundation 6.6.5 (550.43) <10B8470A-88B7-FC74-1C2F-E5CBD966C051> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x805de000 - 0x805ecfe7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <3CE8AA79-F077-F1B0-A039-9103A4A02E92> /usr/lib/libz.1.dylib
0x805f1000 - 0x805fdff7 libkxld.dylib ??? (???) <9A441C48-2D18-E716-5F38-CBEAE6A0BB3E> /usr/lib/system/libkxld.dylib
0x80601000 - 0x80647ff7 libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
0x80654000 - 0x807d6fe7 libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <D5980817-6D19-9636-51C3-E82BAE26776B> /usr/lib/libicucore.A.dylib
0x80838000 - 0x808e5fe7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <9F8413A6-736D-37D9-8EB3-7986D4699957> /usr/lib/libobjc.A.dylib
0x808f9000 - 0x808fcfe7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <A4F6ADCC-6448-37B4-ED6C-ABB2CD06F448> /usr/lib/dyld
0xb8000000 - 0xb81defff LaunchCFMApp ??? (???) <6437A74D-607F-7339-5F7E-F6B0EF81C25D> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
Translated Code Information:
objc[725]: garbage collection is ON
Rosetta Version: 22.27
Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMAp p /Applications/Diablo II Folder/Diablo II (Carbon)
Exception: EXC_BAD_ACCESS (0x0001)
Thread 0: (0xb011cd74, 0xb815a8ff)
0x92105aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x92104190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x92021f08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x92105abc ctr: 0x91f81600
r00: 0xffffffda r01: 0xf0101dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x29b48f55 r06: 0x00000020 r07: 0x00000000
r08: 0x29b48f55 r09: 0x00000000 r10: 0x29b48f55 r11: 0xa02ea698
r12: 0x91f81600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa02f07cc r22: 0xa02f07c0 r23: 0xa02f07c8
r24: 0x00000233 r25: 0xb7c3f6c9 r26: 0xa02f050c r27: 0x00000040
r28: 0x0000000f r29: 0x10670f55 r30: 0xa02f07a0 r31: 0x921059b4
Thread 1: (0xb032484c, 0xb815aa8b)
0x7f1cc224: No symbol
0x98c2b570: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _YieldToThread + 524
0x98c2b6d4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _SetThreadState + 180
0x7f53bdd8: No symbol
0x7f53c3e4: No symbol
0x7f55f6e0: No symbol
0x7f462760: No symbol
0x7f4635c8: No symbol
0x7f462ab4: No symbol
0x7f560164: No symbol
0x7f53b6f8: No symbol
0x98c2bed4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _CooperativeThread + 348
0x92021f08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x91f81cc4 ctr: 0x91f81590
r00: 0xffffffe1 r01: 0xf0305610 r02: 0x00000013 r03: 0xf03056cc
r04: 0x00000003 r05: 0x00000018 r06: 0x00000020 r07: 0x00008707
r08: 0x00000000 r09: 0x00000000 r10: 0x8c84fa8d r11: 0xa02ea194
r12: 0x91f81590 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0xf03056cc r23: 0x00000018
r24: 0x00000020 r25: 0x00008707 r26: 0x00000000 r27: 0x00000000
r28: 0x00000003 r29: 0x00000003 r30: 0x00000000 r31: 0x98c2b36c
Thread 2: (0xb022084c, 0xb815aa8b)
0xf0203cf8: No symbol
0x98c2b570: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _YieldToThread + 524
0x7f53c228: No symbol
0x7f53b628: No symbol
0x7f53b6f8: No symbol
0x98c2bed4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _CooperativeThread + 348
0x92021f08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x91f81cc4 ctr: 0x91f81590
r00: 0xffffffe1 r01: 0xf0203c70 r02: 0x00000013 r03: 0xf0203d2c
r04: 0x00000003 r05: 0x00000018 r06: 0x00000020 r07: 0x00006607
r08: 0x00000000 r09: 0x00000000 r10: 0x8c850c17 r11: 0xa02ea194
r12: 0x91f81590 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0xf0203d2c r23: 0x00000018
r24: 0x00000020 r25: 0x00006607 r26: 0x00000000 r27: 0x00000000
r28: 0x00000003 r29: 0x00000003 r30: 0x00000000 r31: 0x98c2b36c
Thread 3: (0xb02a2e30, 0xb815a93a)
0x9201e6a4: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 880
0x98c2c984: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _TSWaitOnConditionTimedRelative + 240
0x98c2ea00: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _TSWaitOnSemaphoreCommon + 468
0x98bbc670: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : AsyncFileThread(void*) + 92
0x92021f08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x9201e6e8 ctr: 0x91f81610
r00: 0xffffffd9 r01: 0xf02848b0 r02: 0x00000001 r03: 0x00006c03
r04: 0x00006a03 r05: 0x0000003c r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x00000001 r10: 0xf0284e88 r11: 0xa02ea6a0
r12: 0x91f81610 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x98c9d1cc r19: 0x98c9d1d0
r20: 0xa02f16d0 r21: 0x98c9d1d4 r22: 0x00000000 r23: 0x00000000
r24: 0x0000003c r25: 0x00000001 r26: 0xa02f171c r27: 0xf0284e88
r28: 0xa0f1d4ac r29: 0x00000000 r30: 0xa0f1d4e0 r31: 0x9201e340
Thread 4: Crashed (0xb7fffa00, 0xb80c5640)
0x7f0a6c7c: No symbol
0x7f0a5b48: No symbol
0x7f0a09f0: No symbol
0x7f099fa8: No symbol
0x7f0993cc: No symbol
0x7f099210: No symbol
0x7f09c2f4: No symbol
0x7f09a908: No symbol
0x7f09cccc: No symbol
0x7f098038: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x7f0a6c7c ctr: 0x91f82d40
r00: 0x7f0a6c7c r01: 0xbfffeb70 r02: 0x02008000 r03: 0x00000000
r04: 0x000001e0 r05: 0x0000000c r06: 0x00000000 r07: 0x00000000
r08: 0x020653fc r09: 0x00000000 r10: 0x00000020 r11: 0xa044a514
r12: 0x91f82d40 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x02066b18 r18: 0x02066b08 r19: 0x02066b14
r20: 0x02066b10 r21: 0x7f478f60 r22: 0x7f478f68 r23: 0x020653fc
r24: 0x020653fc r25: 0x02066b0c r26: 0x00000016 r27: 0x00125a60
r28: 0x00000016 r29: 0x00125d20 r30: 0x00000000 r31: 0x020650bc
Thread 5: (0xb009ad38, 0xb815acc0)
0x921044b8: /usr/lib/libSystem.B.dylib : __dispatch_mgr_invoke + 228
0x92103e9c: /usr/lib/libSystem.B.dylib : __dispatch_queue_invoke + 308
0x9210402c: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread2 + 372
0x92104168: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 76
0x92021f08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x92104480 ctr: 0x91fc52d8
r00: 0x0000016b r01: 0xf0080bb0 r02: 0x00000000 r03: 0x00000004
r04: 0x00000000 r05: 0x00000000 r06: 0xf0080d0c r07: 0x00000001
r08: 0xf0080d28 r09: 0x00000000 r10: 0x0000003d r11: 0xa02e9530
r12: 0x91fc52d8 r13: 0x10624dd3 r14: 0x92153b04 r15: 0xf0080c0c
r16: 0xf0080c8c r17: 0xa03043dc r18: 0xf0080d28 r19: 0xa02fe588
r20: 0xa02ff588 r21: 0xf0080d0c r22: 0xa02fe508 r23: 0xa02fe488
r24: 0xa03043dc r25: 0x00000000 r26: 0xa02f062c r27: 0x00000000
r28: 0xa02f0604 r29: 0xa02f033c r30: 0xf0080d28 r31: 0x921043dc
Thread 6: (0xb019ed74, 0xb815a8ff)
0x92105aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x92104190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x92021f08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x92105abc ctr: 0x91f81600
r00: 0xffffffda r01: 0xf0182dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b99394c r06: 0x00000020 r07: 0x00000000
r08: 0x3b99394c r09: 0x00000000 r10: 0x3b99394c r11: 0xa02ea698
r12: 0x91f81600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa02f07cc r22: 0xa02f07c0 r23: 0xa02f07c8
r24: 0x00000233 r25: 0xee53a1a1 r26: 0xa02f050c r27: 0x00000040
r28: 0x0000000f r29: 0x224bb94c r30: 0xa02f07a0 r31: 0x921059b4
Model: iMac10,1, BootROM IM101.00CC.B00, 2 processors, Intel Core 2 Duo, 3.06 GHz, 4 GB, SMC 1.52f9
Graphics: ATI Radeon HD 4670, ATI Radeon HD 4670, PCIe, 256 MB
Memory Module: global_name
Diablo 2 Crash On Startup
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 2.1.14.6
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST31000528ASQ, 931.51 GB
Serial ATA Device: PIONEER DVD-RW DVRTS09
Diablo 2 Crashes On Startup Windows 7
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0x24400000 / 2
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26500000 / 2
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000 / 3
USB Device: AK5370, 0x0556 (Asahi Kasei Microsystems Co., Ltd), 0x0001, 0x04300000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 / 2
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x06110000 / 4
Diablo II-OTHER, Mac OS X (10.6.8)
Posted on
Hello first up, was the Diablo patcher running with administrative rights, did it throw up a UAC prompt? If not, right-click it and run as an administrator. That should get it patched. Failing that, go towww.battle.net make a Battle.net account if you don't have one, enter your Diablo CD key and you can download the latest fully patched version from the website.
As for Maplestory, what's changed on your system from the time it was working and now? Any new applications installed that are running?
Paul Smith - MVP for Windows Desktop Experience... I've crawled off NNTP - for now. Posting from Aldershot, UK. On the internet atwindowsresource.net anddasmirnov.net. Please post back letting us know what works and what doesn't. :) And if an answer is helpful mark it as such. :) Paul Smithhttp://www.dasmirnov.net/blog/
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.
Hi Undiminished,
In addition to Paul A. Smith’s response
I see that Maplestory game is incompatible with Windows 7, refer the Windows 7 compatibility center link
Step 1: You may want to run this game in Windows 7 compatibility mode. To do this, follow the steps mentioned in the link below
Maker older programs run in this version of Windows
http://windows.microsoft.com/en-US/windows7/Make-older-programs-run-in-this-version-of-Windows
I see that Diablo 2 is compatible with Windows 7, see the Windows 7 compatibility center link
Step 2: Follow all the steps mentioned in the article below
Game crashes or closes unexpectedly
(This article also holds good to resolve other games issue)
Thanks and Regards:
Ajay K
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this response?
Thanks for your feedback.