lab501 forum  

Go Back   lab501 forum > Hardware > Cutia de sub birou
Connect with Facebook

Cutia de sub birou Aici se discuta despre configuratii prezente sau viitoare


Reply
 
Thread Tools Search this Thread Display Modes
Old 07-05-2017, 13:54   #2621
BIC
Member
 
Join Date: May 2010
Posts: 90
Mentioned: 0 Post(s)

PC-ul meu

Default

Asta explică cei 140 MB/s atinși de SSD... Atunci am să pun Ón caddy Hdd-ul original (100 GB 5400 rpm) și mai caut un HDD microdrive, dacă tot am slot CompactFlash .
Mulțumesc pentru clarificări.
BIC is offline   Reply With Quote
Old 08-05-2017, 09:23   #2622
Boggy
Ancient friend
 
Boggy's Avatar
 
Join Date: Oct 2009
Posts: 8,871
Mentioned: 494 Post(s)

PC-ul meu

Default

Chiar si cu aia 150mb/s ar trebui sa simti un upgrade mare in real life, timpul de acces face o diferenta enorma.
__________________
Boggy doesn't have a computer.
Just a basement full of Asian kids that memorize numbers.
Boggy is offline   Reply With Quote
Old 21-06-2017, 14:44   #2623
agarici cu pedale
Ancient friend
 
agarici cu pedale's Avatar
 
Join Date: Mar 2012
Location: Bucuresti
Posts: 7,807
Mentioned: 48 Post(s)

PC-ul meu



Default

Care ma poti ajuta cu un mister dintr-un dump, nu reusesc sa-i dau de cap sub nici o forma, cand esti prost esti prost pana la capat.

https://1drv.ms/u/s!As_Zx7Eh7JgSo3URk_uREYpbwNYT

Am bsod cu urmatoarlee
INVALID_WORK_QUEUE_ITEM 0x00000096
Parametrii
ffffb28c`63352ce0
fffff800`c3284650
fffff800`c3284380
fffff800`c2eaad90
ntoskrnl.exe
ntoskrnl.exe+16c3f0

Chiar ma depaseste fiindca nu gasesc ceva exact.

LE: Momentan am dat jos Soundblaster SE-ul ca tind sa cred ca el e vinovatul.
Problema principala se manifesta in felul urmator, cand eram pe skype imi crapa skype-ul in conferinta doar si nu mai puteam sa-l folosesc pana nu dadeam restat pe partea de call, doar text altfel freezuia aplicatia.
Reinstall OS ca deja ma disperat fiindca nu gasisem fix.

Azi toate bune si frumoase, skype merge bine, intru intr-un joc si freeze la pc pe sunet repetitiv si apoi bsod, de 2 ori la rand la fel, ambele in combinatie cu call pe skype la activ.
Umtorul pas e sa schimb si cablul SATA la SSD.

Last edited by agarici cu pedale; 21-06-2017 at 15:06.
agarici cu pedale is offline   Reply With Quote
Old 21-06-2017, 14:54   #2624
kobro
Ancient friend
 
kobro's Avatar
 
Join Date: Oct 2010
Posts: 1,059
Mentioned: 41 Post(s)

PC-ul meu

Default

bluescreenview ce zice?
kobro is offline   Reply With Quote
Old 21-06-2017, 14:57   #2625
agarici cu pedale
Ancient friend
 
agarici cu pedale's Avatar
 
Join Date: Mar 2012
Location: Bucuresti
Posts: 7,807
Mentioned: 48 Post(s)

PC-ul meu



Default

SPOILER:

Loading Dump File [C:\Users\Cosy\AppData\Roaming\Skype\My Skype Received Files\062117-13703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`c2e8c000 PsLoadedModuleList = 0xfffff800`c31d85a0
Debug session time: Wed Jun 21 13:33:54.224 2017 (UTC + 3:00)
System Uptime: 0 days 0:22:28.860
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.................................................. ..............

Loading User Symbols
Loading unloaded module list
........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 96, {ffffb28c63352ce0, fffff800c3284650, fffff800c3284380, fffff800c2eaad90}

Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )

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

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

INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: ffffb28c63352ce0, The address of the queue entry whose flink/blink field is NULL
Arg2: fffff800c3284650, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: fffff800c3284380, The base address of the ExWorkerQueue array. This will help determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: fffff800c2eaad90, If this is an ExWorkerQueue (which it usually is), this is the address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.

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


WORKER_ROUTINE:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

WORK_ITEM: ffffb28c63352ce0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x96

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800c304bdbc to fffff800c2ff83f0

STACK_TEXT:
ffff8b80`621c6ac8 fffff800`c304bdbc : 00000000`00000096 ffffb28c`63352ce0 fffff800`c3284650 fffff800`c3284380 : nt!KeBugCheckEx
ffff8b80`621c6ad0 fffff800`c2eca00e : 00000000`00000000 00000000`00000000 fffff800`c3284650 ffffb28c`6c65e040 : nt!KiAttemptFastRemovePriQueue+0xc929c
ffff8b80`621c6b10 fffff800`c2ec9c50 : 00000000`00000100 ffffb28c`6c65e000 fffff800`c2eaad90 00000000`0000000c : nt!KeRemovePriQueue+0x19e
ffff8b80`621c6b80 fffff800`c2f68a37 : ffffb28c`65772cc0 00000000`00000080 ffffb28c`5ea7d040 ffffb28c`6c65e040 : nt!ExpWorkerThread+0x80
ffff8b80`621c6c10 fffff800`c2ffd876 : ffff8b80`1abde180 ffffb28c`6c65e040 fffff800`c2f689f0 ffff813c`029eaa01 : nt!PspSystemThreadStartup+0x47
ffff8b80`621c6c60 00000000`00000000 : ffff8b80`621c7000 ffff8b80`621c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59327910

IMAGE_VERSION: 10.0.15063.413

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x96_nt!IopProcessWorkItem

BUCKET_ID: 0x96_nt!IopProcessWorkItem

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x96_nt!iopprocessworkitem

FAILURE_ID_HASH: {9b586d9a-c1f6-a6de-4692-9ceab4008b6f}

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

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

INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: ffffb28c63352ce0, The address of the queue entry whose flink/blink field is NULL
Arg2: fffff800c3284650, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: fffff800c3284380, The base address of the ExWorkerQueue array. This will help determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: fffff800c2eaad90, If this is an ExWorkerQueue (which it usually is), this is the address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.

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


WORKER_ROUTINE:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

WORK_ITEM: ffffb28c63352ce0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x96

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800c304bdbc to fffff800c2ff83f0

STACK_TEXT:
ffff8b80`621c6ac8 fffff800`c304bdbc : 00000000`00000096 ffffb28c`63352ce0 fffff800`c3284650 fffff800`c3284380 : nt!KeBugCheckEx
ffff8b80`621c6ad0 fffff800`c2eca00e : 00000000`00000000 00000000`00000000 fffff800`c3284650 ffffb28c`6c65e040 : nt!KiAttemptFastRemovePriQueue+0xc929c
ffff8b80`621c6b10 fffff800`c2ec9c50 : 00000000`00000100 ffffb28c`6c65e000 fffff800`c2eaad90 00000000`0000000c : nt!KeRemovePriQueue+0x19e
ffff8b80`621c6b80 fffff800`c2f68a37 : ffffb28c`65772cc0 00000000`00000080 ffffb28c`5ea7d040 ffffb28c`6c65e040 : nt!ExpWorkerThread+0x80
ffff8b80`621c6c10 fffff800`c2ffd876 : ffff8b80`1abde180 ffffb28c`6c65e040 fffff800`c2f689f0 ffff813c`029eaa01 : nt!PspSystemThreadStartup+0x47
ffff8b80`621c6c60 00000000`00000000 : ffff8b80`621c7000 ffff8b80`621c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59327910

IMAGE_VERSION: 10.0.15063.413

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x96_nt!IopProcessWorkItem

BUCKET_ID: 0x96_nt!IopProcessWorkItem

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x96_nt!iopprocessworkitem

FAILURE_ID_HASH: {9b586d9a-c1f6-a6de-4692-9ceab4008b6f}

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

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

INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: ffffb28c63352ce0, The address of the queue entry whose flink/blink field is NULL
Arg2: fffff800c3284650, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: fffff800c3284380, The base address of the ExWorkerQueue array. This will help determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: fffff800c2eaad90, If this is an ExWorkerQueue (which it usually is), this is the address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.

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


WORKER_ROUTINE:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

WORK_ITEM: ffffb28c63352ce0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x96

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800c304bdbc to fffff800c2ff83f0

STACK_TEXT:
ffff8b80`621c6ac8 fffff800`c304bdbc : 00000000`00000096 ffffb28c`63352ce0 fffff800`c3284650 fffff800`c3284380 : nt!KeBugCheckEx
ffff8b80`621c6ad0 fffff800`c2eca00e : 00000000`00000000 00000000`00000000 fffff800`c3284650 ffffb28c`6c65e040 : nt!KiAttemptFastRemovePriQueue+0xc929c
ffff8b80`621c6b10 fffff800`c2ec9c50 : 00000000`00000100 ffffb28c`6c65e000 fffff800`c2eaad90 00000000`0000000c : nt!KeRemovePriQueue+0x19e
ffff8b80`621c6b80 fffff800`c2f68a37 : ffffb28c`65772cc0 00000000`00000080 ffffb28c`5ea7d040 ffffb28c`6c65e040 : nt!ExpWorkerThread+0x80
ffff8b80`621c6c10 fffff800`c2ffd876 : ffff8b80`1abde180 ffffb28c`6c65e040 fffff800`c2f689f0 ffff813c`029eaa01 : nt!PspSystemThreadStartup+0x47
ffff8b80`621c6c60 00000000`00000000 : ffff8b80`621c7000 ffff8b80`621c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59327910

IMAGE_VERSION: 10.0.15063.413

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x96_nt!IopProcessWorkItem

BUCKET_ID: 0x96_nt!IopProcessWorkItem

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x96_nt!iopprocessworkitem

FAILURE_ID_HASH: {9b586d9a-c1f6-a6de-4692-9ceab4008b6f}

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

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

INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: ffffb28c63352ce0, The address of the queue entry whose flink/blink field is NULL
Arg2: fffff800c3284650, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: fffff800c3284380, The base address of the ExWorkerQueue array. This will help determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: fffff800c2eaad90, If this is an ExWorkerQueue (which it usually is), this is the address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.

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


WORKER_ROUTINE:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

WORK_ITEM: ffffb28c63352ce0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x96

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800c304bdbc to fffff800c2ff83f0

STACK_TEXT:
ffff8b80`621c6ac8 fffff800`c304bdbc : 00000000`00000096 ffffb28c`63352ce0 fffff800`c3284650 fffff800`c3284380 : nt!KeBugCheckEx
ffff8b80`621c6ad0 fffff800`c2eca00e : 00000000`00000000 00000000`00000000 fffff800`c3284650 ffffb28c`6c65e040 : nt!KiAttemptFastRemovePriQueue+0xc929c
ffff8b80`621c6b10 fffff800`c2ec9c50 : 00000000`00000100 ffffb28c`6c65e000 fffff800`c2eaad90 00000000`0000000c : nt!KeRemovePriQueue+0x19e
ffff8b80`621c6b80 fffff800`c2f68a37 : ffffb28c`65772cc0 00000000`00000080 ffffb28c`5ea7d040 ffffb28c`6c65e040 : nt!ExpWorkerThread+0x80
ffff8b80`621c6c10 fffff800`c2ffd876 : ffff8b80`1abde180 ffffb28c`6c65e040 fffff800`c2f689f0 ffff813c`029eaa01 : nt!PspSystemThreadStartup+0x47
ffff8b80`621c6c60 00000000`00000000 : ffff8b80`621c7000 ffff8b80`621c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59327910

IMAGE_VERSION: 10.0.15063.413

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x96_nt!IopProcessWorkItem

BUCKET_ID: 0x96_nt!IopProcessWorkItem

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x96_nt!iopprocessworkitem

FAILURE_ID_HASH: {9b586d9a-c1f6-a6de-4692-9ceab4008b6f}

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

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

INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: ffffb28c63352ce0, The address of the queue entry whose flink/blink field is NULL
Arg2: fffff800c3284650, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: fffff800c3284380, The base address of the ExWorkerQueue array. This will help determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: fffff800c2eaad90, If this is an ExWorkerQueue (which it usually is), this is the address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.

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


WORKER_ROUTINE:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

WORK_ITEM: ffffb28c63352ce0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x96

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800c304bdbc to fffff800c2ff83f0

STACK_TEXT:
ffff8b80`621c6ac8 fffff800`c304bdbc : 00000000`00000096 ffffb28c`63352ce0 fffff800`c3284650 fffff800`c3284380 : nt!KeBugCheckEx
ffff8b80`621c6ad0 fffff800`c2eca00e : 00000000`00000000 00000000`00000000 fffff800`c3284650 ffffb28c`6c65e040 : nt!KiAttemptFastRemovePriQueue+0xc929c
ffff8b80`621c6b10 fffff800`c2ec9c50 : 00000000`00000100 ffffb28c`6c65e000 fffff800`c2eaad90 00000000`0000000c : nt!KeRemovePriQueue+0x19e
ffff8b80`621c6b80 fffff800`c2f68a37 : ffffb28c`65772cc0 00000000`00000080 ffffb28c`5ea7d040 ffffb28c`6c65e040 : nt!ExpWorkerThread+0x80
ffff8b80`621c6c10 fffff800`c2ffd876 : ffff8b80`1abde180 ffffb28c`6c65e040 fffff800`c2f689f0 ffff813c`029eaa01 : nt!PspSystemThreadStartup+0x47
ffff8b80`621c6c60 00000000`00000000 : ffff8b80`621c7000 ffff8b80`621c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`c2eaad90 48895c2410 mov qword ptr [rsp+10h],rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59327910

IMAGE_VERSION: 10.0.15063.413

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x96_nt!IopProcessWorkItem

BUCKET_ID: 0x96_nt!IopProcessWorkItem

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x96_nt!iopprocessworkitem

FAILURE_ID_HASH: {9b586d9a-c1f6-a6de-4692-9ceab4008b6f}

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

4: kd>


Asta e facut cu windbg si ma duce la o cauza cu un driver dar nu e clar

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x96

Pana una alta dau dsi driver updates la tot ce am in pc, poate asa scap de driverul ala generic de windows 8 sau ce rahat o fii.

Last edited by agarici cu pedale; 21-06-2017 at 15:17.
agarici cu pedale is offline   Reply With Quote
Old 21-06-2017, 15:29   #2626
agarici cu pedale
Ancient friend
 
agarici cu pedale's Avatar
 
Join Date: Mar 2012
Location: Bucuresti
Posts: 7,807
Mentioned: 48 Post(s)

PC-ul meu



Default

Cred ca l-am gasit pe fraier...

cred ca de la asta era
https://www.pcgarage.ro/adaptoare-bl...us-edr-usb-20/

revin cu update
agarici cu pedale is offline   Reply With Quote
Old 21-06-2017, 16:09   #2627
reflavius
Senior Member
 
reflavius's Avatar
 
Join Date: Sep 2010
Posts: 1,447
Mentioned: 48 Post(s)


Default

99.99 in paranteza )

"fffff802`427e0000 fffff802`427fe000 Microsoft_Bluetooth_Legacy_LEEnumerator T (no symbols)

Unloaded modules:
fffff802`41f90000 fffff802`41fcd000 WUDFRd.sys
fffff802`41f40000 fffff802`41f4b000 cldflt.sys
fffff802`3d9a0000 fffff802`3d9af000 dump_storpor
fffff802`3d9e0000 fffff802`3da07000 dump_storahc
fffff802`3da30000 fffff802`3da4d000 dump_dumpfve
fffff802`3f3b0000 fffff802`3f3d0000 dam.sys
fffff802`3caf0000 fffff802`3caff000 WdBoot.sys
fffff802`3d8a0000 fffff802`3d8af000 hwpolicy.sys
"
Attached Files
File Type: txt 062117-13703-01.dmp.txt (67.3 KB, 13 views)
reflavius is offline   Reply With Quote
Old 21-06-2017, 16:24   #2628
agarici cu pedale
Ancient friend
 
agarici cu pedale's Avatar
 
Join Date: Mar 2012
Location: Bucuresti
Posts: 7,807
Mentioned: 48 Post(s)

PC-ul meu



Default

Yup, de la el era, merci mult.
Ai PM.

Abia ce l-am luat modulul de BT, futu-i si ce ma mai bucuram ca mergea bine.
Oficial cica trebuia sa mearga pe windows 10

Last edited by agarici cu pedale; 21-06-2017 at 16:31.
agarici cu pedale is offline   Reply With Quote
Old 21-06-2017, 17:18   #2629
mbc
Ancient friend
 
mbc's Avatar
 
Join Date: Oct 2010
Location: Cluj-Napoca
Posts: 18,454
Mentioned: 755 Post(s)

PC-ul meu



Send a message via Yahoo to mbc Send a message via Skype™ to mbc
Default

Amu daca iei de la producator de speta asta...

Eu am asta: si merge fara probleme: http://www.pcgarage.ro/adaptoare-blu...sus/usb-bt400/
__________________
Computerul principal in [PC-ul meu]
Lenovo Thinkpad T530, T430, T410, x230, x260 Microserver Gen8, ML10 V2, Brix Projector
Skoda Fabia Combi Ambition 2015, 1.4 TDI 90cp + Octavia Combi Classic 2001, 1.6i 102 cp.
mbc is online now   Reply With Quote
Old 21-06-2017, 17:42   #2630
Snowbawls
Ancient friend
 
Snowbawls's Avatar
 
Join Date: Jan 2013
Location: Bucuresti
Posts: 882
Mentioned: 33 Post(s)

PC-ul meu

Default

Quote:
Originally Posted by mbc View Post
Amu daca iei de la producator de speta asta...

Eu am asta: si merge fara probleme: http://www.pcgarage.ro/adaptoare-blu...sus/usb-bt400/
Lasă că nici Asus nu sunt flawless pe partea de driveri sau implementari de accesorii, dar ai și tu dreptate. Producătorii low cost nu prea investesc Ón QA, ca să nu mai zic de WHQL.

Bine că l-a găsit pe vinovat Ón final.

Sent from my ONEPLUS A3003 using Tapatalk
__________________
- Not to brag, but I've got the latest quad core HHD, my megabytes are 60 Ghz, my wireless RAM is Pentium, I can run websites on my BIOS and blog on my desktop, my GUI is like faster than yours, and I've got the best chipset - over 1 terabyte! Eat it, noob.
Snowbawls is offline   Reply With Quote
Old 21-06-2017, 17:49   #2631
mbc
Ancient friend
 
mbc's Avatar
 
Join Date: Oct 2010
Location: Cluj-Napoca
Posts: 18,454
Mentioned: 755 Post(s)

PC-ul meu



Send a message via Yahoo to mbc Send a message via Skype™ to mbc
Default

Pai nici unul nu e perfect, dar daca ar fi sa risc cu Logilink sau cu Asus, parca as merge cu Asus.
__________________
Computerul principal in [PC-ul meu]
Lenovo Thinkpad T530, T430, T410, x230, x260 Microserver Gen8, ML10 V2, Brix Projector
Skoda Fabia Combi Ambition 2015, 1.4 TDI 90cp + Octavia Combi Classic 2001, 1.6i 102 cp.
mbc is online now   Reply With Quote
Old 22-06-2017, 21:57   #2632
agarici cu pedale
Ancient friend
 
agarici cu pedale's Avatar
 
Join Date: Mar 2012
Location: Bucuresti
Posts: 7,807
Mentioned: 48 Post(s)

PC-ul meu



Default

Am luat si eu unul ca al tau, vad ca e oke acum. Merci mult all.
agarici cu pedale is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

 
Forum Stats
Members: 6,886
Threads: 17,349
Posts: 540,570
Total Online: 190

Newest Member: Kristoph_XP

Latest Threads
- by Boggy
- by Iubitel

Advertisement

Partner Links



All times are GMT +3. The time now is 22:14.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.