Gå til innhold

WackenSS

Medlemmer
  • Innlegg

    138
  • Ble med

  • Besøkte siden sist

Innlegg skrevet av WackenSS

  1. Hæres ut som det jeg sliter med. Jeg hadde versjon 5 og akkurat samme problemet. Fikk internet tilbake idag men det skjer litt for mye i helgen til at jeg får kikket noe på det. Skal prøve igjen til uken.

     

    Fikk kikket litt innom telenor/min side og kan ikke se annet en wifi passord og navn som kan endres.

    Det eneste avviket jeg kan se er at jeg kun har bokstaver i wifi passordet, mens min side sier jeg må ha en blanding av stor og liten bokstav og tall. Kan da ikke være dette som lager krøll?

  2. Kan du prøve å se om det er noen fany innstillinger som du finner om du logger på Telenor MineSider, er vist slik at man ikke får tilgang til alle instillnger via managmentsiden rett på routeren? (ref),

    Dette skal sjekkes ut så fort jeg har nett!

     

    Ellers minner jo dette noe om en innstilling som man finner i DDWRT,hvor man kan velge om wifi skal være bridged eller unbridged

    denne linken fikk ikke jeg opp.

     

    I og med at router laster ned config fra Telenor ved boot, kan det fort lage mer krøll og drive å downgrade roteren? Kan jo være verdt å forsøke å ta kontakt med Telenor på en eller annen måte, for via facebook?

    De skal bare sørge for inntekter til telenorhjelpen...

     

    Det er fortsatt brudd i den 6700meter lange kobberkabelen fra sentralen til mitt hus så prosjektet ligger dødt intill jeg får igjen min sinnsyke 2500/400 linje!

  3. Kan du prøve å se om det er noen fany innstillinger som du finner om du logger på Telenor MineSider, er vist slik at man ikke får tilgang til alle instillnger via managmentsiden rett på routeren? (ref),

    Dette skal sjekkes ut så fort jeg har nett!

     

    Ellers minner jo dette noe om en innstilling som man finner i DDWRT,hvor man kan velge om wifi skal være bridged eller unbridged

    denne linken fikk ikke jeg opp.

     

    I og med at router laster ned config fra Telenor ved boot, kan det fort lage mer krøll og drive å downgrade roteren? Kan jo være verdt å forsøke å ta kontakt med Telenor på en eller annen måte, for via facebook?

    De skal bare sørge for inntekter til telenorhjelpen...

     

    Det er fortsatt brudd i den 6700meter lange kobberkabelen fra sentralen til mitt hus så prosjektet ligger dødt intill jeg får igjen min sinnsyke 2500/400 linje!

  4. Har som sagt 2 stk zyxel p8702n liggende. Etter factory reset hadde jeg fortsatt ikke nett. Prøvde så og sette opp den andre uten hell. Ringer telenor og de innrømmer problemer med nette og skal være utbedret i løpet av dagen... kjent historie!

     

    Det jeg så inne i routerene er at jeg i utgangspunktet hadde den nyeste og den nest nyeste SW til routeren. Etter downgrading av den ene har jeg nå 2 stk med versjon aajx.4

  5. Studerte aldri den gamle routeren da dette bare fungerte. Husker riktignok at den hadde samme adresse (10.0.0.138) som den nye. Netmask er 255.255.255.0

     

    Skal lage et kart slik at dere kan se oppsettet, men først; er det ingen mulighet for at det er zyxel som må ha en bestemt innstilling for og akseptere at jeg kan sende data inn på lan via WiFi?

     

    Skal prøve for morro skyld kutte ut switchen i zyxel og sette opp min egen GB switch.

     

    Dhcp.

    Android 10.0.0.91

    HP win7 laptop 10.0.0.51.

    yamaha forsterker 10.0.0.89

    xbmc raspberry pi 10.0.0.31

    linksys AP 10.0.0.20

     

    Statisk IP.

    Win7 pc. 10.0.0.35

    Win7 server 10.0.0.36

  6. nå har jeg forsket endel, og endret AP til statisk 10.0.0.20 som er innenfor .0 og .137 som routeren fra telenor godtar. Nå dukker alle enhetene opp i nettverkskartet på routeren min, men fortsatt ingen kontakt med xbmc, yamaha forsterkeren, teamwiewer eller spotimote fra zyxel routeren. Ping fra bærbar pc får ikke svar fra noen så lenge jeg kobler meg mot zyxel. kobbler jeg meg på AP så kan jeg pinge alle adresser.

     

    Det er heller ingen bedring vis jeg kobler AP helt vekk. Firewall er satt til minimum eller helt avskrudd i zyxel uten bedring.

     

    Som om jeg ikke var LOST tidligere så er jeg det nå!

     

    Har 2 stk identiske zyxel modem (den ene er reserve) Prøvde og bytte de om uten endring.

     

    Forstår virkelig ikke hva som skjer...

  7. Lagt ved en tegning av oppsettet. Det access pointet jeg har er en liten boks fra linksys som heter access point og kun 1 stk rj45 tilkobling. Kan den route noe da? Det er riktignok noe rart med den,den dukker nemlig ikke opp i nettverkskartet. For og gjøre endringer i SW må jeg koble den direkte til en pc med patch kabel. Uansett, hadde ikke noen problemer med den nye eldre zyxel routeren som stod der før jeg fikk den nye av Telenor.

    post-192517-0-45399500-1414937946_thumb.jpg

  8. Et par ting irritere meg kraftig på denne tlf! Noen som har erfart?

     

    nr 1. Man kan ikke sortere apper alfabetisk med liste funksjon.

    Altså at man har alle apene på én side som man kan bla opp og ned i.

     

    Nr 2. Automatisk lysstyrke på skjermen er helt ubrukelig. Noen ganganger så

    treg at sola har gått ned før den reagerer, mens andre ganger så gjør den ingen ting...

  9. Prøvde og lese en .dmp fil i Windbg, men som forventet så er det ikke noe jeg forstår noe av, vet ikke om det er feil i loggen eller om loggen har fått de "symbolfilene" den skal.

     

    Noen som kan ta meg et steg videre?

     

    Pc specs:

    AMD phenom 9650 Quad core 2.30ghz

    Fabrikant ASUSTeK Computer INC.
    Modell M2N32-SLI DELUXE
    Versjon 1.XX
    Serienummer 123456789000
    Bro
    Nordbro NVIDIA SPP190 (C51XE) Revision A2
    Sørbro NVIDIA nForce 590 SLI Revision A2
    CPU
    Navn AMD Phenom 9650 Quad-Core Processor
    Cpu kontakt Socket AM2+ (940)
    Max CPU hastighet 3700MHz
    Minne sum Reported by BIOS
    Minne type DDR2
    Installed Memory 4096 MBytes
    Available Memory 4095 MBytes
    Channels Dual
    Maksimum kapasitet 16384 MBytes
    Maksimum minne modul størrelse 4096 MBytes
    Minne porter 4
    Feil retting Ingen
    System spor
    ISA 0
    PCI 6
    AGP 0
    VL-BUS 0
    EISA 0
    PCMCIA 0
    ExpressCard 0
    MCA 0

     

    Win 7 Ultimate sp1

     

    Video Adapter NVIDIA GeForce 6200SE TurboCache
    Grafikkprosessor GeForce 6200SE TurboCache
    Adapter DAC Type Integrated RAMDAC
    PCI ID 0x10DE / 0x0162 - NVIDIA Corporation / GeForce 6200SE TurboCache
    PCI sub ID 0x1043 / 0x0345 - ASUSTeK Computer Inc
    Minne 64 MBytes
    Dedicated Video Memory 57 MB (60805120)
    Dedicated System Memory 0 MB (0)
    Shared System Memory 1007 MB (1056374784)
    Adapter BIOS String Version 5.44.02.37.06
    Adapter BIOS Date 07/21/05
    PnP Device Id PCI\VEN_10DE&DEV_0162&SUBSYS_03451043&REV_A1\4&2AD12F4B&0&0020
    Video Mode Description 1280 x 1024 x 4294967296 colors
    Driverversjon 9.18.13.783
    Driver Dato 2013-01-31 00:00:00
    DirectX DirectX 11
    Driver Name nvd3dum.dll
    Driver Description NVIDIA GeForce 6200SE TurboCache
    Denne maskinen står og server 6-8 disker og står kjølig uten skjerm og tastatur. Bruker kun teamwiever for og vedlikeholde/flytte filer. Derfor har jeg satt i et enkelt skjermkort for det dekker behovet..

     

    BSOD kommer alltid vis jeg flytter filer, men det kan ta alt fra 2 min till 60 min før blåskjerm.

     

     

    Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright © Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\SERVER\Desktop\071114-24102-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Symbol search path is: srv*c:\symboler*http://msdl.microsoft.com/download/symbols
    Executable search path is: srv*c:\symboler*http://msdl.microsoft.com/download/symbols
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02ca46d0
    Debug session time: Fri Jul 11 02:44:51.103 2014 (UTC + 2:00)
    System Uptime: 0 days 5:11:46.976
    Loading Kernel Symbols
    .
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    ..............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1E, {0, 0, 0, 0}
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Debugging Details:
    ------------------
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0x1E
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    DPC_STACK_BASE: FFFFF80000BA2FB0
    EXCEPTION_RECORD: fffff80000b9ca18 -- (.exr 0xfffff80000b9ca18)
    ExceptionAddress: fffff80002a484f8 (hal!HalpKInterruptHeap+0x00000000000004f8)
    ExceptionCode: c000001d (Illegal instruction)
    ExceptionFlags: 00000000
    NumberParameters: 0
    TRAP_FRAME: fffff80000b9cac0 -- (.trap 0xfffff80000b9cac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffffffffffe7bf rbx=0000000000000000 rcx=fffffa8005072a90
    rdx=fffffa80050776a8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a484f8 rsp=fffff80000b9cc58 rbp=0000000000000000
    r8=0000000000000000 r9=0000000a94a0f5fc r10=000000000001c392
    r11=fffff80002c51e80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di ng nz na pe nc
    hal!HalpKInterruptHeap+0x4f8:
    fffff800`02a484f8 ?? ???
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80002ace5be to fffff80002ad6b90
    STACK_TEXT:
    fffff800`00b9baf8 fffff800`02ace5be : fffff800`00b9bb18 00000000`00000028 fffff800`00b9c270 fffff800`02b01a90 : nt!KeBugCheck
    fffff800`00b9bb00 fffff800`02b0175d : fffff800`02ce50ec fffff800`02c23a80 fffff800`02a61000 fffff800`00b9ca18 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00b9bb30 fffff800`02b00535 : fffff800`02c26038 fffff800`00b9bba8 fffff800`00b9ca18 fffff800`02a61000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00b9bb60 fffff800`02b114c1 : fffff800`00b9ca18 fffff800`00b9c270 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
    fffff800`00b9c240 fffff800`02ad6242 : fffff800`00b9ca18 00000000`00000000 fffff800`00b9cac0 fffff800`02c51e80 : nt!KiDispatchException+0x135
    fffff800`00b9c8e0 fffff800`02ad439f : fffff800`00b9cac0 fffff800`02a22800 fffff800`02a48400 fffff800`00000000 : nt!KiExceptionDispatch+0xc2
    fffff800`00b9cac0 fffff800`02a484f8 : 00000000`00000000 00000000`0001e296 fffff880`048297f2 00000000`00000010 : nt!KiInvalidOpcodeFault+0x11f
    fffff800`00b9cc58 00000000`00000000 : 00000000`0001e296 fffff880`048297f2 00000000`00000010 00000000`00000246 : hal!HalpKInterruptHeap+0x4f8
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`02ace5be 90 nop
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
    IMAGE_VERSION: 6.1.7601.18247
    FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
    BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x1e_nt!kikernelcalloutexceptionhandler+e
    FAILURE_ID_HASH: {31b31670-23d4-78dd-b3a6-d5566ed846e6}
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Debugging Details:
    ------------------
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0x1E
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    DPC_STACK_BASE: FFFFF80000BA2FB0
    EXCEPTION_RECORD: fffff80000b9ca18 -- (.exr 0xfffff80000b9ca18)
    ExceptionAddress: fffff80002a484f8 (hal!HalpKInterruptHeap+0x00000000000004f8)
    ExceptionCode: c000001d (Illegal instruction)
    ExceptionFlags: 00000000
    NumberParameters: 0
    TRAP_FRAME: fffff80000b9cac0 -- (.trap 0xfffff80000b9cac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffffffffffe7bf rbx=0000000000000000 rcx=fffffa8005072a90
    rdx=fffffa80050776a8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a484f8 rsp=fffff80000b9cc58 rbp=0000000000000000
    r8=0000000000000000 r9=0000000a94a0f5fc r10=000000000001c392
    r11=fffff80002c51e80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di ng nz na pe nc
    hal!HalpKInterruptHeap+0x4f8:
    fffff800`02a484f8 ?? ???
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80002ace5be to fffff80002ad6b90
    STACK_TEXT:
    fffff800`00b9baf8 fffff800`02ace5be : fffff800`00b9bb18 00000000`00000028 fffff800`00b9c270 fffff800`02b01a90 : nt!KeBugCheck
    fffff800`00b9bb00 fffff800`02b0175d : fffff800`02ce50ec fffff800`02c23a80 fffff800`02a61000 fffff800`00b9ca18 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00b9bb30 fffff800`02b00535 : fffff800`02c26038 fffff800`00b9bba8 fffff800`00b9ca18 fffff800`02a61000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00b9bb60 fffff800`02b114c1 : fffff800`00b9ca18 fffff800`00b9c270 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
    fffff800`00b9c240 fffff800`02ad6242 : fffff800`00b9ca18 00000000`00000000 fffff800`00b9cac0 fffff800`02c51e80 : nt!KiDispatchException+0x135
    fffff800`00b9c8e0 fffff800`02ad439f : fffff800`00b9cac0 fffff800`02a22800 fffff800`02a48400 fffff800`00000000 : nt!KiExceptionDispatch+0xc2
    fffff800`00b9cac0 fffff800`02a484f8 : 00000000`00000000 00000000`0001e296 fffff880`048297f2 00000000`00000010 : nt!KiInvalidOpcodeFault+0x11f
    fffff800`00b9cc58 00000000`00000000 : 00000000`0001e296 fffff880`048297f2 00000000`00000010 00000000`00000246 : hal!HalpKInterruptHeap+0x4f8
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`02ace5be 90 nop
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
    IMAGE_VERSION: 6.1.7601.18247
    FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
    BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x1e_nt!kikernelcalloutexceptionhandler+e
    FAILURE_ID_HASH: {31b31670-23d4-78dd-b3a6-d5566ed846e6}
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Debugging Details:
    ------------------
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ExceptionRecord ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: ContextRecord ***
    *** ***
    *************************************************************************
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0x1E
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    DPC_STACK_BASE: FFFFF80000BA2FB0
    EXCEPTION_RECORD: fffff80000b9ca18 -- (.exr 0xfffff80000b9ca18)
    ExceptionAddress: fffff80002a484f8 (hal!HalpKInterruptHeap+0x00000000000004f8)
    ExceptionCode: c000001d (Illegal instruction)
    ExceptionFlags: 00000000
    NumberParameters: 0
    TRAP_FRAME: fffff80000b9cac0 -- (.trap 0xfffff80000b9cac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffffffffffe7bf rbx=0000000000000000 rcx=fffffa8005072a90
    rdx=fffffa80050776a8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a484f8 rsp=fffff80000b9cc58 rbp=0000000000000000
    r8=0000000000000000 r9=0000000a94a0f5fc r10=000000000001c392
    r11=fffff80002c51e80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di ng nz na pe nc
    hal!HalpKInterruptHeap+0x4f8:
    fffff800`02a484f8 ?? ???
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80002ace5be to fffff80002ad6b90
    STACK_TEXT:
    fffff800`00b9baf8 fffff800`02ace5be : fffff800`00b9bb18 00000000`00000028 fffff800`00b9c270 fffff800`02b01a90 : nt!KeBugCheck
    fffff800`00b9bb00 fffff800`02b0175d : fffff800`02ce50ec fffff800`02c23a80 fffff800`02a61000 fffff800`00b9ca18 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00b9bb30 fffff800`02b00535 : fffff800`02c26038 fffff800`00b9bba8 fffff800`00b9ca18 fffff800`02a61000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00b9bb60 fffff800`02b114c1 : fffff800`00b9ca18 fffff800`00b9c270 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
    fffff800`00b9c240 fffff800`02ad6242 : fffff800`00b9ca18 00000000`00000000 fffff800`00b9cac0 fffff800`02c51e80 : nt!KiDispatchException+0x135
    fffff800`00b9c8e0 fffff800`02ad439f : fffff800`00b9cac0 fffff800`02a22800 fffff800`02a48400 fffff800`00000000 : nt!KiExceptionDispatch+0xc2
    fffff800`00b9cac0 fffff800`02a484f8 : 00000000`00000000 00000000`0001e296 fffff880`048297f2 00000000`00000010 : nt!KiInvalidOpcodeFault+0x11f
    fffff800`00b9cc58 00000000`00000000 : 00000000`0001e296 fffff880`048297f2 00000000`00000010 00000000`00000246 : hal!HalpKInterruptHeap+0x4f8
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`02ace5be 90 nop
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
    IMAGE_VERSION: 6.1.7601.18247
    FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
    BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x1e_nt!kikernelcalloutexceptionhandler+e
    FAILURE_ID_HASH: {31b31670-23d4-78dd-b3a6-d5566ed846e6}
    Followup: MachineOwner
    ---------
  10. Altfor teknisk kompliserte Kickstarter-prosjekter har jeg egentlig ikke troen på. Det er noen som klarer seg, som f.eks. Twine og Pebble: Ja, de er tekniske produkter, men de har et noe begrenset bruksområder.

     

    Andre lover å kunne gjøre "absolutt alt", eller iallfall ganske mye. Jeg har selv fått lyspæren LiFX i hus, og selv om det prosjektet ble ganske kraftig forsinket, så har de enda ikke klart å lage en firmware som jeg får koblet opp mot et nettverk, uansett hvilken konfigurasjon jeg har. Thermodo fungerer ikke med Samsung S4, en av de mest solgte mobiler i det siste året, selv om også den ble ganske forsinket.

     

    Mange nerder har en veldig stor tro på prosjektet sitt, og det er bra. Det må man ha. Men noen er rett og slett lite realistiske.

     

     

     

    Vet ikke hvordan det er med kaffetraktere utenfor Vestfold, men min er ihverfall koblet til nettspenning, hvilket er et stykke over 32 volt... denne enheten kan nok ikke ta på seg oppgaver i et 230v miljø.

    Den er utstyrt med reléer. Strømmen trenger ikke gå gjennom selve enheten, kun reléet...
    jeg skjønner det, og kan konkluder med og sette inn denne som en av/på bryter i en kaffetrakter uten ekstrautstyr lar seg kke gjøre...
×
×
  • Opprett ny...