BSOD przy próbie drukowania na jednej z drukarek sieciowych.

	B O A R D
	» Board » Zadaj pytanie » Archiwum » Szukaj » Stylizacja

M E N U

» Nowości

» Archiwum

» Recenzje / Testy

» Board

» Rejestracja

Szukaj @ TwojePC

	OBECNI NA TPC
	» slanter 00:29 » Flo 00:24 » Zibi 00:20 » SebaSTS 00:16 » ReeX 00:13 » Xeno 00:13 » bmiluch 00:13 » R_I_P_ 00:11 » Chrisu 00:07 » Zbyszek.J 00:07 » Chavez 00:07 » P.J._ 00:07 » Mademan 23:59 » Menah 23:56 » past 23:47 » rainy 23:42 » rooter666 23:41 » XTC 23:36 » zibi13 23:30 » metacom 23:24 Dzisiaj przeczytano 445 postów, wczoraj 31345 Szybkie ładowanie jest: wyłączone.

ccc

A R C H I W A L N A W I A D O M O Ś Ć

BSOD przy próbie drukowania na jednej z drukarek sieciowych. , luckyluc 16/11/12 01:07
Mam drukarko-ploter HP DJ70 a do niej dokupiłem HP JetDirect620n by drukować po sieci. Poustawiałem ip, dostęp do printserwera mam przez www, zainstalowałem od nowa drukarkę programem od hp, teoretycznie wszystko działa wraz z wydrukiem strony testowej windowsa. Problem pojawia się przy próbie wydruku z worda i programu typu CAD (innych programów nie próbowałem) i objawia się BSOD'em z zawartością:
System Service Exception
Technical Information: STOP 0x0000003B
win32k.sys
Jeśli trzeba więcej informacji to mam zdjęcie tego BSOD'a. Gdy ta drukarka jest podpięta przez USB to wszystko jest ok, druga drukarka na której drukuję przez LAN nie powoduje takich ani innych problemów. Ktoś wie w czym tkwi problem i może pomóc? Znalazłem jeden wątek na elektrodzie ale brak rozwiązania :/ System to windows 7 64bit.

// Get rich or die tryin.

a masz , elliot_pl 16/11/12 02:13
dumpy ktore sie tworza podczas bsoda? Zazwyczaj w c:\windows\minidump\*.dmp
Musisz miec zainstalowane microsoft debugging tools:
http://www.microsoft.com/...debugging/default.mspx

