Bluescreen tcpip.sys

LiNU · December 22, 2009

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Dec 22 15:35:14.718 2009 (GMT+2)
System Uptime: 1 days 20:11:39.449
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 2, 0, b647fc66}

Probably caused by : tcpip.sys ( tcpip!TCPAbortAndIndicateDisconnect+23 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b647fc66, address which referenced memory

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


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b647fc66 8b400c          mov     eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  start-S2.exe

LAST_CONTROL_TRANSFER:  from b64709e9 to b647fc66

STACK_TEXT:  
b35788f0 b64709e9 024c0f50 b3578a90 876bf3e0 tcpip!TCPAbortAndIndicateDisconnect+0x23
b3578b40 b644da55 0000000e 0000000d 804f0cf3 tcpip!TdiSetInformationEx+0x27f
b3578bec b644d07c 876bf3e0 876bf450 876bf450 tcpip!IPSGetTotalCounts+0x24
b3578c08 b644d034 876bf3e0 876bf450 875eff78 tcpip!ARPQueryInfo+0x78
b3578cd4 00000000 8882c418 882bed50 b3578d48 tcpip!ARPQueryInfo+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b647fc66 8b400c          mov     eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!TCPAbortAndIndicateDisconnect+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44477c19

FAILURE_BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

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

1: kd> lmvm tcpip
start    end        module name
b6447000 b649f080   tcpip    M (pdb symbols)          c:\windows\symbols\sys\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Image path: tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Thu Apr 20 15:18:33 2006 (44477C19)
    CheckSum:         0005ED86
    ImageSize:        00058080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Unul proaspat si de la mine :beer:

Dragos, parere ?

JustAnotherPlayer · December 22, 2009

Ma pe seven nu se iau BSOD-uri...cel putin eu am avut pt ceva timp si n-am luat nici unu.

Uite solutia:))

LiNU · December 22, 2009

Ma pe seven nu se iau BSOD-uri...cel putin eu am avut pt ceva timp si n-am luat nici unu.
Uite solutia:))

1. Si cu licenta cum fac ?

2. Imi garantezi ca PC`u se va misca la fel ca pe XP ?

3. Pe Vista/7 vezi si tu ca apar altfel de probleme...

:beer:

JustAnotherPlayer · December 24, 2009

Bagi Seven pt Mu si tii XP-u.

Tu te referi la licenta pt seven?

7 are mult mai putine probleme decat vista,iar daca ai un GB ram si bagi home premium,iti merge super

LiNU · December 24, 2009

Bagi Seven pt Mu si tii XP-u.
Tu te referi la licenta pt seven?
7 are mult mai putine probleme decat vista,iar daca ai un GB ram si bagi home premium,iti merge super

Sa inteleg ca Windows 7 este gratuit :crazy: pai in cazul asta trimite-mi si mie DVD`u cu 2 licente.

