WoW crashes after logging in (Wine)
This has been a pretty major headache for me today. I'm trying to get WoW to work with Wine, but the two don't seem to play nice together. I've tried both DirectX and OpenGL and I always get the same crash result:
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files (x86)\World of Warcraft\WoW.exe
ProcessID: 8
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:7DC9C467
The instruction at "0x7DC9C467" referenced memory at "0xFFFFFFFF".
The memory could not be "read".
This always pops up in its own window, while in the terminal I get:
[avalith@zeus World of Warcraft]$ wine WoW.exe
fixme:process:GetLogicalProcessorInformation (0x33f620,0x33fc20): stub
fixme:process:GetLogicalProcessorInformation (0x15fbfc0,0x15fc5c0): stub
fixme:process:GetLogicalProcessorInformation (0x15fbfc0,0x15fc5c0): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x16fe340,0x16fe940): stub
fixme:process:GetLogicalProcessorInformation (0x16fe340,0x16fe940): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x16fe340,0x16fe940): stub
fixme:process:GetLogicalProcessorInformation (0x16fe340,0x16fe940): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x16fe340,0x16fe940): stub
fixme:process:GetLogicalProcessorInformation (0x16fe340,0x16fe940): stub
fixme:process:GetLogicalProcessorInformation (0x33f554,0x33fb54): stub
fixme:process:GetLogicalProcessorInformation (0x33f554,0x33fb54): stub
archive Data/Cache/SoundCache-1.MPQ opened
archive Data/Cache/SoundCache-2.MPQ opened
archive Data/Cache/SoundCache-3.MPQ opened
archive Data/Cache/SoundCache-0.MPQ opened
archive Data/Cache/enUS/SoundCache-enUS.MPQ opened
archive Data/wow-update-base-15211.MPQ opened
archive Data/enUS/wow-update-enUS-15211.MPQ opened
archive Data/Cache/patch-base-15211.MPQ opened
archive Data/Cache/enUS/patch-enUS-15211.MPQ opened
archive Data/Cache/SoundCache-patch-15211.MPQ opened
archive Data/Cache/enUS/SoundCache-patch-enUS-15211.MPQ opened
archive Data/wow-update-base-15354.MPQ opened
archive Data/enUS/wow-update-enUS-15354.MPQ opened
archive Data/Cache/patch-base-15354.MPQ opened
archive Data/Cache/enUS/patch-enUS-15354.MPQ opened
archive Data/Cache/SoundCache-patch-15354.MPQ opened
archive Data/Cache/enUS/SoundCache-patch-enUS-15354.MPQ opened
archive Data\world2.MPQ opened
archive Data\enUS\expansion3-speech-enUS.MPQ opened
archive Data\enUS\expansion3-locale-enUS.MPQ opened
archive Data\expansion3.MPQ opened
archive Data\enUS\expansion2-speech-enUS.MPQ opened
archive Data\enUS\expansion2-locale-enUS.MPQ opened
archive Data\expansion2.MPQ opened
archive Data\enUS\expansion1-speech-enUS.MPQ opened
archive Data\enUS\expansion1-locale-enUS.MPQ opened
archive Data\expansion1.MPQ opened
archive Data\enUS\speech-enUS.MPQ opened
archive Data\enUS\locale-enUS.MPQ opened
archive Data\sound.MPQ opened
archive Data\world.MPQ opened
archive Data\art.MPQ opened
fixme:win:EnumDisplayDevicesW ((null),0,0x33ed20,0x00000000), stub!
fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 0x4 and card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x300)").
fixme:win:EnumDisplayDevicesW ((null),0,0x33b2e0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x33b2e0,0x00000000), stub!
I'm at a loss here... I have no idea where to go and googling the error codes isn't helping any. I've read the wiki and copied the installation from my old Windows system. I really, really don't want to have to go back to it just for WoW. I apologize for a lack of information, but I don't really have anything to go on except this little bit.
Last edited by Avalith (2012-03-26 18:24:54)
Solved! Turns out I just had to install lib32-ati-dri.
Orr maybe not. That lets me log in, but as soon as I choose a character it crashes on me. This is what popped up in the terminal after the crash:
wine: Unhandled page fault on execute access to 0x00000000 at address (nil) (thread 0009), starting debugger...
Unhandled exception: page fault on execute access to 0x00000000 in 32-bit code (0x00000000).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:00000000 ESP:0032fbe4 EBP:0032fc44 EFLAGS:00210246( R- -- I Z- -P- )
EAX:000083f1 EBX:00020000 ECX:00000de1 EDX:1b56bba8
ESI:00000000 EDI:15312fb8
Stack dump:
0x0032fbe4: 00867585 00000de1 00000000 000083f1
0x0032fbf4: 00000200 00000200 00000000 00020000
0x0032fc04: 1b56bba8 00000200 15312fb8 00000200
0x0032fc14: 00000000 00000000 00000200 00000200
0x0032fc24: 0000813d 00000009 00000000 00000400
0x0032fc34: 1b58bba8 00020000 1b56bba8 000083f1
000c: sel=0067 base=00000000 limit=00000000 16-bit --x
Backtrace:
=>0 0x00000000 (0x0032fc44)
1 0x00867799 in wow (+0x467798) (0x0032fc98)
2 0x00867842 in wow (+0x467841) (0x0032fca8)
3 0x0084217a in wow (+0x442179) (0x0032fcb4)
4 0x0083f535 in wow (+0x43f534) (0x0032fcd8)
5 0x006f9700 in wow (+0x2f96ff) (0x0032fd18)
6 0x008a23a9 in wow (+0x4a23a8) (0x0032fd48)
7 0x0089f33c in wow (+0x49f33b) (0x0032fd70)
8 0x008a09aa in wow (+0x4a09a9) (0x0032fdc4)
9 0x008a09f1 in wow (+0x4a09f0) (0x0032fddc)
10 0x00408488 in wow (+0x8487) (0x0032fe70)
11 0x7b85a5cc call_process_entry+0xb() in kernel32 (0x0032fe88)
12 0x7b85b83f in kernel32 (+0x4b83e) (0x0032fec8)
13 0x7bc758e0 call_thread_func_wrapper+0xb() in ntdll (0x0032fed8)
14 0x7bc77e4d call_thread_func+0x7c() in ntdll (0x0032ffa8)
15 0x7bc758be RtlRaiseException+0x21() in ntdll (0x0032ffc8)
16 0x7bc4c9be call_dll_entry_point+0x33d() in ntdll (0x0032ffe8)
17 0xf75f38bd wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000)
18 0xf75f397b wine_switch_to_stack+0x2a() in libwine.so.1 (0xffd973b8)
19 0x7bc52686 LdrInitializeThunk+0x3b5() in ntdll (0xffd97428)
20 0x7b86195a __wine_kernel_init+0xa19() in kernel32 (0xffd985c8)
21 0x7bc52ddb __wine_process_init+0x25a() in ntdll (0xffd98648)
22 0xf75f0dfc wine_init+0x28b() in libwine.so.1 (0xffd986a8)
23 0x7bf00d6b main+0x8a() in <wine-loader> (0xffd98af8)
24 0xf7445483 __libc_start_main+0xf2() in libc.so.6 (0x00000000)
0x00000000: -- no code accessible --
Modules:
Module Address Debug info Name (132 modules)
PE 400000- 10da000 Export wow
PE 3c910000-3cbc4000 Deferred battle.net
ELF 7b800000-7ba37000 Dwarf kernel32<elf>
\-PE 7b810000-7ba37000 \ kernel32
ELF 7bc00000-7bcd2000 Dwarf ntdll<elf>
\-PE 7bc10000-7bcd2000 \ ntdll
ELF 7bf00000-7bf04000 Dwarf <wine-loader>
ELF 7cc2d000-7cc63000 Deferred uxtheme<elf>
\-PE 7cc30000-7cc63000 \ uxtheme
ELF 7cdfa000-7de37000 Deferred r600_dri.so
ELF 7de37000-7de42000 Deferred libxcursor.so.1
ELF 7de53000-7de6e000 Deferred libgcc_s.so.1
ELF 7de80000-7deaa000 Deferred libexpat.so.1
ELF 7deaa000-7dedf000 Deferred libfontconfig.so.1
ELF 7dedf000-7deef000 Deferred libxi.so.6
ELF 7deef000-7def8000 Deferred libxrandr.so.2
ELF 7def8000-7df03000 Deferred libxrender.so.1
ELF 7df03000-7df9f000 Deferred winex11<elf>
\-PE 7df10000-7df9f000 \ winex11
ELF 7df9f000-7e03b000 Deferred libfreetype.so.6
ELF 7e069000-7e093000 Deferred msacm32<elf>
\-PE 7e070000-7e093000 \ msacm32
ELF 7e093000-7e144000 Deferred winmm<elf>
\-PE 7e0a0000-7e144000 \ winmm
ELF 7e144000-7e159000 Deferred hid<elf>
\-PE 7e150000-7e159000 \ hid
ELF 7e159000-7e195000 Deferred winspool<elf>
\-PE 7e160000-7e195000 \ winspool
ELF 7e195000-7e201000 Deferred setupapi<elf>
\-PE 7e1a0000-7e201000 \ setupapi
ELF 7e201000-7e27f000 Deferred rpcrt4<elf>
\-PE 7e210000-7e27f000 \ rpcrt4
ELF 7e27f000-7e3a6000 Deferred ole32<elf>
\-PE 7e2a0000-7e3a6000 \ ole32
ELF 7e3a6000-7e3da000 Deferred ws2_32<elf>
\-PE 7e3b0000-7e3da000 \ ws2_32
ELF 7e3da000-7e4dd000 Deferred comctl32<elf>
\-PE 7e3e0000-7e4dd000 \ comctl32
ELF 7e4dd000-7e703000 Deferred shell32<elf>
\-PE 7e4f0000-7e703000 \ shell32
ELF 7e703000-7e776000 Deferred shlwapi<elf>
\-PE 7e710000-7e776000 \ shlwapi
ELF 7e776000-7e79d000 Deferred mpr<elf>
\-PE 7e780000-7e79d000 \ mpr
ELF 7e79d000-7e7b4000 Deferred libz.so.1
ELF 7e7b6000-7e7c6000 Deferred libbz2.so.1.0
ELF 7e7c6000-7e7e2000 Deferred dinput8<elf>
\-PE 7e7d0000-7e7e2000 \ dinput8
ELF 7e7e2000-7e857000 Deferred wininet<elf>
\-PE 7e7f0000-7e857000 \ wininet
ELF 7e857000-7e99c000 Deferred wined3d<elf>
\-PE 7e860000-7e99c000 \ wined3d
ELF 7e99c000-7e9da000 Deferred d3d9<elf>
\-PE 7e9a0000-7e9da000 \ d3d9
ELF 7e9da000-7e9e3000 Deferred librt.so.1
ELF 7e9e3000-7e9ea000 Deferred libxdmcp.so.6
ELF 7e9ea000-7e9ee000 Deferred libxau.so.6
ELF 7e9ee000-7e9fb000 Deferred libdrm.so.2
ELF 7e9fb000-7ea01000 Deferred libxxf86vm.so.1
ELF 7ea01000-7ea23000 Deferred libxcb.so.1
ELF 7ea23000-7ea3c000 Deferred libxcb-glx.so.0
ELF 7ea3c000-7eb73000 Deferred libx11.so.6
ELF 7eb73000-7eb79000 Deferred libxfixes.so.3
ELF 7eb79000-7eb7d000 Deferred libxdamage.so.1
ELF 7eb7d000-7eb93000 Deferred libglapi.so.0
ELF 7eb93000-7ebad000 Deferred libice.so.6
ELF 7ebad000-7ec06000 Deferred libgl.so.1
ELF 7ec08000-7ec0c000 Deferred libxcomposite.so.1
ELF 7ec0c000-7ec10000 Deferred libxinerama.so.1
ELF 7ec10000-7ec34000 Deferred imm32<elf>
\-PE 7ec20000-7ec34000 \ imm32
ELF 7ec34000-7ed0f000 Deferred opengl32<elf>
\-PE 7ec50000-7ed0f000 \ opengl32
ELF 7ed0f000-7ed79000 Deferred advapi32<elf>
\-PE 7ed20000-7ed79000 \ advapi32
ELF 7ed79000-7ee45000 Deferred gdi32<elf>
\-PE 7ed90000-7ee45000 \ gdi32
ELF 7ee45000-7ef97000 Deferred user32<elf>
\-PE 7ee60000-7ef97000 \ user32
ELF 7ef97000-7efa4000 Deferred libnss_files.so.2
ELF 7efa4000-7efd2000 Deferred libm.so.6
ELF 7efd4000-7efe6000 Deferred libxext.so.6
ELF 7efe6000-7f000000 Deferred version<elf>
\-PE 7eff0000-7f000000 \ version
ELF f0d19000-f0d2d000 Deferred psapi<elf>
\-PE f0d20000-f0d2d000 \ psapi
ELF f0d2d000-f0d91000 Deferred dbghelp<elf>
\-PE f0d30000-f0d91000 \ dbghelp
ELF f0d91000-f0dcb000 Deferred winhttp<elf>
\-PE f0da0000-f0dcb000 \ winhttp
ELF f0dcb000-f0dee000 Deferred iphlpapi<elf>
\-PE f0dd0000-f0dee000 \ iphlpapi
ELF f0dee000-f0eb2000 Deferred crypt32<elf>
\-PE f0e00000-f0eb2000 \ crypt32
ELF f0eb2000-f0ee1000 Deferred msvcr90<elf>
\-PE f0ec0000-f0ee1000 \ msvcr90
ELF f0ee1000-f0f7d000 Deferred msvcrt<elf>
\-PE f0ef0000-f0f7d000 \ msvcrt
ELF f0f7d000-f0fa8000 Deferred msvcr80<elf>
\-PE f0f90000-f0fa8000 \ msvcr80
ELF f614a000-f6164000 Deferred libnsl.so.1
ELF f6164000-f6191000 Deferred libvorbis.so.0
ELF f6191000-f6308000 Deferred libvorbisenc.so.2
ELF f6308000-f635a000 Deferred libflac.so.8
ELF f635a000-f63ce000 Deferred libsndfile.so.1
ELF f63ce000-f6418000 Deferred libdbus-1.so.3
ELF f6418000-f647f000 Deferred libpulsecommon-1.1.so
ELF f647f000-f64cd000 Deferred libpulse.so.0
ELF f64cd000-f65c3000 Deferred libasound.so.2
ELF f65f1000-f66ff000 Deferred oleaut32<elf>
\-PE f6610000-f66ff000 \ oleaut32
ELF f7301000-f7309000 Deferred libogg.so.0
ELF f7309000-f7310000 Deferred libasyncns.so.0
ELF f7310000-f7319000 Deferred libjson.so.0
ELF f7319000-f7320000 Deferred libasound_module_pcm_pulse.so
ELF f7320000-f734e000 Deferred winealsa<elf>
\-PE f7330000-f734e000 \ winealsa
ELF f734e000-f7372000 Deferred mmdevapi<elf>
\-PE f7350000-f7372000 \ mmdevapi
ELF f7372000-f73bb000 Deferred dsound<elf>
\-PE f7380000-f73bb000 \ dsound
ELF f73f1000-f73f7000 Deferred libuuid.so.1
ELF f73f9000-f73fe000 Deferred libdl.so.2
ELF f7402000-f7419000 Deferred libresolv.so.2
ELF f7419000-f7420000 Deferred libnss_dns.so.2
ELF f7420000-f7423000 Deferred libx11-xcb.so.1
ELF f7423000-f742c000 Deferred libsm.so.6
ELF f742c000-f75cf000 Dwarf libc.so.6
ELF f75cf000-f75ea000 Deferred libpthread.so.0
ELF f75ea000-f772e000 Dwarf libwine.so.1
ELF f772f000-f7751000 Deferred ld-linux.so.2
ELF f7751000-f7752000 Deferred [vdso].so
Threads:
process tid prio (all id:s are in hex)
00000008 (D) C:\Program Files\World of Warcraft\Wow.exe
00000017 0
0000002e 0
0000000d 0
0000000b 0
00000047 0
00000046 0
00000045 0
00000044 0
00000043 0
00000042 0
00000041 0
00000040 0
0000003f 0
0000003e 0
0000003d 0
0000003c 0
00000039 1
00000037 1
00000034 0
00000033 0
00000032 0
00000031 2
00000030 15
0000002f 15
0000002d 0
0000002c 0
0000002b 0
0000002a 0
00000029 0
00000028 0
00000027 0
00000026 0
00000023 0
00000009 0 <==
0000000e services.exe
0000001e 0
0000001d 0
00000015 0
00000010 0
0000000f 0
00000012 winedevice.exe
00000019 0
00000014 0
00000013 0
0000001a plugplay.exe
0000001f 0
0000001c 0
0000001b 0
00000020 explorer.exe
00000021 0
Last edited by Avalith (2012-03-26 18:26:17)
Similar Messages
-
In my MacBook Pro(10.7.5), finder is crashing after logging in. It is showing crash report with Relaunch option, when i click on Relaunch option finder is working properly but i am unable to see Top bar(Apple logo, Date and Wifi etc... bar). Even in safari address bar, TextEdit not accepting any text means when type something not showing up and also i am unable operate any thing from keyboard. Plz help me…..
One thing that you can try is installing a 'fresh' version of OS X Lion. Boot into your Recovery partition (holding down the command and R keys whilst booting) and elect to install OS X from the Recovery screen. You need not erase your hard drive and you should not lose any of your data.
Oh, and just as a precaution, I would use Disk Utility, once you're in Recovery mode, to verify your hard drive before trying to install the OS again.
Clinton -
WOW Crashes After 10 min, K8N Neo4 Help Please.....
OK guys i'm stumpted... I've been working on this computer for about 2 weeks for a friend(this is his system).
I updated sig, Don't know if it worked?
He bought this in July as a new gaming rig. But has not had any luck since.
The problem goes like this.
You can load up WoW and the game looks great and runs great, for about 5-10 minutes and then it crashes. Black screen and then reset. I can hear the HD power cycle. and then the speaker beeps at me. I have to shut down the computer; reset doesn't work.
Some games work ok. Some will run for hours and hours. Yet others will crash after 1 hour, it's very unpredictable.
What i've tried:
Switched out his 6800gt for my 6600gt Fixed the problem. So i figured the 6800gt was being underpowered by his generic power supply. I hooked up my OCZ 520 Modstream, and got the same problem. (I know on the DFI boards the 20 pin psu are a NO NO so i figured this had to be the problem, but it wasn't.)
I read that some other people were having trouble with this card and this MSI board.
I tried disable fastwrites, No luck... Tried underclocking the card, No luck...
Tried updated the MOBO Bios, No luck... Although this did solve the random reset problem. (latest 11/04..I think)
I tried His 6800 GT in my computer, it works fine.
I also tried my OCZ pc3200 VX ram and still the same problem.
Oh, did I mention it's prime and Memtest stable.....10 hours
Sorry this is a long read.
thanks guys.If you are confident a different videocard will solve the problem,yes.
Maybe the 6800 series just don't like the curent setup , since you stated it works flawness in another system.
On a sidenote,WoW seems to have caused problems to many users with a certain videocard,don't recall if it was ati,could be since I don't read much about nvidia anymore,on the other hand I also read about nvidia card users in ati forums.
Try some older drivers with the videocard.
Your testing seems to indicate the rest of this system is working fine,so idd,it could be just the videocard,or type of card.
It's a pcie card right?Maybe try setting the pcie bus a little higher?It defaults to 100.
Have you connected a single power line to the card?Or did you use 1 of the molex connectors already attached to the hard drive?
Now recently I read somewhere that the recommended setup was to use the power lead from the videocard with the lead going into the hard drive.It was stated that a single clean power feed was causing some instability.But I must confess that my card gets a single feed,and it works fine.Maybe something to try,you never know
Also,does the psu have a 24pin connector?Maybe yours has and in this machine it's just 20pins?Is the 4pin connector also used on the mainboard?
Goodluck. -
Crashing after Log and Transfer
I am experiencing a FCP crash after using Log and Transfer to import P2 files. The material is on an external FW800 drive. I go to Add Custom Path in the Log and Transfer dialog box, point the software to the CONTENTS folder of each captured P2 card, the list populates with the clips, I drag the files into the que, and they import as usual. All is well and good until I X out of Log and Transfer, and when I do that, FCP crashes. I have not experienced this when capturing directly from a camera. This has happened over and over since beginning this project, and we are still yet to get all the material into the machine for editing.
Also, in case it is pertinent, I am using a MacBook Pro 2.2 GHz Core i7 machine with 8GB RAM.
Any ideas or has anyone else experienced this? Thanks in advance!
-VanFirst thing I'd try is trashing your preferences. Google preference manager from digital rebellion. It's a free download and in invaluable. It's so cool you'll WANT to pay for it. It allows you to store a good set of preferences, trash them when they get funky and then restore the good set, including all the cool stuff you created.
ANYWAY, I'm in the habit of saving every which way from Tuesday after something interesting has happened, like a capture or L&T. I know that's not a solution, but a best practice. hopefully a pref trash will set you right. -
Skype keeps crashing after log in 7.3.0.101
Whenever I try to launch Skype, it loads the homepage (after logging in) and then immediately crashes. This has been happening for a few months now and with every skype account that I've tried. I've reinstalled several times (including deleting all skype files on my computer+registery and resetting all my settings), but nothing.
Running Windows 7, 64-bit.
Problem Event Name: APPCRASH
Application Name: Skype.exe
Application Version: 7.3.0.101
Application Timestamp: 5512b3c5
Fault Module Name: CESpy.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5085a464
Exception Code: c0000005
Exception Offset: 0000c28d
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I've tried everything I could find in the discussions. Help?
Attachments:
diagnostics.pdf 250 KBruwim wrote:
Jack2626 wrote:
Hi, im having the ame issue but from fault module:
Problem Event Name: APPCRASH
Application Name: Skype.exe
Application Version: 7.3.60.101
Application Timestamp: 5512d489
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: 0eedfade
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Any help would be greatly appreciated.
Please, run the DirectX diagnostics tool.
Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
Be aware that you will have to zip this file before attaching it here.
Attachments:
DxDiag.zip 9 KB -
Firefox 19 Crashes after logging into Facebook
Java version installed: Java 7 Update 17
Adobe Flash: 11.6 r602
Everytime I log in to Facebook using Firefox, the browser crashes.
It also crashes when i Restart with Add-Ons Disabled.
When i type about:crashes in the address bar no crash reports are displayed.
Can anyone please help?Problem Solved, Installed Firefox 20.0 Beta version and no problems at all so far. Firefox not crashing when logging into facebook.
-
CUPC 8.6.3.20802 crashes after logging in successfully System version 8.6.2.100000-44.
Hi there,
At my company i have a Dell Latitude E6330 laptop running version 8.6.3.20802 of the CUPC.
The program appears to crash and auto shut down right after I appear to successfully log into it.
We are running System version 8.6.2.100000-44.
It does not seem to happen to other users on the same laptop model as me, we have tried to reinstall and re-image my machine as well as even clear out my Windows Roaming profile to start fresh it still crashes. It appears that when I try to log on to another Dell Desktop it will work but when I go back to my laptop it does the same thing.
I have found a few different logs however I do not want to spam my thread with every single log that the Communicator gives me. I have tried to turn on Detailed Logging however the application crashes before it is able to be turned on.
If you guys could please let me know where I could find some log information which I could post up and give me some assistance in troubleshooting the issue that would be great.
I am part of the IT department at my firm and we have already tried various troubleshooting steps but any extra assistance would be great!
Thanks heaps in advance!Hello,
Was this ever resolved? i am facing the same issue -
Thinkpad S440 systematic crashes after upgrade to Win 8.1
Hi,
After installing Windows 8.1 I've had big problems with my brand new Thinkpad S440. The laptop has generated systematic bluescreens, mostly related to the Intel Wireless-N 7260 WiFi module. Disabling it in the Device Manager helped a little bit, but I also get other Bluescreens related to e.g.. to "usbxhci.sys" and other modules. After the BSoD the laptop always goes into a reboot-loop at the Lenovo logo during the boot-up with the only solution do do a hard shut down (keeping the power-button pressed for 5 sec).
Yesterday I tried doing a fresh install, but it did not help at all. A few minutes after installing Win 8.1 from scratch the laptop generated a bluescreen.
I have updated all drivers to the latest version, and also tried to solve it by installing an earlier version of e.g. the WiFi driver. Neither one has helped.
Below is a list of the minidumps generated during BSoD's I've had during the last 12 hours since installing a fresh copy of Windows 8.1.
Please, what can I do about this situation? I would not like to return the machine since I like the hardware, but in the current state my Thinkpad S440 is useless. I have not found a way going back to Windows 8.0, since the recovery partition on the HDD apparently was destroyed (according to an Microsoft engineer) during my first trial to update to Win 8.1. (the first update ended in a Black Screen of Death). Microsoft was only willing supply me with a Win 8.1 product key (since a clean install was the only way to recover from the Black Screen of Death back then), which, of course, doesn't work for installing Win 8.0.
System Information (local)
computer name: LENOVO
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: 20AY001DMS, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8284897280 total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 11/20/2013 1:12:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4734-01.dmp
This was probably caused by the following module: storport.sys (storport+0x1400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000740400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 1:12:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: storport.sys (storport!memset+0xC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000740400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 10:03:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-9437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A67DE929, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 11/20/2013 10:03:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: storport.sys (storport!StorPortExtendedFunction+0xEBB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A67DE929, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 6:23:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4750-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C71AFE)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80002C71AFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 10:50:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4375-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C5DAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 8:50:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-4921-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002EFDB12)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF80002EFDB12)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 8:02:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-5640-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C76B12)
Bugcheck code: 0xD1 (0x1038, 0x2, 0x0, 0xFFFFF80002C76B12)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 7:38:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-7296-01.dmp
This was probably caused by the following module: netwbw02.sys (0xFFFFF800021A763A)
Bugcheck code: 0xD1 (0xFFFFE00069F99A4D, 0x2, 0x0, 0xFFFFF800021A763A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netwbw02.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUALIs there something I can disable in the Device Manager to stop USBXHCI.sys from crashing?
On Wed 11/20/2013 8:57:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11421-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CF2AFB)
Bugcheck code: 0xD1 (0xFFFFE008048F5240, 0x2, 0x0, 0xFFFFF80002CF2AFB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:57:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0xD1 (0xFFFFE008048F5240, 0x2, 0x0, 0xFFFFF80002CF2AFB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:52:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5265-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F3EAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:47:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11218-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C97AFE)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80002C97AFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:29:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5218-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CE9B20)
Bugcheck code: 0xD1 (0x2261DC, 0x2, 0x0, 0xFFFFF80002CE9B20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:20:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11140-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002D44AFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:08:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5000-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E9DAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 7:46:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11093-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C90AFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 6:53:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4937-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CBAB20)
Bugcheck code: 0xD1 (0x225EEC, 0x2, 0x0, 0xFFFFF80002CBAB20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 6:21:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-10140-01.dmp
This was probably caused by the following module: storport.sys (storport+0x1400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800006BF400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -
Yahoo Messenger crashes after logging in
Just purchases a new Macbook Pro pre-installed with Leopard to which I installed YIM..after I log in the YIM crashes...deleted YIM, associated files in Library, etc and re-installed YIM...same issue...since this was the only additional software I had initially loaded onto my MBP. re-installed Leopard without backup of previous system and then re-installed YIM to see if this would resolve the issue...same occurring problem with YIM when I log in...am at a loss as what to do...
my gf uses my old 2006 powerbook with Leopard and has no problem with running YIM on the PB nor does my daughter's new macbook running Leopard...
any suggestions would be helpful...the first forum user who can solve my problem will receive a new hunky, musky male scented Hasselhoff hand cream with dispenser...: )Hi..
Since you are running Lion v10.7.3, you need to use Lion Recovery to repair the startup disk if necessary, or reintall the Mac OS X. Not Disk Utility. -
Firefox crashes after logging into Gmail account
Firefox (ver. 26.0 German) crashes without being able to report the crash!
I have found another crash report on this, BUT I have more detailed information on this issue.
Crashing started to happen, after I changed the privacy configuration as follow:
1st: I changed the config. from "accepting thirdparty cookies" from "yes" to "never" and
2nd: from "keep cookies until expiration" to "until close firefox".
Then I deleted all cookies.
From then, FF crashes when I'm loggint into Gmail, which is successful, but after two ajax/jquery "load()" calls (I can see the animation of reload icon twice!) FF crashes.
I was working with FF/Gmail before I changed the configuration, and everything was working well (I deleted cookies everytime I logged out of gmail). Nearby: I changed the configuration as there was only one Tab in one Window (my own static local startpage) open, and I was not logged in my Gmail account.
I have scanned (fullscan) my PC by "Kaspersky Internet Sec. 2014" (no malware found) +
I have scanned (fullscan) my PC by "Spybot - Search & Destroy" (no malware found) +
I looked into "Windows-Software" but there was no "BitGuard" +
I have deactivated all of Addons,
but FF crashes again and again.
When I change the config. to default, i.e. accepting thirdparty cookies and keeping them until they expire, FF does not crash anymore!
Hope this helps and has nothing to do with an NSA "feature/function" ;-)
Kindly Regards,
PedramThe issue was not Gmail, nor Firefox, nor OS.
It was Bugfire plugin, which does not really stop tracking scripts!
I found and solved the problem by (step by step):
''(Please keep in mind that I am using German version, so some translations my not be 100%ly correct in FF English version!)''
1. loggins as Administrator
2. backing up the bookmarks etc.
3. deactivating all Plugins
4. unistalling all Plugins and modules ([[https://support.mozilla.org/en-US/kb/disable-or-remove-add-ons|disable-or-remove-add-ons]])
5. uninstalling Firefox in Windows (Start ==> System Control ==> Software ==> (rightclick) Firefox ==> "remove", "Yes")
6. running explorer and navigate to "'''%tmp%'''" (without doublequotes!)
7.''' [CTRL + A] t'''o mark all temporary files and folders
8.''' [DEL]''' to delete them
9. Reboot
10. Installing Firefox
11. Testing Gmail -> it worked
12. changed configuration of Firefox to: "accept cookies form thirdparties" ==> "Never", and "keep until:" ==> "Firefox closes"
13. Restarted FF, logged into Gmail ==> it worked!
14. Then I started systematically installing plugins, started by "Adblock Plus" etc. one by one. After installing every Plugin I restarted FF and could log onto Gmail successfully, except after activaten of "Firebug".
My question: will this report be forwarded to firebug, or do I have to report it to the firebug Team (this is my first reporting on this site)?
Kindly Regards,
Pedram Ganjeh-Hadidi -
Adobe reader for iOS crashes after log in for online storage
I need help with this... Thanks
Thank you for the information. We are investigating the issue at our end. It would be great if you could send us the crash logs at [email protected]
For crash logs , please sync your device with iTunes and then find the crash logs at
* Mac OS X : ~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>
* Windows XP: C:\Documents and Settings\<USERNAME>\Application Data\Apple computer\Logs\CrashReporter/<DEVICE_NAME>
* Windows Vista & Windows 7: C:\Users\<USERNAME>\AppData\Roaming\Apple computer\Logs\CrashReporter/MobileDevice/<DEVICE_NAME>
* The log files' names start with the application name and have the extension "crash".
Regards,
Ankit -
Application Manager Crashing After Log In
I'm a subscriber to the Creative Cloud. Both my MacBook Pro and iMac show one Adobe update available in the menu bar. When I attempt to open the updater, it launches the the Adobe Application Manager, which asks me for my user name and password. After entering this information, though, the Adobe Application Manager crashes. I've tried simply relaunching the application, rebooting my computer... nothing is resolving this issue.
After viewing some other discussions here, I ended up spending a good portion of last Sunday afternoon simply un-installing all of my CS6 apps while keeping my preferences, running the CS Cleaner Tool, and then re-installing them all on my MacBook Pro.
Your advice about creating a separate user account with Admin. privileges did work on my iMac, though. Saved a lot of time. Thankfully, I haven't had an issue with it since then [fingers crossed].
- Don -
[SOLVED] nVidia driver 195.36.08 causes KDE4.4 to crash after logging?
Hi to all Archers
I noticed the new nVidia driver (195.36.08) on pacman's yesterday updates, I didn't update it immediately and preferred to wait until I was available to fiddle with it in case things went wrong. Apparently, that was the case
Here's what happens if I install the new driver:
KDM starts as usual, I login in, I see KDE loading progress and before it finishes, boom it crashes and returns to KDM login once again.
I tried reinstalling KDE, Xorg and read nVidia wiki to see if there is any hints. I tried once again with a new stock xorg.conf, and removed .nvidia-settings-rc and even disabled KDE compositing but all this couldn't help getting KDE up and running.
However, when I reinstall the previous version (190.53) everything is back to normal.
So what I want to know is am I the only one who gets this problem or there're others here having the same issue?
Because the first time I installed the nVidia driver (almost 3 months now) I used their own installer then used Arch packages afterwards, I suspect that perhaps their installer messed things up !?
For now the solution is to stick to the previous version.
I'm using Arch Linux 32bit and my GC is an nVidia 7300GT.
Regards,
Med
Last edited by stuntgp2000 (2010-03-08 00:17:10)zero-giulio wrote:
I want to install the 190.53 version of nvidia driver, because it's the correct driver version for my video card, according to nvidia site (see http://www.nvidia.com/object/linux_disp … 0.53.html).
Also, in my prevoius arch system I installed that version and everything worked well. I don't want to try the newerr version. It doesn't matter if 190.53 are not the latest driver available. I'm self confident with the 190.53 version.
How can I install them? The problem is that pacman suggest me only the latest version :-(
You'll find them here http://schlunix.org/archlinux/extra/os/ after choose your system architecture.
if you want to know more about downgrading for more than a few packages read this guide http://wiki.archlinux.org/index.php/Dow … g_Packages
Assuming you have a recent nvidia graphic card and using a i686 system you should download these:
http://schlunix.org/archlinux/extra/os/ … pkg.tar.gz
http://schlunix.org/archlinux/extra/os/ … pkg.tar.gz
Good luck, -
CS4 crashes after update on win XP...
I just updated CS4 with the latest patches and it started to crash when I try to publish one of my flashfiles.
The file uses actionscript 2 and worked just fine before the upgrade.
Anyone else have similar experiences?Unfortunatley not, due to corporate policies.
Do you know if the flashcompiler/environment generate any logfiles when publishing?
Build logs or errorlogs?
Is there any way I can find out which step of the build is causing the crash?
Regards,
Torbjörn. -
Background Black after logging in, Win 7
After moving computers on the domain to another location and changing the names. The users logged in and they got a black background. They were not able to change the wallpaper but they could change the color from black to something else. When I log in I
get the normal wallpaper I always have. I am a domain administrator.
Why is this happening? How do I fix this?When you disconnected them then reconnected them at a different point in the network they were most likely staged (within Active Directory) and are just waiting to be added properly back into the domain (which is a simple drag and drop operation).
If I had my server up and running I'd point you to the exact location but its waiting on some new hardware, sorry.
Please remember to flag a post that helps you as "answer" so that it may help others with same problems.
I moved the computers into the right OU. This did not fix the problem. They still have the black background instead of wallpaper.
Maybe you are looking for
-
I am working on a site in wordpress and realized that it's visible in all browsers except Firefox. Could you give me some info on how to fix this issue?
-
Its important that all characters display correctly in my pdf.
When I convert a file to pdf, I always get this error: Cannot extract the embedded font'HWNDJR 83mkhgdligynvro' some characters may not display correctly. What is wrong? Its important that all characters display correctly in my pdf ebook. Please advi
-
Photoshop images into Illustrator
I want to use a shape created in Photoshop with a style applied.When I bring it into Illustrator, apply Live Trace, the style disappears. How can I keep the style intact?
-
Quotation number from Service order or notification
Hi, As per the process, we create service quotation from service order using the transaction DP80. I can get the service order number from the quotation (VBAK-AUFNR). But I need to get this quotation number from service order or service notification
-
Root node contains specific attribute could make the XSLT transfrom fail
I have to convert EJB deploy desciptor in my project, but I found that XML format transfrom with Apache Xalan will fail when the root node contants some specific attribute. Here is an example: Input XML file: <?xml version="1.0" encoding="ISO-8859-1"