Flickering of screen (pulse) immediately after the start

Similar Questions

• HP10 1901 Tablet: Tablet 10 1901 hp stops immediately after the start, despite the load fully

  Hello

  My hp 10 Tablet has less than two years, and I don't use much.  The problem started with the volume suddenly down to zero out of control, and even if I press the volume up button, the volume is just down once again, when I let the button.  And then the Tablet has started to close automatically, even when it has a lot of power left, as more than 50%.  Now, even if I have fully charged, when I press the power, immediately after the start, it says, 'stop' and he just stops.  I try to turn it on again, and the same story is repeated.  I'm just fet upward.  What is a mechanical problem or a software problem?  I don't understand.  Please help me.

  Hello and welcome to the HP support community!

  It is difficult on this side of the screen of remote diagnosis your problems!

  You should try to eliminate the causes of the problem.  Only thing we recommend is to first try a Factory Reset.  It recharges a clean copy of the OS.  If she solves problems, then you're done!

  If problems persist or get worse, then it is probably related to the material.  Damaged the volume button, USB port, due to lack of battery, etc.

  Perform a factory reset on your tablet.

  WyreNut

• MU computer stops immediately after the start-up or attempts repeated; So sometimes minutes after;

  The computer stops immediately after the start, repeatedly or a few minutes after have managed to start it. The error log showed two evenys:

  (1) the service Acquisition of Image Windows (WIA) suspended at startup; (2) the server {81ED811 A1F4E726-8CF1 - 11 D 1-BF92-00600} is not registered with DCOM within the required time.  After restarting the computer, and after installing all of the updates, I installed the last printer; I unplugged the printer and the computer booted immediately!  Does anyone have suggestions, and if I have to update the drivers (hp Laser jet 5 p & hp scanjet 5370C;) How? Please help, frustration to a max; Thank you very much; HeinrichDS

  HeinrichDS

  Recommendation of the Palcouk of sense what is the operating system and is worth a try.  If you're still having problems, then you need to talk to specialists in XP (because it is a Forum for Vista).  In this case, please transfer your question in the Forums of XP to http://social.answers.microsoft.com/Forums/en-US/category/windowsxp where the XP experts will be happy to help you.

  Good luck!

  Lorien - MCSA/MCSE/network + / has + - if this post solves your problem, please click the 'Mark as answer' or 'Useful' button at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.