Aaa... si ca nu uit, vezi si ce nistre drivere pentru laptop Acer Extensa 5630G (vezi ca pentru laptop imi trebe pe 64 biti sa imi recunoasca toti ce`i 4 G rami).

Hai Mos Cracinule... :beer:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Dec 24 11:32:40.890 2009 (GMT+2)
System Uptime: 1 days 1:58:59.637
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.............................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 2, 0, b64adc66}

Probably caused by : tcpip.sys ( tcpip!TCPAbortAndIndicateDisconnect+23 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b64adc66, address which referenced memory

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


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b64adc66 8b400c          mov     eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  start-S2.exe

LAST_CONTROL_TRANSFER:  from b649e9e9 to b64adc66

STACK_TEXT:  
b54798f0 b649e9e9 025a44d8 b5479a90 8a01ca10 tcpip!TCPAbortAndIndicateDisconnect+0x23
b5479b40 b647ba55 0000000e 00000014 804f0cf3 tcpip!TdiSetInformationEx+0x27f
b5479bec b647b07c 8a01ca10 8a01ca80 8a01ca80 tcpip!IPSGetTotalCounts+0x24
b5479c08 b647b034 8a01ca10 8a01ca80 87bc6230 tcpip!ARPQueryInfo+0x78
b5479cd4 00000000 8a1b8780 8a2d0550 b5479d48 tcpip!ARPQueryInfo+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b64adc66 8b400c          mov     eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!TCPAbortAndIndicateDisconnect+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44477c19

FAILURE_BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

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

1: kd> lmvm tcpip
start    end        module name
b6475000 b64cd080   tcpip    M (pdb symbols)          c:\windows\symbols\sys\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Image path: tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Thu Apr 20 15:18:33 2006 (44477C19)
    CheckSum:         0005ED86
    ImageSize:        00058080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Asta e cado de craciun :dance:

JustAnotherPlayer · December 24, 2009

Lasa ca 7 merge prea bine si fara licenta:))eu am ultimate-u

si daca vreu sa te joci fara BSOD renunta si tu la 846 de ram,si bagi seven pe 32bits si stai cu 3.25,oricum iti ajung

Si nu cred ca rulezi pe laptop o aplicatie care sa aibe nevoie de mai mult de 3.25 gb ram,si nici gaming pt ca are Radeon HD3470...care...deh'.

Eu am un Aspire 6530G si cu 3.25 zbarnaie...

LiNU · December 24, 2009

Lasa ca 7 merge prea bine si fara licenta:))eu am ultimate-u
si daca vreu sa te joci fara BSOD renunta si tu la 846 de ram,si bagi seven pe 32bits si stai cu 3.25,oricum iti ajung
Si nu cred ca rulezi pe laptop o aplicatie care sa aibe nevoie de mai mult de 3.25 gb ram,si nici gaming pt ca are Radeon HD3470...care...deh'.
Eu am un Aspire 6530G si cu 3.25 zbarnaie...

Sunt obligat sa pastrez Win cu licenta.

Iti recomand sa citesti intregul topic si dupaia sa mai postezi.

Scap de BOSD isi dau de alte erori pe Win7/Vista. Am incercat

AngelDust · December 24, 2009

Eu vreau sa-mi mearga pe XP.Sunt batut in cap si nu vreau sa inteleg beneficiile Win 7 sau sa le vad .Vad ca se tot posteaza de ceva timp , dar nimic concret.Se poate rezolva problema pe XP sau nu?Isi mai bate careva capul cu ea?Daca nu macar raman cu parerea romaneasca "las-o bah ca merge asa " si aia e.

JustAnotherPlayer · December 25, 2009

Bine,hai sa va iau altfel.

Din cate am vazut pana acuma,cel putin la mine,problema nu este numai din start.exe sau Windows XP

Este si din cauza netului.

Am avut net prin LAN,de la o retea de cartier,si cu XP Sp2 clean,luam BSOD in prostie.

Acum am net prin Modem USB de la clicknet,si iau BSOD mult mai rar,cu aceasi vers de windows.

Cu net mobil de la vodafone+N73 cu optiunea 500MB live,nu iau BSOD NICIODATA (tot cu aceasi versiune de windows)

Cu o versiune de XP luata de pe extern,numita ADA XP Blue,cu netul prin USB de la clicknet,am scapat de tot de BSOD.(Inainte,cu modemu si cu SP2 clean,luam foarte rar,odata la 1 zi)

Se pare ca a plecat de tot:)

Revenim la chestia cu netul prin LAN

Placile de baza mai vechi nu iau BSOD,cu placa de retea integrata...de ce nu stiu

Am un PC deala vechi,luat de la Altex acu 6-7 ani...si n-a luat in viata lui BSOD,cu netu de la reteaua de cartier...iar pe celalalt PC,al meu,ata' nou,luam cam la o ora,o ora si.

Cineva a zis ca si-a luat o placa de retea mai de doamne ajuta,nu deaia la 15 ron,si a scapat de problema.

Da acuma astia cu laptop ce fac?

tranced · December 25, 2009

am placa de retea SMC si tot iau un bsod la doua saptamani sa zic

JustAnotherPlayer · December 25, 2009

Cat n-ar da LiNU sa ia si el odata la 2 saptamani:))

LiNU · December 25, 2009

Am incercat cu placa de retea si noua si veche. Am luat o placa de retea chiar de pe vremea cand a inceput sa apana PCI. Am incerca cu aceasi versiune de Win pe 3 calculatoare, pe 2 luam BOSD si pe unul nu luam. Configuratii asemanatoare. Cu netu am incercat cu Stik de la Orange, Cliknet, RDS.

Ieri am luat 2 BOSD de dimineatza si m-am enervat si am reinstalat win, celalalt avea vreo 4 luni.

Biggles · December 26, 2009

Cat n-ar da LiNU sa ia si el odata la 2 saptamani:))

si eu la fel....

Mai mult de 12-14-maxim 16 ore nu pot sta in joc ca iau BSOD. :comp1:

Biggles · December 27, 2009

bunny ija sau oricare alt admin care are access la loguri...

am luat iar BSOD. puteti sa verificati in loguri cam la ce ora exact am luat??? in jurul orei 2 si ceva noaptea,

imi puteti spune cu exactitate si minutul cand ati pierdut legatura cu charul Bulaneitor?

PS: incerc o solutie la BSOD, si vreau sa vad daca functioneaza.

bunny · December 28, 2009

Nu am acces la loguri, imi pare rau, pm vdragosh, Lancelot, ija sau Odyzzeus.

Biggles · December 29, 2009

PS: incerc o solutie la BSOD, si vreau sa vad daca functioneaza.

uptime 1 day 2 h & 36 min

Mai asteptam. pana acum totul merge normal.

tranced · January 4, 2010

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini010410-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Jan 4 18:46:42.661 2010 (GMT+2)
System Uptime: 6 days 1:58:06.112
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
......................................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {c, 2, 0, ab6ccfa9}
Probably caused by : tcpip.sys ( tcpip!ReadNextTCB+152 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ab6ccfa9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000c
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!ReadNextTCB+152
ab6ccfa9 8b400c mov eax,dword ptr [eax+0Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: start-S2.exe
LAST_CONTROL_TRANSFER: from ab6bdb5e to ab6ccfa9
STACK_TEXT:
a6d148f0 ab6bdb5e 02548338 a6d14a90 8845f988 tcpip!ReadNextTCB+0x152
a6d14b24 00000000 897da7e0 c0300000 001fc000 tcpip!TdiQueryInformationEx+0x865
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!ReadNextTCB+152
ab6ccfa9 8b400c mov eax,dword ptr [eax+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tcpip!ReadNextTCB+152
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 485b99ad
FAILURE_BUCKET_ID: 0xD1_tcpip!ReadNextTCB+152
BUCKET_ID: 0xD1_tcpip!ReadNextTCB+152
Followup: MachineOwner
---------
1: kd> lmvm tcpip
start end module name
ab694000 ab6ec480 tcpip M (pdb symbols) c:\windows\symbols\sys\tcpip.pdb
Loaded symbol image file: tcpip.sys
Image path: tcpip.sys
Image name: tcpip.sys
Timestamp: Fri Jun 20 14:51:09 2008 (485B99AD)
CheckSum: 0005ED6B
ImageSize: 00058480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

inca unul

tranced · January 8, 2010

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini010810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Fri Jan 8 19:03:10.062 2010 (GMT+2)
System Uptime: 1 days 20:33:00.787
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
.......................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {c, 2, 0, ab6ccfa9}
Probably caused by : tcpip.sys ( tcpip!ReadNextTCB+152 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ab6ccfa9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000c
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!ReadNextTCB+152
ab6ccfa9 8b400c mov eax,dword ptr [eax+0Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: start-S2.exe
LAST_CONTROL_TRANSFER: from ab6bdb5e to ab6ccfa9
STACK_TEXT:
aa4d58f0 ab6bdb5e 027fa550 aa4d5a90 89795640 tcpip!ReadNextTCB+0x152
aa4d5b24 00000000 897bb3c0 c0300000 00228000 tcpip!TdiQueryInformationEx+0x865
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!ReadNextTCB+152
ab6ccfa9 8b400c mov eax,dword ptr [eax+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tcpip!ReadNextTCB+152
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 485b99ad
FAILURE_BUCKET_ID: 0xD1_tcpip!ReadNextTCB+152
BUCKET_ID: 0xD1_tcpip!ReadNextTCB+152
Followup: MachineOwner
---------
1: kd> lmvm tcpip
start end module name
ab694000 ab6ec480 tcpip M (pdb symbols) c:\windows\symbols\sys\tcpip.pdb
Loaded symbol image file: tcpip.sys
Image path: tcpip.sys
Image name: tcpip.sys
Timestamp: Fri Jun 20 14:51:09 2008 (485B99AD)
CheckSum: 0005ED6B
ImageSize: 00058480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

January 20, 2010

de luni de zile nu am avut aceasta problea..de astazi am si eu aceasta problema ..am bagat updateu sa vedem acuma .. daca merge

la fel si dupa instalarea patchului =((

LiNU · January 20, 2010

Bun venit in club :P eu unul m-am plictisit sa mai postez minidump`urile.

Se pare ca nu e nici o rezolvare... momentan.

January 20, 2010

tx linu

culmea ..acuma am bagat alt update si numai apare bluescreen da se blocheaza dupa 1 minut

:tiphat:

January 21, 2010

gata baieti imi merge..

l`am curatat bine de praf ca nu`l mai curatasem de mult(mai ales la cooler era dezastru #-o )

am reinstalat windowsu si e totul bine pana acum:)

Biggles · January 23, 2010

gata baieti imi merge..
l`am curatat bine de praf ca nu`l mai curatasem de mult(mai ales la cooler era dezastru #-o )
am reinstalat windowsu si e totul bine pana acum:)

bv... :beer: asta am facut si eu... a mers bine ceva timp dupa care poc... BSOD

Bun venit in club :P eu unul m-am plictisit sa mai postez minidump`urile.
Se pare ca nu e nici o rezolvare... momentan.

Avand in vedere ca windowsu meu este unul original, leam trimis un mail celor de la Microsoft in legatura cu aceasta problema (le-am atasat si minidumpu)... miau raspuns cam dupa vreo 2 sapt... nu mai stiu exact ce zicea in mail... daca vreti caut si vil postez... dar 2 lucruri leam inteles clar din raspunsul lor.

1. da... stim despre aceasta problema, sunt mai multi care se confrunta cu aceasta

si

2. din pacate nu am gasit o solutie la problema dumneavoastra, inca se lucreaza la remedierea problemei si ca ma vor cantacta imediat ce vom gasi rezolvarea.

cam atata...

vdragosh · January 23, 2010

bv... :beer: asta am facut si eu... a mers bine ceva timp dupa care poc... BSOD
Avand in vedere ca windowsu meu este unul original, leam trimis un mail celor de la Microsoft in legatura cu aceasta problema (le-am atasat si minidumpu)... miau raspuns cam dupa vreo 2 sapt... nu mai stiu exact ce zicea in mail... daca vreti caut si vil postez... dar 2 lucruri leam inteles clar din raspunsul lor.
1. da... stim despre aceasta problema, sunt mai multi care se confrunta cu aceasta
si
2. din pacate nu am gasit o solutie la problema dumneavoastra, inca se lucreaza la remedierea problemei si ca ma vor cantacta imediat ce vom gasi rezolvarea.
cam atata...

daca o echipa de cateva sute de programatori ( daca nu mii ) nu sunt in stare sa gaseasca o solutie ,

cam in cat timp o sa gasesc eu raspunsul la aceasta problema cand ma ocup de MU doar in putinul timp disponibil care il am ( + ca la mine nu se manifesta in nici un fel ) ?

am sperat sa gasim ceva in comun la cei la care apare BSOD ( am auzit ca sunt unii care au 2-3 PC-uri acasa si BSOD-ul nu apare pe toate ... )

Biggles · January 24, 2010

daca o echipa de cateva sute de programatori ( daca nu mii ) nu sunt in stare sa gaseasca o solutie ,
cam in cat timp o sa gasesc eu raspunsul la aceasta problema cand ma ocup de MU doar in putinul timp disponibil care il am ( + ca la mine nu se manifesta in nici un fel ) ?
am sperat sa gasim ceva in comun la cei la care apare BSOD ( am auzit ca sunt unii care au 2-3 PC-uri acasa si BSOD-ul nu apare pe toate ... )

NU cred ca rezolvarea BSOD care este cauzat din cauza unui simplu joc reprezinta prioritatea de top a celor de la microsoft, sunt alte chestii mult mai importante de rezolvat.

cat despre partea a doua... am 3 calculatoare... doar pe 1 imi iau BSOD... si da... chiar nu mam interesat deloc ... totusi cauta pe forum si vei vedea cate incercari am avut ca sa gasim o rezolvare la aceasta problema.

Dupa cum spunea si bunny...

Ok, maine sa postezi iar, sa-mi spui daca ti-a dat eroarea. Bine ar fi sa te tina. :)
Pacat ca postezi doar tu, iar altii care se lupta cu restarturile le e lene sa dea un reply. Nu se vor rezolva problemele singure, oameni buni. >.<

din pacate cunostintele mele pana aici tin... altceva nu mai stiu sa fac ca sa gasesc solutia. o sa las Einstenii sa o gaseasca.

PS: si eu ca si tine... in putinul meu timp liber am incercat sa ii dau de capat, din pacate nu am reusit... am trimis problema la niste specialisti... vam spus raspunsul care lam primit de la ei... ce as putea sa fac mai mult de atat???

Companie	Domeniu	Politica de confidenţialitate
RCS&RDS S.A.	linkmania.ro	Vezi politica de confidenţialitate
ips4_hasJS, ips4_ipsTimezone, ips4_IPSSessionFront, ips4_member_id, ips4_pass_hash, ips4_language, ips4_anon_login, ips4_theme, ips4_forum_view, ips4_recentEmoji
Google LLC	google.com	Vezi politica de confidenţialitate
_ga, _gid, _gat, AMP_TOKEN, _gac_, __utma, __utmt, __utmb, __utmc, __utmz

Sign In

Archived

Bluescreen tcpip.sys

Recommended Posts

LiNU

JustAnotherPlayer

LiNU

JustAnotherPlayer

LiNU

JustAnotherPlayer

LiNU

AngelDust

JustAnotherPlayer

tranced

JustAnotherPlayer

LiNU

Biggles

Biggles

bunny

Biggles

tranced

tranced

Guest bLu_

LiNU

Guest bLu_

Guest bLu_

Biggles

vdragosh

Biggles

Recently Browsing 0 members

Browse

Activity