in reply to [OT]ish: HTTP/HTML/IO::Socket sanity check.

So, having excluded everything I can think of, and still having the problem, I throw it open to see what idiocies I am commiting?

Well, each BSOD comes with an error message, so you're not relaying that

Remember this? What perl are you running? IO::Socket? OS? msvcrt?

Also , run the debugger already, you know you have to :)

 perl -le" undef $ENV{SYSTEMROOT}; exec qw(perl.exe -e die); "

Replies are listed 'Best First'.
Re^2: [OT]ish: HTTP/HTML/IO::Socket sanity check.
by BrowserUk (Patriarch) on Feb 28, 2012 at 05:12 UTC
    Well, each BSOD comes with an error message, so you're not relaying that

    Okay, what can you make of this, the only variant info from the BSOD screen;

    STOP: 0x0000007E (0XFFFFFFFFC0000005, 0XFFFFF80003667F61, 0XFFFFFA6001
+B08978, 0XFFFFFA6001B08350 )

    [download]
    Remember this?

    If it was a segfault, I could supply that type of info, but it is never displayed because the BSOD takes priority. Nothing is logged in either the system or application logs. It doesn't get chance.

    What perl are you running? IO::Socket? OS? msvcrt?

    Versions of stuff:

    C:\test>perl -v
This is perl, v5.10.1 built for MSWin32-x64-multi-thread
(with 2 registered patches, see perl -V for more detail)
Copyright 1987-2009, Larry Wall
Binary build 1007 [291969] provided by ActiveState http://www.ActiveSt
+ate.com
Built Jan 27 2010 14:12:21
Perl may be copied only under the terms of either the Artistic License
+ or the
GNU General Public License, which may be found in the Perl 5 source ki
+t.
Complete documentation for Perl, including FAQ lists, should be found 
+on
this system using "man perl" or "perldoc perl".  If you have access to
+ the
Internet, point your browser at http://www.perl.org/, the Perl Home Pa
+ge.

C:\test>perl -MIO::Socket -E"say $IO::Socket::VERSION"
1.31

C:\test>ver
Microsoft Windows [Version 6.0.6001]

C:\test>dumpbin /headers \Windows\system32\msvcrt.dll
Microsoft (R) COFF/PE Dumper Version 9.00.21022.08
Copyright (C) Microsoft Corporation.  All rights reserved.


Dump of file \Windows\system32\msvcrt.dll

PE signature found

File Type: DLL

FILE HEADER VALUES
            8664 machine (x64)
               6 number of sections
        4791AD6B time date stamp Sat Jan 19 07:57:31 2008
               0 file pointer to symbol table
               0 number of symbols
              F0 size of optional header
            2022 characteristics
                   Executable
                   Application can handle large (>2GB) addresses
                   DLL

    [download]
    Also , run the debugger already, you know you have to :)

    I'm not sure how running "the debugger" (Perl or other) will help since all useful information will be obliterated by the BSOD?

     perl -le" undef $ENV{SYSTEMROOT}; exec qw(perl.exe -e die); "

    I have quiet literally no idea what that is meant to be telling me (to do?)?

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?
[reply]
[d/l]
[select]
      Okay, what can you make of this, the only variant info from the BSOD screen;

      Perhaps http://zapp5.staticworld.net/howto/graphics/215201-0110-bsod_original.jpg will help you see other useful information on your bluescreen.

      I'm not sure how running "the debugger" (Perl or other) will help since all useful information will be obliterated by the BSOD?

      If you use the debugger to single-step through your script, then I presume that you'll be able to narrow down the source of the problem to a single Perl statement, unless the bluescreen also obliterates your own memories. (Or it may only tell you that the bluescreen doesn't happen when your script is run with the debugger enabled, of course.)

      Meanwhile, I'll see if I can spot anything suspicious in the code, which I haven't had a chance to study yet.

      - tye        

[reply]
        Perhaps http://zapp5.staticworld.net/howto/graphics/215201-0110-bsod_original.jpg will help you see other useful information on your bluescreen.

        Had there been any extra info there I would have noted it.

        However, on one occasion only -- of 3 BSODs this time, and many previous -- it did list some extra info at the bottom:

        USBPORT.SYS 0x00000007E and then a bunch of 16 byte hex addresses simi
+lar but slightly different from the first above.

        [download]

        With that, I disconnected my wifi dongle and plugged in a cable direct to the router and the problem went away. Revert to wifi again and the BSOD comes back.

        Upshot. It looks like you hit the nail on the head with "drivers". I'll have to see if there is a later driver for the USB adapter.

        Thanks for nudging me in the right direction.

        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

        The start of some sanity?
[reply]
[d/l]

In Section Seekers of Perl Wisdom