Page 1 of 1

BSOD on Win 10

Posted: 20 Dec 2015, 21:54
by combat2k
Salut,

pe noul N170 am tot intampinat cateva freeze-uri (+restart) cu eroarea DRIVER_POWER_STATE_FAILURE. Prima solutie e safe mode, Device Manager, identificare device cu semnul exclamarii (PnP monitor-ul), uninstall + restart. Problema inca persista...

Am pus si 359.12-le recomandat de myx, am crezut ca e ceva legat de jocuri, prima data mi-a dat cand am facut alt+tab + click pe joc pt fullscreen. Dar mi-a dat si cand eram doar in Windows (Chrome + uTorrent gen...)...

idei? Cum sa o apuc pt investigatie?

Merci,

Re: BSOD on Win 10

Posted: 20 Dec 2015, 22:10
by oGu
Salut,

pe noul N170 am tot intampinat cateva freeze-uri (+restart) cu eroarea DRIVER_POWER_STATE_FAILURE. Prima solutie e safe mode, Device Manager, identificare device cu semnul exclamarii (PnP monitor-ul), uninstall + restart. Problema inca persista...

Am pus si 359.12-le recomandat de myx, am crezut ca e ceva legat de jocuri, prima data mi-a dat cand am facut alt+tab + click pe joc pt fullscreen. Dar mi-a dat si cand eram doar in Windows (Chrome + uTorrent gen...)...

idei? Cum sa o apuc pt investigatie?

Merci,
E windows-ul care era instalat pe el?

Re: BSOD on Win 10

Posted: 20 Dec 2015, 22:41
by combat2k
Win 10 clean install.

No serial yet, ma gandesc sa cumpar unu de pe net...

Driverele venite pe DVD, restu downloadat de la Clevo, + nVidia latest. .12-le lu myx.

Re: BSOD on Win 10

Posted: 20 Dec 2015, 22:54
by myx
Incearca un cleanup cu DDU si dupa pune 359.06.

Eu am scos 359.12 azi ca am observat ca imi dadea rate-ur Gsync-ul.

Re: BSOD on Win 10

Posted: 23 Dec 2015, 07:54
by mrmrm
Si eu patesc asta, de la intel hd graphics drivers.Nu am gasit inca solutie... niciodata nu se intampla in jocuri...mereu in alt tabbing sau la schimbarea ferestrelor. N150 , driveri de pe site, win10 genuine.

Re: BSOD on Win 10

Posted: 24 Dec 2015, 08:38
by combat2k
Asta e si presupunerea mea, dar am ajuns sa fac debugging pe dump-urile Windows-ului. Astept urmatorul dump, deocamdata nu am gasit ceva relevant in dump legat de Intel sau NVidia...

Re: BSOD on Win 10

Posted: 24 Dec 2015, 09:45
by oGu
Asta e si presupunerea mea, dar am ajuns sa fac debugging pe dump-urile Windows-ului. Astept urmatorul dump, deocamdata nu am gasit ceva relevant in dump legat de Intel sau NVidia...
Cred ca astea sunt probleme aparute din cauza windows 10 si driverii de la nVidia. Daca da-ti un search pe google la "DRIVER_POWER_STATE_FAILURE" o sa vedeti multe topicuri cu diferite explicatii dar in special cea cu driverii de la nVidia.

Mai sunt solutii care spun sa dezactivati optiunile de "windows can turn off this device" de la hub-urile USB si de la bluetooth si Wi-Fi.

Re: BSOD on Win 10

Posted: 24 Dec 2015, 09:45
by myx
Nvidia a scos drivere noi,poți încerca și cu alea.

Sent from my Nexus 5 using Tapatalk

Re: BSOD on Win 10

Posted: 24 Dec 2015, 11:45
by combat2k
Asta e si presupunerea mea, dar am ajuns sa fac debugging pe dump-urile Windows-ului. Astept urmatorul dump, deocamdata nu am gasit ceva relevant in dump legat de Intel sau NVidia...
Cred ca astea sunt probleme aparute din cauza windows 10 si driverii de la nVidia. Daca da-ti un search pe google la "DRIVER_POWER_STATE_FAILURE" o sa vedeti multe topicuri cu diferite explicatii dar in special cea cu driverii de la nVidia.

Mai sunt solutii care spun sa dezactivati optiunile de "windows can turn off this device" de la hub-urile USB si de la bluetooth si Wi-Fi.
Am vazut, oGu, d-asta nu m-am panicat :-) d-asta si ziceam ca prefer Windows 7, dar pana la urma s-or rezolva problemele.. din pacate n-am avut timp de review, d-abia am avut timp sa ma Fallout 4 nitel ...

Nu am mai primit BSOD-uri de vreo 2 zile cu ultimul driver, dar cine stie, va anunt cand mai primesc ... o sa incerc si chestia cu dezactivat power saving-ul pe alte device-ui.. o sa vad..

Re: BSOD on Win 10

Posted: 24 Dec 2015, 20:21
by combat2k
one more BSOD.

Playing PES 2016, Alt+Tab, worked couple of times, then freezing, 20-30 seconds, BSOD + DRIVER_POWER_STATE_FAILURE.

Latest drivers nvidia (geforce.com) + intel (clevo). Windows 10 without key and activation... :-) yet :-)

minidumpul analizat arata cam asa:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe000cc1cf6c0, fffff8011fa73890, ffffe000d0bce010}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000cc1cf6c0, Physical Device Object of the stack
Arg3: fffff8011fa73890, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000d0bce010, The blocked IRP

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffe000cc1fad60

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d60a

MODULE_NAME: pci

FAULTING_MODULE: fffff800bda10000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFF8011FA7BFB0

STACK_TEXT:
fffff801`1fa73858 fffff801`1d9e761e : 00000000`0000009f 00000000`00000003 ffffe000`cc1cf6c0 fffff801`1fa73890 : nt!KeBugCheckEx
fffff801`1fa73860 fffff801`1d9e753e : ffffe000`d19b5e90 ffffe000`ca1a4298 00000000`00000000 fffff801`1d8af746 : nt!PopIrpWatchdogBugcheck+0xde
fffff801`1fa738c0 fffff801`1d84fa16 : ffffe000`d19b5ec8 fffff801`1fa73a10 00000000`00000001 00000000`005fd39e : nt!PopIrpWatchdog+0x32
fffff801`1fa73910 fffff801`1d94b51a : 00000000`00000000 fffff801`1db23180 fffff801`1db99740 ffffe000`d4154080 : nt!KiRetireDpcList+0x5f6
fffff801`1fa73b60 00000000`00000000 : fffff801`1fa74000 fffff801`1fa6d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.10586.0

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_image_pci.sys

FAILURE_ID_HASH: {a89ab2d1-2459-89ee-9990-558bbc68ffab}

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

Nu ma prind exact care e problema, dar o sa mai intreb prin alte forumuri si va tin la curent. Pana una alta, mai usor cu alt+tab-ul din jocuri :D

Re: BSOD on Win 10

Posted: 24 Dec 2015, 21:20
by myx
Pune pe pastebin ce vine si dupa followup: machine owner ala...ultimul rand postat aici.

Re: BSOD on Win 10

Posted: 25 Dec 2015, 03:12
by combat2k
Pai nu mai vine nika.. sau o trebui sa mai dau vreo comanda de extra detalii.. ce am paste-uit aici e cu !analyze-v, altceva ce as putea sa mai dau?