tam tego dumpa mozna zaladowac i sprawdzic dokladniej o co chodzi
momtoronomyotypaldollyochagi...
1. tak mam, a w nich jest to: , luckyluc 16/11/12 10:50
  Symbol search path is: *** Invalid ***
  ****************************************************************************
  * Symbol loading may be unreliable without a symbol search path. *
  * Use .symfix to have the debugger choose a symbol path. *
  * After setting your symbol path, use .reload to refresh symbol locations. *
  ****************************************************************************
  Executable search path is:
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  * *
  * The Symbol Path can be set by: *
  * using the _NT_SYMBOL_PATH environment variable. *
  * using the -y <symbol_path> argument when starting the debugger. *
  * using .sympath and .sympath+ *
  *********************************************************************
  Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  Product: WinNt, suite: TerminalServer SingleUserTS
  Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
  Machine Name:
  Kernel base = 0xfffff800`03855000 PsLoadedModuleList = 0xfffff800`03a99670
  Debug session time: Fri Nov 16 00:37:51.921 2012 (UTC + 1:00)
  System Uptime: 0 days 0:55:20.388
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  * *
  * The Symbol Path can be set by: *
  * using the _NT_SYMBOL_PATH environment variable. *
  * using the -y <symbol_path> argument when starting the debugger. *
  * using .sympath and .sympath+ *
  *********************************************************************
  Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  Loading Kernel Symbols
  ...............................................................
  ................................................................
  ........................................
  Loading User Symbols
  Loading unloaded module list
  .....
  *******************************************************************************
  * *
  * Bugcheck Analysis *
  * *
  *******************************************************************************
  
  Use !analyze -v to get detailed debugging information.
  
  BugCheck 3B, {c0000005, fffff960000d5900, fffff8800a2e8f20, 0}
  
  *** WARNING: Unable to verify timestamp for win32k.sys
  *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
  ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  Probably caused by : win32k.sys ( win32k+c5900 )
  
  Followup: MachineOwner
  ---------
  
  1: kd> !analyze -v
  *******************************************************************************
  * *
  * Bugcheck Analysis *
  * *
  *******************************************************************************
  
  SYSTEM_SERVICE_EXCEPTION (3b)
  An exception happened while executing a system service routine.
  Arguments:
  Arg1: 00000000c0000005, Exception code that caused the bugcheck
  Arg2: fffff960000d5900, Address of the instruction which caused the bugcheck
  Arg3: fffff8800a2e8f20, Address of the context record for the exception that caused the bugcheck
  Arg4: 0000000000000000, zero.
  
  Debugging Details:
  ------------------
  
  ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  *** Either you specified an unqualified symbol, or your debugger ***
  *** doesn't have full symbol information. Unqualified symbol ***
  *** resolution is turned off by default. Please either specify a ***
  *** fully qualified symbol module!symbolname, or enable resolution ***
  *** of unqualified symbols by typing ".symopt- 100". Note that ***
  *** enabling unqualified symbol resolution with network symbol ***
  *** server shares in the symbol path may cause the debugger to ***
  *** appear to hang for long periods of time when an incorrect ***
  *** symbol name is typed or the network symbol server is down. ***
  *** ***
  *** For some commands to work properly, your symbol path ***
  *** must point to .pdb files that have full type information. ***
  *** ***
  *** Certain .pdb files (such as the public OS symbols) do not ***
  *** contain the required information. Contact the group that ***
  *** provided you with these symbols if you need this command to ***
  *** work. ***
  *** ***
  *** Type referenced: nt!_KPRCB ***
  *** ***
  *************************************************************************
  
  ADDITIONAL_DEBUG_TEXT:
  You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  
  MODULE_NAME: win32k
  
  FAULTING_MODULE: fffff80003855000 nt
  
  DEBUG_FLR_IMAGE_TIMESTAMP: 5080499b
  
  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
  
  FAULTING_IP:
  win32k+c5900
  fffff960`000d5900 4c8b4c0af8 mov r9,qword ptr [rdx+rcx-8]
  
  CONTEXT: fffff8800a2e8f20 -- (.cxr 0xfffff8800a2e8f20)
  rax=0000000000000040 rbx=0000000000000000 rcx=00000000083bffc8
  rdx=fffffffffb810040 rsi=fffff900c23a7cd8 rdi=fffff900c2c4b9a0
  rip=fffff960000d5900 rsp=fffff8800a2e9908 rbp=0000000004e30040
  r8=00000000003fffc8 r9=000000000001fffe r10=fffff80003a58a00
  r11=0000000007fc0000 r12=000000000165ac68 r13=0000000000000000
  r14=00000000037d0040 r15=00000000003fffc8
  iopl=0 nv up ei pl nz na pe nc
  cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
  win32k+0xc5900:
  fffff960`000d5900 4c8b4c0af8 mov r9,qword ptr [rdx+rcx-8] ds:002b:00000000`03bd0000=????????????????
  Resetting default scope
  
  CUSTOMER_CRASH_COUNT: 1
  
  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  
  BUGCHECK_STR: 0x3B
  
  CURRENT_IRQL: 0
  
  LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960000d5900
  
  STACK_TEXT:
  fffff880`0a2e9908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k+0xc5900
  
  FOLLOWUP_IP:
  win32k+c5900
  fffff960`000d5900 4c8b4c0af8 mov r9,qword ptr [rdx+rcx-8]
  
  SYMBOL_STACK_INDEX: 0
  
  SYMBOL_NAME: win32k+c5900
  
  FOLLOWUP_NAME: MachineOwner
  
  IMAGE_NAME: win32k.sys
  
  STACK_COMMAND: .cxr 0xfffff8800a2e8f20 ; kb
  
  BUCKET_ID: WRONG_SYMBOLS
  
  Followup: MachineOwner
  ---------
  // Get rich or die tryin.
  1. zerknij tutaj , Bitboy_ 16/11/12 10:57
    http://forum.dobreprogramy.pl/...-exe-t472502.html
    i
    http://windows7forum.pl/...acy-bluescreeny-22942-t
    9600K@4.6,AorusEliteZ390,CryorigR1
    Ultimate,GskillRipJawsV360016GB,AsusGTX1070
    ,FraDesION660P
    1. problem na dwóch komputerach , luckyluc 16/11/12 11:16
      jeden stacjonarny drugi laptop. Obecnie wiszę na słuchawce obsługą HP ale na szybko zerknąłem na linki i tam chyba piszą o problemach sprzętowych z ramem, kręceniem itp.
      // Get rich or die tryin.
haha swietne , RusH 16/11/12 09:01
wyglada jak zdalny exploit skoro urzadzenie z sieci jest w stanie wywalic winde
I fix shit
http://raszpl.blogspot.com/
1. co ciekawe , luckyluc 16/11/12 09:52
  mam router z portami usb które mogą robić za print serwer no to pomyślałem świetnie, nie będę musiał kupować JetDirect. Poustawiałem wszystko , drukarkę wpiąłem do usb w routerze, zainstalowałem urządzenie w systemie i objawy były dokładnie te same. Podejrzewasz co z tym zrobić?
  // Get rich or die tryin.
2. zerknij do komentow nt kingstona na glownej , zgf1 16/11/12 13:32
  123
  Leave me alone I know what I'm doing!
sterownika oczywiscie nie bylo do win 7 64bit , faf 16/11/12 09:12
wiec wrzuciles z XP ?

i sie dziwisz ?

sterownik nie kuma pewnie czaczy ze urzadzenie mu dziwnie gada i robi hopla
1. masz na myśli sterownik do drukarki? , luckyluc 16/11/12 09:49
  jest do win7 64bit i ma się dobrze, pisałem że na usb działa.
  // Get rich or die tryin.
  1. no ok - ale dalej to sterownik jest kupa , faf 16/11/12 12:48
    z dumpa
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    
    sterownik spodziewa sie komunikacji po USB
    raczej HP zrobilo bube
    1. jak zwykle , sred 16/11/12 13:50
      zresztą,
      HP powinno mieć zakaz produkcji softu i sterowników do kombajnów... ;-)
    2. miałeś rację , luckyluc 16/11/12 18:06
      zasugerowali instalację sterowników od xp 64bit i o dziwo działa.
      // Get rich or die tryin.
pomoc techniczna w hp gada po Polsku prosto z Holandi , luckyluc 16/11/12 11:59
najpierw babka (Polka) z działu DesignJet po wysłuchaniu przełączyła do działu JetDirect w którym gość (Polak) poinformował że obsługa jest powiązana z modelem drukarki więc odesłał z powrotem do DesignJet i tu szok: pojawiła się kobieta (nie Polka) z ewidentnie nie polskim akcentem zadała dodatkowe pytania i na koniec powiedziała że oddzwoni, spytała czy będzie dzwonić z Polski, roześmiała się i powiedziała że nie, że dzwoni z Holandii. Ciekawe że ludzie uczą się Polskiego by pracować w Holandii w dziale wsparcia.
// Get rich or die tryin.
1. moze ma rodzine , elliot_pl 16/11/12 15:30
  po polsku i jej to w pracy pomoglo :)
  momtoronomyotypaldollyochagi...
  1. okazało się że to Czeszka , luckyluc 16/11/12 16:06
    123
    // Get rich or die tryin.
chyba jednak to nie wina sterowników tylko 2 takich samych drukarek w systemie. , luckyluc 16/11/12 19:32
Problem był raczej po mojej stronie. Wynika że nie można mieć tej samej drukarki zainstalowanej 2 razy , a ja tak miałem. Jedna była zainstalowana dla kabla usb a druga jako sieciowa, a było tak na wszelki wypadek gdyby mnie nie było w domu a sieć się wysypała to mama by wtedy tylko wpięła kabel usb... No cóż ja nie wiedziałem, że tak nie można.
// Get rich or die tryin.
1. i ty twierdzisz ze to twoja wina? , elliot_pl 16/11/12 21:30
  to jakis zart... owinno byc mozna instalowac drukarke i 5x z roznymi portami - jaki ma to wplyw jesli driver jest normalny a nie indyjski?
  momtoronomyotypaldollyochagi...
  1. hp nie zna pojęcia , Artaa 16/11/12 21:46
    normalny driver...
    
    ;-)
    1. ehhh , elliot_pl 16/11/12 21:49
      ze lza w oku wspominam starego compaqa
      momtoronomyotypaldollyochagi...
  2. nie znam się na pisaniu sterowników do urządzeń , luckyluc 17/11/12 10:24
    zatem nie wiem jakie ograniczenia narzucają systemy operacyjne i czy w ogóle narzucają. Kiedyś było tak że rzeczy związane z komputerami stały na wysokim poziomie i co najlepsze były idioto odporne, teraz ... no cóż widzimy jak jest, zaczynają wchodzić coś a'la tanie chińskie zabawki :/
    // Get rich or die tryin.