Results 1 to 8 of 8

Thread: Blue Screen

  1. #1
    Bronze Lounger
    Join Date
    Jan 2010
    Location
    Birkirkara, Malta
    Posts
    1,467
    Thanks
    205
    Thanked 15 Times in 14 Posts

    Blue Screen

    I attach the minidump file created when my computer crashed this morning, and would greatly appreciate it if someone would please interpret the file for me.

    Thanks and regards,
    Roy

    Correction-when I try to upload the file (121413-29031-01.dmp) I am told the file is invalid. What, if anything, can I do about this?
    OS Dual Boot Windows 10 Pro 64 Bit & Windows 7 Pro With SP1 64 bit. (Intel Core i7 2600K Processor LGA1155-Asus P867 Pro Motherboard-GTX550 Ti DirectCU Graphics Card-Memory 8GB)

    Roy Whitethread

  2. #2
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Hi, Roy. Copy the dump to the Desktop then zip it, attach the zip.

    Better still, carefully read and follow the instructions here: http://www.sysnative.com/forums/bsod...8-7-vista.html then zip the required folder and attach it here. It's better to have background data, especially with only one crash minidump.

  3. #3
    Bronze Lounger
    Join Date
    Jan 2010
    Location
    Birkirkara, Malta
    Posts
    1,467
    Thanks
    205
    Thanked 15 Times in 14 Posts
    Hi satrow, thanks for the explicit instructions. The zipped files are attached, and I await your further comments. (Regarding the performance monitor reference to antivirus, I do have antivirus installed, namely Avast Internet Security, which for some reason does not register with Security Centre).

    With regard to the attachments, I had to alter the file extension from 7z to zip, because I could not attach them otherwise.

    Regards,
    Roy
    Attached Files Attached Files
    Last edited by royw; 2013-12-14 at 07:36.
    OS Dual Boot Windows 10 Pro 64 Bit & Windows 7 Pro With SP1 64 bit. (Intel Core i7 2600K Processor LGA1155-Asus P867 Pro Motherboard-GTX550 Ti DirectCU Graphics Card-Memory 8GB)

    Roy Whitethread

  4. #4
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Hiya, Roy. Many security softwares don't get picked up by the Security Centre, ignore it for now.

    I don't see anything definitive, the Stack Trace for the last BSOD was a single line (basically zero history of what led to the BSOD), the MSInfo32 Windows Error Reports appeared to be truncated to ~12 entries over the last 2 days. Those entries indicated crashes from some 9x different programs, that feels like a lot in such a short time span.

    There's still some background info we can glean from the drivers, etc: there are some old hardware drivers that need updating, I don't think they're any newer on the ASUS support site for your 'board, you'll need to track them down from the chipset makers. From the support site, I do see a number of more recent BIOS versions available, most of which are related to stability and one is for a USB fix (your older crash was USB device -related). I would advise updating the BIOS, be careful and read the instructions and any caveats fully before you begin.

    There's at least one software that seems to be prone to being involved in crashes/stability problems, Rapport is the main one I'd want out of the way, I would uninstall it during troubleshooting. Drivers for virtual hardware are also frequently involved, you have a DVD -related tool that loads a driver for a virtual drive, I would uninstall that as well:
    ElbyCDIO.sys Mon Mar 4 09:21:51 2013 (513467AF)
    CDRTools/ElbyCDIO/DVD Region Killer/VirtualCloneDrive (elby CloneDVD™ 2)/AnyDVD
    http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys.


    Drivers that need updating:

    jraid.sys Tue Aug 10 10:28:44 2010 (4C611BCC)
    JMicron RAID Driver
    http://www.carrona.org/drivers/driver.php?id=jraid.sys

    HECIx64.sys Wed Oct 20 00:33:43 2010 (4CBE2AD7)
    Intel Management Engine Interface
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys

    mvxxmm.sys Mon Nov 22 07:00:18 2010 (4CEA1502)
    Marvell Aux NV Bridge DLL - related to mv91xx SCSI HD Controller
    http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys

    mv91xx.sys Mon Nov 22 07:00:45 2010 (4CEA151D)
    Marvell MV91xx AHCI/RAID driver
    http://www.carrona.org/drivers/driver.php?id=mv91xx.sys

    asmtxhci.sys Thu Feb 24 02:25:47 2011 (4D65C1AB)
    Asmedia USB 3.0 driver
    http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys

    asmthub3.sys Thu Feb 24 02:25:56 2011 (4D65C1B4)
    ASMedia USB 3.0 Hub driver
    http://www.carrona.org/drivers/driver.php?id=asmthub3.sys

    iaStor.sys Tue Apr 26 19:06:18 2011 (4DB7099A)
    Intel Storage drivers
    http://www.carrona.org/drivers/driver.php?id=iaStor.sys

    lvrs64.sys Wed Jan 18 06:40:36 2012 (4F166964)
    Logitech Camera driver
    http://www.carrona.org/drivers/driver.php?id=lvrs64.sys

    lvuvc64.sys Wed Jan 18 06:41:08 2012 (4F166984)
    Logitech USB Video Class Driver (WebCam)
    http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys

    e1c62x64.sys Thu Feb 21 05:14:02 2013 (5125AD1A)
    Intel(R) 82579V Gigabit Network Connection driver
    http://www.carrona.org/drivers/driver.php?id=e1c62x64.sys


    Once you have dealt with the above, I suggest you turn on Driver Verifier for 24-48 hours, it's designed to flush out bad drivers and will create some extra stress. It can also stop some computers from starting - read the workaround for that before you enable it: http://www.sysnative.com/forums/bsod...h-related.html Once you have collected a verified crash dump or two, zip and attach them or re-run the BSOD collection app and attach the fresh results.

  5. #5
    Bronze Lounger
    Join Date
    Jan 2010
    Location
    Birkirkara, Malta
    Posts
    1,467
    Thanks
    205
    Thanked 15 Times in 14 Posts
    Hi satrow, I apologise for the late reply but I have had medical problems for the last few weeks (non life threatening I'm pleased to say) and have only just been able to get back to this thread.

    I truly appreciate the help you are trying to give me, but firstly I am scared to try updating the BIOS (I don't know how to anyway), and when it came to the links for updating drivers I tried several but could not work out which to install and how to download them. I did update one or two but as soon as I started Driver Verifier I then got a further BSOD which it said was caused by a corrupt driver. I managed to restore my system using Macrium Reflect's Recovery Environment to restore a backup image, and I am now tempted to leave things as they are, except for the fact that when I boot to my Win 7 partition I get the following message:

    Asus Setup-[SetupInfo] value is NULL

    I would appreciate your further comments.

    Thanks and regards,
    Roy

  6. #6
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Roy, your health is more important than anything else, don't fret over being late

    So you enabled Driver Verifier and it detected a corrupt driver? Ok, we'll need that memory dump, it should have the bad driver listed, it might be the major cause of the problems. Zip and attach it or re-run the Sysnative App and zip/attach the folder.

    Don't do anything with the BIOS yet.

  7. #7
    Bronze Lounger
    Join Date
    Jan 2010
    Location
    Birkirkara, Malta
    Posts
    1,467
    Thanks
    205
    Thanked 15 Times in 14 Posts
    Hi satrow, thanks again. The .zip file is attached and I await your further advice.

    Regards,
    Roy
    Attached Files Attached Files
    OS Dual Boot Windows 10 Pro 64 Bit & Windows 7 Pro With SP1 64 bit. (Intel Core i7 2600K Processor LGA1155-Asus P867 Pro Motherboard-GTX550 Ti DirectCU Graphics Card-Memory 8GB)

    Roy Whitethread

  8. #8
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Hmm, it hasn't pinpointed the faulty driver, it looks more like a bug in the way Driver Verifier works: http://support.microsoft.com/kb/2550576

    This problem has only been observed after the machine's TCP/IP configuration has been changed from a static IP address to a dynamic address with DHCP, which leaves an empty value for the IPAddress registry key for the network interface.

    NOTE: If the computer is configured to reboot automatically following a failure (within Computer / Properties / Advanced system settings / Startup and Recovery Settings / Automatically Restart checkbox enabled), the STOP error may never appear on the display before the restart occurs. Instead, the machine will restart and display the option for booting Windows into Safe mode. If no dump file is created, the only indication of the failure may be a Critical error logged to the System Event log:

    Event ID: 41
    Source: Kernel-Power
    General: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped
    responding, crashed, or lost power unexpectedly.
    So a false alarm, I'm afraid.

    Perhaps it's time for you to read up on updating that BIOS after all? Or at least update those 2010/11 3rd party drivers?
    HECIx64.sys Intel Management Engine Interface
    mvxxmm.sys Marvell Aux NV Bridge DLL - related to mv91xx SCSI HD Controller
    mv91xx.sys Marvell MV91xx AHCI/RAID driver
    asmtxhci.sys Asmedia USB 3.0 driver
    asmthub3.sys ASMedia USB 3.0 Hub driver
    iaStor.sys Intel Storage drivers
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000000000, caller is trying to allocate zero bytes
    Arg2: 0000000000000000, current IRQL
    Arg3: 0000000000000000, pool type
    Arg4: 0000000000000000, number of bytes
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_0
    
    CURRENT_IRQL:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    LAST_CONTROL_TRANSFER:  from fffff8000371c4ec to fffff8000328fbc0
    
    STACK_TEXT:  
    fffff880`0377e488 fffff800`0371c4ec : 00000000`000000c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0377e490 fffff800`0371cf2b : fffffa80`0393ce00 fffff800`032ba84c fffff980`4551af98 ffffffff`80000ba0 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0377e4d0 fffff800`0372dba8 : 00000000`6547654c 00000000`00000080 00000000`00000010 00001fa0`0000007f : nt!ExAllocatePoolSanityChecks+0xcb
    fffff880`0377e510 fffff800`0372de17 : 00000000`00000000 00000000`00000000 fffff980`6547654c fffff980`42adefec : nt!VeAllocatePoolWithTagPriority+0x88
    fffff880`0377e580 fffff880`07e0f5a1 : 00000000`00000000 00000000`0000002c fffff980`42adefd0 fffff800`0372913c : nt!VerifierExAllocatePoolWithTagPriority+0x17
    fffff880`0377e5c0 fffff880`07e0e7bb : fffff880`07e15c20 fffff980`42adefd0 fffff980`4551af90 fffff980`42adefd0 : tcpipreg!InterfaceAddressRegKeyChangeHandler+0x109
    fffff880`0377e6f0 fffff880`07e0da59 : fffff880`00000001 00000000`00000103 fffff980`4551af70 00000000`00000001 : tcpipreg!TcpipRegQueryAndUpdateKeyValue+0x363
    fffff880`0377e780 fffff880`019e1754 : fffff880`07e13a60 00000000`00000004 00000000`00000000 00000000`00010202 : tcpipreg!TcpipRegStartRegistryKeyNotification+0xbd
    fffff880`0377e7d0 fffff880`07e0e293 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07e19073 : NETIO!RtlInvokeStartRoutines+0x34
    fffff880`0377e810 fffff800`0367a467 : 00000000`00000006 fffffa80`0be4a3a0 fffffa80`0be4b000 00000000`00000001 : tcpipreg!DriverEntry+0x257
    fffff880`0377e860 fffff800`0367a865 : 00000000`00000010 00000000`00000000 00000000`00000010 00000000`00010206 : nt!IopLoadDriver+0xa07
    fffff880`0377eb30 fffff800`03299261 : fffff800`00000000 ffffffff`80000ba8 fffff800`0367a810 fffffa80`0675a040 : nt!IopLoadUnloadDriver+0x55
    fffff880`0377eb70 fffff800`0352c2ea : 00000000`00000000 fffffa80`0675a040 00000000`00000080 fffffa80`06735740 : nt!ExpWorkerThread+0x111
    fffff880`0377ec00 fffff800`032808e6 : fffff880`03589180 fffffa80`0675a040 fffff880`035940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0377ec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tcpipreg!InterfaceAddressRegKeyChangeHandler+109
    fffff880`07e0f5a1 4c8be0          mov     r12,rax
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  tcpipreg!InterfaceAddressRegKeyChangeHandler+109
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tcpipreg
    
    IMAGE_NAME:  tcpipreg.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  506c62be
    
    FAILURE_BUCKET_ID:  X64_0xc4_0_VRF_tcpipreg!InterfaceAddressRegKeyChangeHandler+109
    
    BUCKET_ID:  X64_0xc4_0_VRF_tcpipreg!InterfaceAddressRegKeyChangeHandler+109

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •