la ce ajuta chestia aia? ca mie mi se pare culmea inutilitatii...

E utilă chestia cu dezactivarea touch-ului atunci când ai mouse pe usb.

si c ce incurca touch activat?

Când lucrezi ceva și folosești tastatura intens, se întâmplă să atingi cu mâna touch-ului și îți ”sare” cursorul.

Aprob!

Solutie dezactivare touch: http://www.henkel.ro/cps/rde/xchg/SID-0AC8...tUID=0000012008

Sau disable din device manager.

De vreo doua zile mi se restarteaza calculatorul din 5 in 5 minute si-mi da urmatorul mesaj la repornire:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1048

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80029D08F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:

http://rapidshare.com/files/446583433/020711-30609-01.dmp

Poate descifra careva cauza?
Merci!

cum sa citesti un fisier .dmp http://www.windowsbbs.com/general-discussi...structions.html

Folosesc Autocad si cand ating touchpad-ul imi sare cursorul si e cam deranjant... de aia mie nu mi se pare o chestie inutila sa il dezactivezi (touchpad-ul). Fiecare cu chichitele si cu obisnuintele lui... parerea mea
Multumesc pentru cei care au oferit solutii utile.

This post has been edited by Ionut-P: 7 Feb 2011, 12:39

Multumesc, am reusit sa creez debuglog, insa tot nu pricep mare lucru:

