Jump to content

g__day

Hero
  • Content count

    649
  • Joined

  • Last visited

  • Days Won

    6

g__day last won the day on November 28 2017

g__day had the most liked content!

Community Reputation

64 Learner

About g__day

  • Rank
    Master
  • Birthday 09/12/1961
  1. So some major progress - I now have 1) admin user id and password - and have been shown how to use Excel 2013 with PowerQuery add on - which reads javascript really well! I can now query the old or classic views of my device - with the admin user id, or the new views using PowerQuery and if the URL is not protected all is fine. My Dilemma If in Excel I simply select Data -> From Web and supply the URL User Id and Password – it works fine – but it returns javascript which Excel simply can't natively ingest. If in Excel I select Powerquery -> from Web, it asks basic or advanced. If I chose basic – it only asks for the url and this fails. If I chose Advanced – I don't know how to format the query to supply the user id and password. Which is annoying given Powerquery natively does support Javascript and easily converts it into readable tables! If in Powerquery I try and reach say http://envoy:011842@192.168.0.12/api/v1/production/inverters the call will fail and bring up web access – where I can choose API, Simple or web access – and for simple or advanced I can add user id and password – but the call simply hangs. Does anyone know how to use Excel 2013 with PowerQuery on a web access call to supply the user id and password? Many thanks, Matthew
  2. Interesting development last week - GITHub posted a 20.4MB 64 bit version of Deep Sky Stacker v4.1.0 and its much, much faster - I just stacked 20 images of M20 and all up it took about 3 minutes. https://github.com/LucCoiffier/DSS/releases/download/4.1.0-Release/DeepSkyStacker64Installer.zip Have to play with it some more - but it looks pretty much the same - just the stacking is a lot faster, not sure about the registering but stacking was wow the first time around!
  3. g__day

    Windows10 BSOD WHEA

    I think it more likely there may have been an under voltage at low usage issue (no idea why it took so long to manifest unless a Windows update automatically triggered it. An updated BIOS may have side stepped the issue by raising an auto / default voltage for the detected CPU. Still watching the stability but so far so good!
  4. g__day

    Windows10 BSOD WHEA

    Asked on Whirlppol forums - they are quite good. They ran thru my dump file - concurred it was hardware related bug, said the idle CPU voltages seem low - suggested I update my motherboard BIOS and see if a new BIOS better manages these new CPUs. Did so and no crashes for two weeks :)
  5. Fresh reinstall on a re-formatted disk - the nuclear option - sorted it. Total p.i.t.a.
  6. g__day

    Windows10 BSOD WHEA

    Scorptec said send it back and we will fix / replace whatever is wrong :) So will likely do that next week! From WhoCrashed: Just ran Whocrashed thanks for the suggestion. It could provide very little information - it just says it thinks it is an unspecified hardware fail: On Sat 17/03/2018 2:04:55 AM your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF) Bugcheck code: 0x124 (0x0, 0xFFFFAD0960174028, 0xB2000000, 0x70005) Error: WHEA_UNCORRECTABLE_ERROR file path: C:\Windows\system32\hal.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Hardware Abstraction Layer DLL Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
  7. g__day

    Windows10 BSOD WHEA

    One surprising thing - never seems to crash in playing a game for hours - but surf the net or watch youtube for 5 mins... So maybe some h/w isn't playing nice at low utilisation? A voltage is too low somewhere. Scorptec have been good - saying just drop it in to use (1km away) and its under warranty - we will replace whatever maybe broken - first guy wondered memory or CPU - not cheap fixes. I did run System restore - memtest - Chkdsk - all fine. Will try options suggested above - given PC is stable enough. Thanks all!
  8. g__day

    Windows10 BSOD WHEA

    Will do mate. BTW - just played Serious Sam 3 for an hour or two - rock solid - which makes me wonder if its a registry error if its crashing in a browser or excel? The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. The above error happen many times in the last 24 hours. The other error was: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff830d0cd75028, 0x00000000b2000000, 0x0000000000070005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 86634aa3-7259-4e7a-87ce-5e06da5d2039..
  9. Hi folks On my new big rig the PC now just randonly crashes - usually within 5-10 mins of booting with a WHEA unrecoverable error. I haven't been overclocking or using it hard - nor any changes put thru. ANy ideas how to fix this very persistent and annoying issue - system restore hasn't helped! Thanks, Matthew
  10. About 20 times faster than before - it was definitely CPU bound before :)
  11. Adia64 confirms yes 3,000 MHz - success! Many thanks all!
  12. Well further development - nothing I did at the BIOS seemed to give the desired result. I tried the Gigabtye Windows utility for overclocking and selected only RAM - shifted it to 3000 MHz - rebooted - Windows Performance manager still said it was 2133MHz but CPU-Z and Futuremark seem to think its 3000MHz RAM. They sure don't go out of their way to documenting things well or making life easy!
  13. Yes - memory frequency appears at 3000 MHz and 2133 MHz - with no documentation as to why two numbers appear nor what informs the BIOS as to which number to choose. More sleuthing required!
  14. Monitor solution found thanks to doctor google! Under BIOS -> boot - RoG advises turn CSM off - disabling capability system mode switched screen straight away so not my landscape 30" Kogan presents the BIOS boot screen staright away and now the portrait Acer and Samsung are inert - which I can live with. Finally I can read the BIOS without twisting my neck off! Thanks all! Now I just have to figure out why the BIOS RAM frequency with XMP says 100 MHz with 30 multiplier but shows speed as both 3000 MHz and 2133 MHz - then selects the 2133 MHz option. Back to Google I reckon. It was only on youtube I discovered that although the Corsair RAM is very good - and is stable at 3000 MHz - someone, somewhere defines that as an overclock - versus a marketed clock - and obscures what you have to do to achieve this rated clocking speed.
  15. On all re-starts of any kind. The main monitor simply isn't getting any signal at all until Windows does its circle thing. My ACER 24" monitor uses Display port - it is fine, Kogan is dead until the Windows balls of display life appear, the Samsung 24" connects using HDMI - it gets nothing until I sign in to Windows with my password.
×