• vmplayer - 5.0.0 ends immediately after the start

  Hello

  I'm under fedora 17 with 3.5.2 - 3.fc17.x86_64 kernel and VMware-Workstation-full-version 9.0.0 - 812388.x86_64.bundle.
  vmplayer - 5.0.0 ends immediately after the start.

  vmplayer - 5.0.0 runs only with kernel - 3.4.0 - 1.fc17.x 86_6 4

  The content of the vmware-modconfig - 5653.log file looks as follows:

  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: Log for VMware Workstation pid = 5653 version = version 9.0.0 Build = build-812388 option = output
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: The process is 64-bit.
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: Host codepage = UTF-8 encoding = UTF-8
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: Host is the version of Fedora Linux 3.5.2 - 3.fc17.x86_64 17 (Beefy Miracle)
  2012-08-23 T 20: 00:54.505 + 01:00 | vthread-3 | I120: Msg_Reset:
  2012-08-23 T 20: 00:54.505 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': Datei oder Verzeichnis nicht found.
  2012-08-23 T 20: 00:54.505 + 01:00 | vthread-3 | I120: —————————————-
  2012-08-23 T 20: 00:54.505 + 01:00 | vthread-3 | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: Msg_Reset:
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / home/martin/.vmware/config ': Datei oder Verzeichnis nicht found.
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: —————————————-
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | I120: Optional preferences PREFS not found in home/martin/.vmware/config file. Using the default values.
  2012-08-23 T 20: 00:54.506 + 01:00 | vthread-3 | W110: Connecting to /tmp/vmware-martin/vmware-modconfig-5653.log
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Reading in info for the vmmon module.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Reading in info for module vmnet.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Reading in info for the vmblock module.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Reading in info for vmci module.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Reading in info for the vsock module.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Definition of vsock to depend on vmci.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Created new pathsHash.
  2012-08-23 T 20: 00:54.511 + 01:00 | vthread-3 | I120: Modinfo calling over 'vmmon.
  2012-08-23 T 20: 00:54.513 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012-08-23 T 20: 00:54.513 + 01:00 | vthread-3 | I120: Modinfo invoking on "vmnet".
  2012-08-23 T 20: 00:54.516 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012-08-23 T 20: 00:54.516 + 01:00 | vthread-3 | I120: Modinfo invoking on 'vmblock '.
  2012-08-23 T 20: 00:54.519 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012-08-23 T 20: 00:54.519 + 01:00 | vthread-3 | I120: Modinfo calling over 'vmci.
  2012-08-23 T 20: 00:54.521 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.
  2012-08-23 T 20: 00:54.521 + 01:00 | vthread-3 | I120: Modinfo calling over 'vsock.
  2012-08-23 T 20: 00:54.523 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.

  The content of the file looks like kernel.log as follows:

  August 23 at 20:01:01 localhost kernel: [710.974813] general protection fault: 0000 [#5] SMP
  August 23 at 20:01:01 localhost kernel: [710.974818] CPU 1
  August 23 at 20:01:01 localhost kernel: [710.974819] Modules related to the: stv0299 ves1x93 dvb_ttpci ttpci_eeprom saa7146_vv saa7146 dvb_core videobuf_dma_sg videobuf_core v4l2_common videodev media exactly bluetooth rfkill vmnet (O) (O) vsock vmci (O) (O) vmmon fuse snd_hda_codec_hdmi ppdev coretemp lpc_ich mfd_core nvidia (IN.) snd_rme96 snd_hda_codec_analog serio_raw parport_pc parport skge sky2 nfsd lockd sunrpc kvm_intel i2c_ auth_rpcgss nfs_acl i2c_i801 shpchp core KVM snd_hda_intel snd_hda_codec snd_hwdep snd_pcm asus_atk0110 uinput microcode snd_page_alloc snd_timer snd soundcore binfmt_misc firewire_ohci firewire_core crc_itu_t edac_core i82975x_edac [last unloaded: scsi_wait_scan]
  August 23 at 20:01:01 localhost kernel: [710.974851]
  August 23 at 20:01:01 localhost kernel: [710.974853] Pid: 6227, comm: vmware-vmx Tainted: manufacturer of P D O 3.5.2 - 3.fc17.x86_64 #1 rod system product name/P5WDG2 WS PRO
  August 23 at 20:01:01 localhost kernel: [710.974855] RIP: 0010: [] [] HostIF_SafeRDMSR + 0xf/0 × 30 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974863] RSP: 0018:ffff88016e7e5b88 EFLAGS: 00010246
  August 23 at 20:01:01 localhost kernel: [710.974864] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 000000000000048b
  August 23 at 20:01:01 localhost kernel: [710.974866] RDX: 0000000000000000 RSI: ffff88016e7f2590 RDI: 000000000000048b
  August 23 at 20:01:01 localhost kernel: [710.974867] RTB: ffff88016e7e5b88 R08: R09 ffff8801bfc96610: ffffffffa0d46672
  August 23 at 20:01:01 localhost kernel: [710.974868] R10: 0000000000000038 R11: 0000000000003246 R12: 0000000000000000
  August 23 at 20:01:01 localhost kernel: [710.974869] R13: ffff88016e7f2580 R14: ffff88016e7f2580 R15: 00007fffdfd66850
  August 23 at 20:01:01 localhost kernel: [710.974871] FS: 00007ff5cd372740 (0000) GS:ffff8801bfc80000 (0000) knlGS:0000000000000000
  August 23 at 20:01:01 localhost kernel: [710.974872] CS: 0010 DS: 0000: 0000 CR0: 0000000080050033
  August 23 at 20:01:01 localhost kernel: [710.974874] CR2: 000000000099ca 10: 00000001446 d 5000 CR4 CR3: 00000000000007e0
  August 23 at 20:01:01 localhost kernel: [710.974875] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
  August 23 at 20:01:01 localhost kernel: [710.974876] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
  August 23 at 20:01:01 localhost kernel: [710.974878] vmware-vmx process (pid: 6227, threadinfo ffff88016e7e4000, task ffff8801b2699710)
  August 23 at 20:01:01 localhost kernel: stack [710.974879]:
  August 23 at 20:01:01 localhost kernel: [710.974880] ffff88016e7e5bb8 ffffffffa0d48e23 ffffffffa0d48da0 ffff88016e7e5be8
  August 23 at 20:01:01 localhost kernel: [710.974883] ffff88016e7f2580 ffff88016e7e5bd8 0000000000000000 ffffffffa0d47780
  August 23 at 20:01:01 localhost kernel: [710.974885] ffff88016e7f2580 00000000fffffff4 ffff88016e7e5c08 ffffffffa0d4ac1c
  August 23 at 20:01:01 localhost kernel: [710.974888] Scout:
  August 23 at 20:01:01 localhost kernel: [710.974892] [Vmx86GetMSR] + 0 × 83/0xd0 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974896] []? Vmx86GetUnavailPerfCtrsOnCPU + 0 × 0 × 150/150 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974900] [HostIF_CallOnEachCPU] + 0 × 0 × 20/40 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974904] [] Vmx86_GetAllMSRs + 0x2c/0 × 50 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974907] [] LinuxDriver_Ioctl + 0x70f/0xd40 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974911] []? unlock_page + 0 × 0 × 31/50
  August 23 at 20:01:01 localhost kernel: [710.974914] []? __do_fault + 0x3f9/0 × 560
  August 23 at 20:01:01 localhost kernel: [710.974916] []? handle_pte_fault + 0 × 95/0xb10
  August 23 at 20:01:01 localhost kernel: [710.974920] []? ext4_file_write + 0xbf/0 × 260
  August 23 at 20:01:01 localhost kernel: [710.974922] []? free_pages_and_swap_cache + 0xad/0xd0
  August 23 at 20:01:01 localhost kernel: [710.974924] []? handle_mm_fault + 0 × 259/0 × 320
  August 23 at 20:01:01 localhost kernel: [710.974927] []? do_page_fault + 0x1bc/0x4b0
  August 23 at 20:01:01 localhost kernel: [710.974930] [LinuxDriver_UnlockedIoctl] + 0 × 0 × 18/20 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974933] [do_vfs_ioctl] + 0 99/0 × 580 ×
  August 23 at 20:01:01 localhost kernel: [710.974935] [sys_ioctl] + 0 × 99/0xa0
  August 23 at 20:01:01 localhost kernel: [710.974937] [system_call_fastpath] + 0 × 16/0x1b
  August 23 at 20:01:01 localhost kernel: [710.974938] Code: 83 c4 e8 a6 01 84 3rd e0 44 89 e0 48 3 b 43 08 and 72 e9 48 89 df e8 33 b4 42 e0 eb 9th 90 55 48 89 e5 66 66 66 66 90 31 c0 89 89 32 31 f9 c2 ff 41 89 c0 48 e2 20 89 f8 4 c 09 48 89 16 5 c2 c1 d c3
  August 23 at 20:01:01 localhost kernel: [710.974962] RIP [] HostIF_SafeRDMSR + 0xf/0 × 30 [vmmon]
  August 23 at 20:01:01 localhost kernel: [710.974966] RSP
  August 23 at 20:01:01 localhost kernel: [710.974968] - [end trace 04aa45b3d8c2dbda].

  VMware kernel modules compiles well

  [root@fc17 tmp]# vmware-modconfig --console --install-all
  Stopping vmware (via systemctl):                           [  OK  ]
  Using 2.6.x kernel build system.
  make: Entering directory `/tmp/modconfig-C4tvy7/vmmon-only'
  /bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
  make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/linux/hostif.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/linux/driver.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/linux/driverLog.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/apic.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/memtrack.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/hashFunc.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/vmx86.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/cpuid.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/task.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/comport.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/phystrack.o
    CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/vmcore/moduleloop.o
    LD [M]  /tmp/modconfig-C4tvy7/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC      /tmp/modconfig-C4tvy7/vmmon-only/vmmon.mod.o
    LD [M]  /tmp/modconfig-C4tvy7/vmmon-only/vmmon.ko
  make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
  make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmmon-only'
  make[1]: »postbuild« ist bereits aktualisiert.
  make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmmon-only'
  cp -f vmmon.ko ./../vmmon.o
  make: Leaving directory `/tmp/modconfig-C4tvy7/vmmon-only'
  Using 2.6.x kernel build system.
  make: Entering directory `/tmp/modconfig-C4tvy7/vmnet-only'
  /bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
  make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/driver.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/hub.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/userif.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/netif.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/bridge.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/filter.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/procfs.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/smac_compat.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/smac.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/vnetEvent.o
    CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/vnetUserListener.o
    LD [M]  /tmp/modconfig-C4tvy7/vmnet-only/vmnet.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC      /tmp/modconfig-C4tvy7/vmnet-only/vmnet.mod.o
    LD [M]  /tmp/modconfig-C4tvy7/vmnet-only/vmnet.ko
  make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
  make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmnet-only'
  make[1]: »postbuild« ist bereits aktualisiert.
  make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmnet-only'
  cp -f vmnet.ko ./../vmnet.o
  make: Leaving directory `/tmp/modconfig-C4tvy7/vmnet-only'
  Using 2.6.x kernel build system.
  make: Entering directory `/tmp/modconfig-C4tvy7/vmblock-only'
  /bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
  make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/filesystem.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/file.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/block.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/module.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/super.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/control.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/stubs.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/inode.o
    CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/dentry.o
    LD [M]  /tmp/modconfig-C4tvy7/vmblock-only/vmblock.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC      /tmp/modconfig-C4tvy7/vmblock-only/vmblock.mod.o
    LD [M]  /tmp/modconfig-C4tvy7/vmblock-only/vmblock.ko
  make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
  make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmblock-only'
  make[1]: »postbuild« ist bereits aktualisiert.
  make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmblock-only'
  cp -f vmblock.ko ./../vmblock.o
  make: Leaving directory `/tmp/modconfig-C4tvy7/vmblock-only'
  Using 2.6.x kernel build system.
  make: Entering directory `/tmp/modconfig-C4tvy7/vmci-only'
  /bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
  make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/linux/driver.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/linux/vmciKernelIf.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciDriver.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciResource.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciRoute.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciContext.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciDatagram.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciHashtable.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciEvent.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciQueuePair.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciQPair.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciDoorbell.o
    CC [M]  /tmp/modconfig-C4tvy7/vmci-only/driverLog.o
    LD [M]  /tmp/modconfig-C4tvy7/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC      /tmp/modconfig-C4tvy7/vmci-only/vmci.mod.o
    LD [M]  /tmp/modconfig-C4tvy7/vmci-only/vmci.ko
  make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
  make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmci-only'
  make[1]: »postbuild« ist bereits aktualisiert.
  make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmci-only'
  cp -f vmci.ko ./../vmci.o
  make: Leaving directory `/tmp/modconfig-C4tvy7/vmci-only'
  Using 2.6.x kernel build system.
  make: Entering directory `/tmp/modconfig-C4tvy7/vsock-only'
  /bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
  make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/af_vsock.o
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/vsockAddr.o
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/notifyQState.o
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/util.o
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/stats.o
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/notify.o
    CC [M]  /tmp/modconfig-C4tvy7/vsock-only/driverLog.o
    LD [M]  /tmp/modconfig-C4tvy7/vsock-only/vsock.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC      /tmp/modconfig-C4tvy7/vsock-only/vsock.mod.o
    LD [M]  /tmp/modconfig-C4tvy7/vsock-only/vsock.ko
  make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  /bin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
  make[1]: Entering directory `/tmp/modconfig-C4tvy7/vsock-only'
  make[1]: »postbuild« ist bereits aktualisiert.
  make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vsock-only'
  cp -f vsock.ko ./../vsock.o
  make: Leaving directory `/tmp/modconfig-C4tvy7/vsock-only'
  Starting vmware (via systemctl):                           [  OK  ]

  The two files "/ usr/lib/vmware/settings ' and ' / home/martin/vmware/config ' do not exist.
  Now the question is, how do I create these files or what files should be removed from the old settings. ?

  Why are there vmplayer immediately after startup. ?

  I had what I think it's the same problem on 9, Fedora-17 64-bit workstation.

  I used the patch vmmon here:

  http://communities.VMware.com/thread/400616?start=15&TSTART=0

  and modifed the patcher created by Artem S. Tashkinov to apply it.

  Solved it for me, I hope for you, too.

• Just upgraded window 7 for windows 10 and photoshop CC 2015 accident immediately after the start

  someone knows how to fix this?

  Hi Gabriele,

  Thanks for posting on the Adobe forums.

  Please follow these steps:

  1. press SHIFT while launching Photoshop. It allows to disable 3rd party plugins.

  2. press CTRL + SHIFT + ALT when you launch photoshop. It resets the preferences.

  3. Please submit the Eventviewer error message. This link will help you: http://www.cyberlink.com/support/faq-content.do?id=10449

  Kind regards

  Sandeep

• SignalExpress closes immediately after the splash screen

  I'm having a problem with the Software NI SignalExpress where the application fails to open completely - it closes immediately after the splash screen. I am using windows XP Pro. SP3.

  I tried to uninstall, registry errors compensation and reinstall, I also tried the repair installation - or who work.

  A test of SignalExpress installation was installed on my PC until I got a full copy with the purchase of a data acquisition (usb-6218).

  Hi André,.

  Sounds a bit nasty. If repairing and reassembling and all this malarky does not recommend the use of msiblast to clean your computer of all the software of NOR and starting again with a new install. When you software uninnstall he didn't get rid of everything, there is still hidden folders around dootted.

  I joined msiblast.exe.

  -Run msiblast

  -Make sure the radio button "Show OR installers only" is selected.

  -Select all and then click on uninstall.

  When this is complete, your computer will be NOT free. After that;

  -Install all software from OR you for example LabVIEW Signal express

  -Then install the drivers. The USB-6218 case uses the DAQmx driver that the latest version can be downloaded from this link.

  If it persists then write again.

  Kind regards

• HP Pavilion 500-330 Desktop PC blue screen with the cursor after the start

  I have a desktop computer Pavilion 500-330 Windows 8.1 running on a 64-bit system. The problem is after the start, a blue screen with a cursor appears, and the computer does not go to the lock screen.  I did restore, get updates and even left the only blue screen, but after many hours, he was always there.  If I do a force re-booting, the lock screen comes, but not always immediately.  There is no problem to wake up when it is in "standby".

  Any help will be appreciated.

  Hello again @padway,

  Actually, if you already did a cover of the plant on your computer the problem you describe seems to be a physical problem. Please contact our technical support at the 800-474-6836. If you do not live in the United States / Canada region, please click the link below to get help from your region number. http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html. As a recovery plant excludes any kind of software problem this is your best course at this time. A technician from the local computer or a computer repair shop may be an option if you are not in the warranty as well.

  I want to thank you for display on the HP Forums. Have a great day!

• Screen does not light after the start, but after standby on Satellite M100

  Hello
  I have some experience with computers and laptops, but this problem exhausted all of my knowledge.
  My girlfriend has a Toshiba Satellite M100, PSMA1E. He currently works on Windows XP, SP3.
  The laptop has always had problems closing/stand bye. He would stand bye and the screen would not. She would usually be manually turn off (holding the power button) and restart.

  Same thing happened last week, but with me. I turned off the power button but when I turned it on the screen was completely black. After a few attempts, I realized that everything worked; I could hear the usual audio files and XP Boot, but there was no way I could get the job of the screen.

  The strangest thing is that the CMOS/BIOS, one with the Toshiba logo settings screen, also does not appear. If it's an OS problem, I thought that I would be able to access the BIOS at least, but it does not work. FN + F5 does not work.

  Then, strange yet something happened. I was turning it on and off with keyboard shortcuts and I realized that if I put on stand bye using shortcuts and then go back on the screen turns on perfectly well (there is a cause of adjustment resolution icons are irrelevant, but it works perfectly fine).

  From that on I tried everything I know. Update the BIOS, all Windows XP updates, all Toshiba QuickFix, cleaning the registry with different tools, uninstall and reinstall the video driver (ATI Radeon X 1400) utility, shortcuts keyboard, power saver, tools hardware Toshiba, looking to start up programs, services, everything I could possibly think off.

  What intrigues me is that the Toshiba start screen will not be displayed. I can't access the BIOS, but I tried to restore the standard values of the BIOS with Toshiba hardware tools. It did not work. I don't even know if reinstalling XP will work because whenever I turn it on it is all black and I have to make the stand bye / Tower on Tower.

  When I have it plugged into an external monitor, I could see all starting the process (initial screen of the BIOS and Windows). I then tried to access the video driver display configuration but it would show only the external monitor. It would only detect the laptop screen after a stand bye / turn back on, and then it worked perfectly: the screen two screens simultaneously, extended, everything. Ah, changing BIOS selection automatic the LCD + external monitor does not work.

  I am really puzzled here and I can't understand it. I really don't think it's a hardware problem, because the screen works 100% after the stand bye. I guess that XP is do something during the closing down that completely 'stops' my screen, even after starting, and then I can only turn it on with the thing stand bye.

  Any help would be really appreciated!

  Best,

  Hi guys

  I had a similar problem on a series of Satellite A200 and I could solve works to update the BIOS and update the graphics driver.
  In addition, you must make sure that all available MS fixes and patches have been installed.

  Unfortunately, but that's all I can suggest. If the problem persists and you would not be able to solve update components then an ASP needs to check.

  Good luck

• no user accts are visible, after the start, on the family windows xp login screen

  have HP pavilion zd7000 with windows XP Home edition OS... after the start there is no visible user accounts to choose from... There should be 2 it... Owner and my name... no password were assigned to each user account, don't know how it happened was working perfectly for months... now I can't past the login screen... someone can help me? .. .thanks in advance

  When the login screen appears, try pressing Ctrl-Alt-Del twice.  This should bring up a classic connection window.  Enter the user name and password (if there is one) and see if you can connect in this way.

  HTH,

  JW

• My screen goes black and the start menu does not load after start up logo and the only thing on the screen I see is my mouse pointer

  My screen goes black and the start menu does not load after start up logo and the only thing on the screen I see is my mouse pointer

  Hello

  You can access Mode safe? Repeatedly press F8 as you start? If yes you can try Control Panel - device
  Manager - graphics card - Double click on - driver tab - click on UPDATE driver - then right click
  on devices and UNINSTALL - REBOOT.

  Another method to try to get to the desktop (try in normal Windows Mode without failure)
  CTRL + ALT + DELETE and on the tab process EXPLORER.exe and COMPLETE the PROCESS on this subject - then
  on the Applications tab - lower right - new task - type in EXPLORER.exe. Safe mode is reached
  by tapping F8 as you start several times.

  First check this thread in case it is simple and if not to come back to this thread.

  http://social.answers.Microsoft.com/forums/en-us/vistaprograms/thread/50247d5e-0ae0-446c-A1bd-11287fd1478a

  Black screen problems are extremely difficult to repair and all patch is usually on a base hit or miss.
  That there is no information on a black screen as it is on a blue screen just adds to the
  Difficulty. Often using a restore point or Startup Repair will have no effect. You can try a
  Google to see the proposed repairs, whom some have worked however these cover a wide
  field efforts.

  Here's a video of one of them.

  http://www.Google.com/search?hl=en&q=black+screen+of+death+Vista&btnG=search&AQ=f&OQ=&AQI=G1

  Here's another fix
  http://blogs.PCMag.com/SecurityWatch/2008/12/the_mysterious_black_screen_of.php

  You have a Vista disk? You can try restoring the system to it. If you do not have your system disks
  manufacturer will sell them at low prices. Or try in safe mode if you can get there.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

  You can create a recovery disc or use someone even version (to do the system restore there only to)
  being bootable).

  How to create a Vista recovery disk
  http://www.Vistax64.com/tutorials/141820-create-recovery-disc.html

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

  These require the correct Vista discs since you can not start safe mode.

  Try the Startup Repair tool-

  This tells you how to access the System Recovery Options and/or with a Vista disk
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  Try recovery options Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

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

  Here are a few Google searches where many have found different solutions:

  Vista black screen - check that a 1st
  http://www.Google.com/search?hl=en&source=HP&q=Vista+black+screen&AQ=f&OQ=&AQI=G10

  Vista black screen Solution
  http://www.Google.com/search?hl=en&q=Vista+black+screen+solution&AQ=f&OQ=&AQI

  Vista black screen Fix
  http://www.Google.com/search?hl=en&q=Vista+black+screen+fix&AQ=f&OQ=&AQI

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

  If necessary and you can access all ordinary Windows.

  You can try an In-Place Upgrade (hopefully save programs and data) or a repair installation (if all goes well
  saves the data, and you need to reinstall the programs). Be sure to do a good backup or three.

  You can use another DVD that are not protected but you will need to copy you have the product key.

  On-site upgrade
  http://vistasupport.MVPs.org/repair_a_vista_installation_using_the_upgrade_option_of_the_vista_dvd.htm

  If nothing works, you can make a repair facility that must save the data but you will need to
  Reinstall the programs. This also requires correct Vista disks especially for OEM versions. You will be
  need to know your product Code.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  How to perform a repair for Vista Installation
  http://www.Vistax64.com/tutorials/88236-repair-install-Vista.html

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

  Another method that works sometimes: at the command prompt, type of Vista startup disk:
  (type in a single line or copy / paste a line at a time and then press enter - type no parenthesis)
  or "BOLD")

  c:

  cd\

  CD c:\Windows\System32\winevt (there is a space between cd and C :)
  
  Ren LogsOLD Logs (there are spaces between ren and newspapers and Logsold)

  RESTART Windows

  I hope this helps.

  I hope this helps.
  Rob - bicycle - Mark Twain said it is good.

• A black band appears just below the bookmarks toolbar immediately after the uninstall of a program called 'Picexa '.

  A black band appears just below the bookmarks toolbar immediately after the uninstall of a program called 'Picexa '.
  Please, what is your solution?

  Start Firefox in Safe Mode to check if one of the extensions (Firefox/tools > Modules > Extensions) or if hardware acceleration is the cause of the problem.

  • Put yourself in the DEFAULT theme: Firefox/tools > Modules > appearance
  • Do NOT click on the reset button on the startup window Mode safe
  • https://support.Mozilla.org/KB/safe+mode
  • https://support.Mozilla.org/KB/troubleshooting+extensions+and+themes

  You can use one of them to set toolbars to display.

  • Firefox '3-bar' menu button > customize > show/hide toolbars
  • View > toolbars
    Press the ALT key, or press F10 to display the Menu bar
  • Right click on empty toolbar space

• Re: satellite A300 screen turns off after the toshiba logo, will not boot from the CD/DVD

  Hello, I have this problem with Toshiba satellite A300.

  I deleted several files and folders of my drives C and E. To restart the computer, it only shows the Toshiba logo then a slightly gray white screen on a thorough inspection. Whenever I press CRL + ALT + DELETE, the computer restarts and behaves in the same way.

  I tried to use an external monitor, but there is no difference. The tent to start using a CD/DVD, same behaviour occurs, it does not start and screen remains blank after the Toshiba logo, I tried even to change g the order of boot, but in vain.

  What could happen?
  Thanks in advance.

  Hello

  It seems that you deleted system files and Windows no longer starts. Have you tried to restore the disk image factory settings or hard drive recovery? Or do copy the Windows installation... It is easier to reinstall rather fix the problem.

• 7.0.0.102 crashes immediately after the connection

  After update to Skype 7, it crashes immediately after the connection.

  I don't have facerig or FFsplit or any webcams. Update of Windows Firewall is disabled.

  The event logs show this:

  Name of the failing application: Skype.exe, version: 7.0.0.102, time stamp: 0x54897add
  Name of the failed module: Skype.exe, version: 7.0.0.102, time stamp: 0x54897add
  Exception code: 0xc0000005
  Offset: 0x00d527d7
  ID of the process failed: 0x1e7c
  Start time of application vulnerabilities: 0x01d029890c579caf
  The failing application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
  Path of the failing module: C:\Program Files (x86)\Skype\Phone\Skype.exe
  Report ID: 58eb96c6-957c-11e4-aae2-00224d806fdf

  Any ideas that I can do to make it work again?

  I don't know, but maybe it's one of several cases in the latest version of Skype 7.0 is not able properly to interpret data from the BIOS. At least, that was the issue with the cases already reported with this error message:

  Exception code: 0xc0000005

  Offset: 0x00d527d7

  A fix may be available in one of the next versions of Skype. In the meantime, the solution is to uninstall version 7.0 and install the 6.21.0.104 previous version.

  http://download.Skype.com/MSI/SkypeSetup_6.21.0.104.msi

• What can I do to correct a startup problem that has begun to occur immediately after the installation of windows updates today? I was about to save some work but ran the updates before hand

  I have just to complete installation of updates on my compaq presario sr2037x... and when it restarted it goes to the ' start windows normally, safe mode, safe mode w/network, w/command prompt safemode and the last known good configuration "screen... I tried to start windows normally, then the last known good configuration and not matter what I do it looks like its about to start up, then a brief blue screen flashes then I finish immediately at the start screen mode to choose.

  BSoD on my xp. Thank you microsoft. No problem until your update. You are the people going to do about it? Does not load in any case, in any case.

  STOP: 0X000000E3 (0X80558BE0, 0X81B4B020, 0X00000000, 0X00000002)

  Found this by searching. don't know if it will work again. This update might be the problem. KB971486

  Link here.  http://www.stateofthetech.com/?p=117

  Read on to find some easier ways to fix. Now, I must go and get a record of Microsofts problem!

• Screen goes black after the log on screen and works fine in safe mode.

  Original title: black screen.

  dv65 Pavilion my laptop starts up, but the screen goes black after the log on screen, judging by its instllation it works, but not the screen. It works very well in SafeMode so. Laptop is 3-4 years. I tried to connect it to my TV but she copy behavior laptop screen. Because of this problem, I had to return to the State of the plant 3 times this month. Plese help!

  Hi Avint,

  Glad to know that you were able to resolve the issue and thank you for sharing information.