Opened log file 'c:debuglog.txt'

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\020711-30609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Mon Feb 7 00:52:26.218 2011 (UTC + 2:00)
System Uptime: 0 days 0:00:10.984
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029d08f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80029d08f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02f626f0 fffff800`02d07a89 : fffffa80`029d08d0 fffffa80`018fab60 00000000`000007ff 00000000`00000030 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f62c10 fffff800`02be9667 : fffffa80`029d08d0 fffff800`02c625f8 fffffa80`018fab60 fffff8a0`001ac240 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f62c40 fffff800`02b51c45 : fffff800`02cc4360 fffff800`02c6a580 00000000`00000000 fffffa80`018fab60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f62c80 fffff800`02aca961 : fffff800`02f14e40 fffff800`02b51c20 fffffa80`018fab60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f62cb0 fffff800`02d61c06 : 74ff5000`0000a081 fffffa80`018fab60 00000000`00000080 fffffa80`018e4b30 : nt!ExpWorkerThread+0x111
fffff880`02f62d40 fffff800`02a9bc26 : fffff800`02c37e80 fffffa80`018fab60 fffffa80`018fa040 c1e80424`748d5608 : nt!PspSystemThreadStartup+0x5a
fffff880`02f62d80 00000000`00000000 : fffff880`02f63000 fffff880`02f5d000 fffff880`02f629f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

rax=fffffa8002a9f000 rbx=fffffa80029d08f8 rcx=fffff88002f62730
rdx=fffffa800180c000 rsi=0000000000000000 rdi=fffffa8002a9f000
rip=fffff80002ef287c rsp=fffff88002f626f0 rbp=0000000000000001
r8=000000000000f1e0 r9=000000000000060c r10=00000000000007ff
r11=000000000000060c r12=fffff80002cc43c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`02ef287c 48897c2438 mov qword ptr [rsp+38h],rdi ss:0018:fffff880`02f62728=fffffa8000000910
Child-SP RetAddr : Args to Child : Call Site
fffff880`02f626f0 fffff800`02d07a89 : fffffa80`029d08d0 fffffa80`018fab60 00000000`000007ff 00000000`00000030 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f62c10 fffff800`02be9667 : fffffa80`029d08d0 fffff800`02c625f8 fffffa80`018fab60 fffff8a0`001ac240 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f62c40 fffff800`02b51c45 : fffff800`02cc4360 fffff800`02c6a580 00000000`00000000 fffffa80`018fab60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f62c80 fffff800`02aca961 : fffff800`02f14e40 fffff800`02b51c20 fffffa80`018fab60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f62cb0 fffff800`02d61c06 : 74ff5000`0000a081 fffffa80`018fab60 00000000`00000080 fffffa80`018e4b30 : nt!ExpWorkerThread+0x111
fffff880`02f62d40 fffff800`02a9bc26 : fffff800`02c37e80 fffffa80`018fab60 fffffa80`018fa040 c1e80424`748d5608 : nt!PspSystemThreadStartup+0x5a
fffff880`02f62d80 00000000`00000000 : fffff880`02f63000 fffff880`02f5d000 fffff880`02f629f0 00000000`00000000 : nt!KxStartSystemThread+0x16
start end module name
fffff800`00b98000 fffff800`00ba2000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB)
fffff800`02a04000 fffff800`02a4d000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08)
fffff800`02a4d000 fffff800`03029000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9)
fffff880`00c00000 fffff880`00cc0000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D)
fffff880`00cc0000 fffff880`00ccf000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00cd1000 fffff880`00cde000 mcupdate mcupdate.dll Tue Jul 14 04:29:09 2009 (4A5BDF65)
fffff880`00cde000 fffff880`00cf2000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027)
fffff880`00cf2000 fffff880`00d50000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00d50000 fffff880`00df4000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
fffff880`00e00000 fffff880`00e0b000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB)
fffff880`00e0b000 fffff880`00e57000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F)
fffff880`00e6a000 fffff880`00ec1000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106)
fffff880`00ec1000 fffff880`00eca000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00eca000 fffff880`00ed4000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
fffff880`00ed4000 fffff880`00f07000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00f07000 fffff880`00f14000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
fffff880`00f14000 fffff880`00f29000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`00f29000 fffff880`00f3e000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00f3e000 fffff880`00f9a000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141)
fffff880`00f9a000 fffff880`00fa1000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115)
fffff880`00fa1000 fffff880`00fb1000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114)
fffff880`00fb1000 fffff880`00fcb000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00fcb000 fffff880`00fd4000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`00fd4000 fffff880`00ffe000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118)
fffff880`0101c000 fffff880`01030000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
fffff880`01030000 fffff880`011d3000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F)
fffff880`01234000 fffff880`01292000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C)
fffff880`01292000 fffff880`012ac000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156)
fffff880`012ac000 fffff880`0131f000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814)
fffff880`0131f000 fffff880`01330000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF)
fffff880`01330000 fffff880`0133a000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111)
fffff880`0133a000 fffff880`01386000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128)
fffff880`01386000 fffff880`013c0000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A)
fffff880`013c0000 fffff880`013e1000 nv_agp nv_agp.sys Tue Jul 14 02:38:44 2009 (4A5BC584)
fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A)
fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4)
fffff880`0148b000 fffff880`014d5000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164)
fffff880`014d5000 fffff880`014e5000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E)
fffff880`014e5000 fffff880`014ed000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB)
fffff880`014ef000 fffff880`015e1000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184)
fffff880`015e1000 fffff880`015f3000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201)
fffff880`015f3000 fffff880`015fc000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA)
fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458)
fffff880`018e8000 fffff880`01922000 fvevol fvevol.sys Tue Jul 14 02:22:15 2009 (4A5BC1A7)
fffff880`01922000 fffff880`01938000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`01938000 fffff880`01968000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`01968000 fffff880`01976000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
fffff880`01976000 fffff880`01982000 dump_ataport dump_ataport.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`01982000 fffff880`0198b000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`0198b000 fffff880`0199e000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
Mini Kernel Dump does not contain unloaded driver list
Closing open log file c:debuglog.txt

Arde pe un CD un Hirens Boot si baga un Memtest.

O sa incerc diseara, merci!

Sper ca nu ai praf in sloturile memoriilor.

Baga si-un Praftest.

http://www.sevenforums.com/crash-lockup-de...s-what-try.html

Io pentru inceput as verifica tensiunile in sursa.

Se da un router wireless D-Link DI-524 si 2 laptopuri.Pana acum o saptamana toate mergeau normal.A fost rupta o fibra in zona si dupa aceea au venit baietii de la net(Aitel) si au configurat din nou wireless-ul dar nu mai merge decat la un laptop...al 2-lea nu se mai conecteaza nici mort.Am incercat tot felul de setari dar nimic. Ce dreaq sa aiba?

pai in setari.ori au activat baietii destepti filtrare pe mac si nu ai scris bine mac-ul ?

si atunci de ce se conecteaza oricare din ele iar celalalt ramane pe afara?

l@u - posibil sa fie mai multe probleme.
Ai static IP sau DHCP? E posibil sa fie pus un 'range' de un singur IP la dhcp.
Tu nu stii sa il configurezi?
Pune cateva screenshoturi cu ce ai configurat pe router, poate reusim sa te ajutam.
P.S. - daca il conectezi pe al doilea pe cablu merge?

dane adresa de remote sil facem

Salut, am o intrebare , cine stie cum se schimba rezolutia unui joc fara sa intri in el, pur si simplu porneste cu o rezolutie pe care monitorul meu nu o poate reda, am incercat cu run in 640x480 doar ca sa pot intra in el si sa modific, dar nu are efect. placa video e un hd radeon pro 2600, pe 128 biti si 512mb vram, nu e ea prea puternica, dar se tine la jocuri.

cauti pe unde ai jocul un fisier in care el tine setarile.
de obicei se numeste config.cfg. il deschizi cu notepad si cauti rezolutia, rata de refresh si le schimbi manual. salvezi si ar trebui sa mearga.
despre ce joc e vorba, sau ce monitor folosesti?

la naiba da

This post has been edited by C@talin: 9 Feb 2011, 11:48

@ Andy_ACS Este IP static si l-am configurat de 2 ori in 3 ani si a mers dar acum parca l-au luat dracii caci nu vrea sa mai mearga deloc.Imi vine sa dau cu el de pamant si sa cumpar altul.Ii bag toate setarile asa cum le am in laptop(ip,gateway,subnet mask etc)dar degeaba ,al doilea laptop se conecteaza la router prin wireless dar spune ca nu este conectat routerul la net.

Problema e ca am cautat, si nu am gasit fisierul, am mai modificat asa rezolutia la alt joc, dar asta din vina mea, mai caut odata poate acum al vad. Jocu e metro2033 iar monitorul e un crt de 17 la 60hertz si 1280 cu 1024.

Fa update la ultimul driver (altul decat 197.13!)

apoi:


http://www.gamebrood.com/2010/03/18/metro-...-fix-and-fixes/
http://www.unigamesity.com/how-to-fix-metr...screen-crashes/

sau cauta sa modifici direct rezolutia acolo, cauta liniile
r_res_hor
r_res_vert
e posibil sa nu stie de rezolutii mici, incearca direct cu maximum suportat de monitor.
vezi si refresh rate.

This post has been edited by kxz: 9 Feb 2011, 12:25

ok, ms mult.

chiar daca rezolvi problema rezolutiei nu stiu cum o sa iti ruleze jocul. Are niste cerinte foarte mari. De exemplu pentru a rula la calitate maxima are nevoie de doua gforce gtx460 legate in SLI si tot nu scoate mai mult de 35-40 de cadre pe secunda

Nici nu vreau cine stie ce performante, sau grafica la maxim, doar sa.l pot juca, am inteles ca e destul de interesant si sunt curios sa vad cum e in realitate. Procesorul si rami duc sigur, placa video sa vad daca rezista, daca nu intotdeauna exista overclocking, sau mai simplu alta placa ( da asta mai asteapta).

Pai care e intreaga configuratie? Ca daca vrei sa-l joci frame cu frame mai bine il lasi asa. Eu nu eram multumit cum mergea pe un 9800GTX, cu un procesor Pentium G6950, ce-i drept pe 1680x1050, dar oricum jocul asta e cam cel mai pretentios din cate stiu eu.