Results 1 to 11 of 11

Thread: My BSOD

  1. #1
    Lounger
    Join Date
    Dec 2009
    Location
    Somerset
    Posts
    26
    Thanks
    3
    Thanked 0 Times in 0 Posts

    Angry My BSOD

    051613-41059-01.zip

    This is Win 7 64bit OS and this BSOD comes up very occasionally.
    All programmes on this OS are at a minimum.
    Your opinion much appreciated as too what is the cause......
    Jim

  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 Jim and Welcome to the Lounge!

    Fixing a BSOD from just one dump is frequently impossible without further details/logs, etc.; here though, there are some old drivers listed and one of them is known to cause BSOD's in W7. There's more than an element of guesswork here as ASUS do not supply Windows 7 drivers for your motherboard - please create a Restore point before continuing: http://windows.microsoft.com/en-US/w...-restore-point

    First update the main nForce chipset drivers (nvm62x64.sys): http://www.nvidia.com/object/nforce-...58-driver.html then reboot.

    Next, unzip the attachment: asacpi.sys.zip, open Device Manager and locate the ATK0110 ACPI UTILITY (you may need to go to > View > Show hidden devices and look in the Non-Plug and play category), right-click it and select Update driver > point the browser to the unzipped folder for it to update. You'll probably need to reboot for it to take effect. Once done, check the details for the driver in Device Manager, it should now be 7/16/2009.

    To update the Marvell SATA/RAID driver (mv614x.sys) download the driver from here: http://drivers.softpedia.com/progDow...oad-90126.html and unzip it, update it via Device Manager.

    I don't see an Adaptec SCSI controller listed for your motherboard, if you haven't added a PCI Adaptec card, you should be safe to uninstall it via Device Manager. If you do have one installed, try finding a more recent driver here: http://www.adaptec.com/en-us/support/u320/
    Code:
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffe8a004849998, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002d927ea, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000007, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf9100
     ffffe8a004849998 
    
    FAULTING_IP: 
    nt!CmpInsertKeyHash+7a
    fffff800`02d927ea 4c895cd310      mov     qword ptr [rbx+rdx*8+10h],r11
    
    MM_INTERNAL_CODE:  7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880087702f0 -- (.trap 0xfffff880087702f0)
    .trap 0xfffff880087702f0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000e0a270
    rdx=0000000000000b31 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d927ea rsp=fffff88008770488 rbp=0000000000e8dce0
     r8=0000000000000000  r9=0000000000000000 r10=0000000027ba57bb
    r11=fffff8a00c769cd0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!CmpInsertKeyHash+0x7a:
    fffff800`02d927ea 4c895cd310      mov     qword ptr [rbx+rdx*8+10h],r11 ds:04c8:00000000`00005998=????????????????
    .trap
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002b3e52b to fffff80002ac1c00
    
    STACK_TEXT:  
    fffff880`08770188 fffff800`02b3e52b : 00000000`00000050 ffffe8a0`04849998 00000000`00000001 fffff880`087702f0 : nt!KeBugCheckEx
    fffff880`08770190 fffff800`02abfd2e : 00000000`00000001 ffffe8a0`04849998 00000000`00020000 ffffe8a0`04844000 : nt! ?? ::FNODOBFM::`string'+0x43781
    fffff880`087702f0 fffff800`02d927ea : fffff800`02d902d2 00000000`00000000 00000000`5ba218df 00000000`0a071200 : nt!KiPageFault+0x16e
    fffff880`08770488 fffff800`02d902d2 : 00000000`00000000 00000000`5ba218df 00000000`0a071200 fffff8a0`0008b760 : nt!CmpInsertKeyHash+0x7a
    fffff880`08770490 fffff800`02d64410 : fffff8a0`00e0a270 00000000`00e8dce0 fffff8a0`063f9ce4 fffff8a0`024d9b98 : nt!CmpCreateKeyControlBlock+0x203
    fffff880`08770530 fffff800`02d8d217 : fffff8a0`ffffff00 fffff880`00e8dce0 fffff8a0`024d9b98 fffff880`00000002 : nt!CmpAddInfoAfterParseFailure+0xc4
    fffff880`087705d0 fffff800`02dbe958 : fffffa80`05d871c8 fffffa80`00000001 fffffa80`05d87010 00000000`00000001 : nt!CmpParseKey+0x1177
    fffff880`087708d0 fffff800`02dbfb76 : 00000000`00000274 fffffa80`05d87010 00000000`00000000 fffffa80`0381e7a0 : nt!ObpLookupObjectName+0x588
    fffff880`087709c0 fffff800`02d913cc : 00000000`0a178300 00000000`00000000 fffff8a0`024e1e01 fffff880`08770aa8 : nt!ObOpenObjectByName+0x306
    fffff880`08770a90 fffff800`02d9389f : 00000000`0057e0c0 00000000`00020019 00000000`0057e148 00000000`00000000 : nt!CmOpenKey+0x28a
    fffff880`08770be0 fffff800`02ac0e93 : fffffa80`0634c060 fffff880`08770ca0 00000000`00000001 00000000`00000000 : nt!NtOpenKeyEx+0xf
    fffff880`08770c20 00000000`7781226a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0057e058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7781226a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!CmpInsertKeyHash+7a
    fffff800`02d927ea 4c895cd310      mov     qword ptr [rbx+rdx*8+10h],r11
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!CmpInsertKeyHash+7a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!CmpInsertKeyHash+7a
    
    BUCKET_ID:  X64_0x50_nt!CmpInsertKeyHash+7a
    for information only, 3rd party drivers listed in the dump:

    ASACPI.sys Mon Mar 28 03:30:36 2005 (42476C4C)
    Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities
    http://www.carrona.org/drivers/driver.php?id=ASACPI.sys

    adpu320.sys Wed Feb 28 00:04:15 2007 (45E4C6FF)
    Adaptec .NET Ultra320 Driver
    http://www.carrona.org/drivers/driver.php?id=adpu320.sys

    mv614x.sys Mon Mar 26 06:53:22 2007 (46075FD2)

    mv614x.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    nvm62x64.sys Fri Oct 17 22:01:06 2008 (48F8FD12)
    nVidia Ethernet Networking Driver (nForce chipset driver)
    http://www.carrona.org/drivers/driver.php?id=nvm62x64.sys

    dump_a320raid.sys Wed Feb 10 19:12:38 2010 (4B730526)

    dump_a320raid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    a320raid.sys Wed Feb 10 19:12:38 2010 (4B730526)

    a320raid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA)
    AMD storage controller driver - usually from the Windows 7 DVD
    http://www.carrona.org/drivers/driver.php?id=amdxata.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

    MpFilter.sys Fri Aug 24 00:03:14 2012 (5036B6B2)
    Microsoft Windows AntiMalware protection system
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys

    point64.sys Tue Sep 18 11:18:08 2012 (50584A60)
    Microsoft IntelliPoint Filter Driver
    http://www.carrona.org/drivers/driver.php?id=point64.sys

    nvlddmkm.sys Fri Mar 15 01:37:00 2013 (51427B3C)
    nVidia Video drivers
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

  3. The Following User Says Thank You to satrow For This Useful Post:

    jimboba (2013-05-29)

  4. #3
    WS Lounge VIP mrjimphelps's Avatar
    Join Date
    Dec 2009
    Location
    USA
    Posts
    3,407
    Thanks
    447
    Thanked 405 Times in 377 Posts
    Quote Originally Posted by jimboba View Post
    051613-41059-01.zip

    This is Win 7 64bit OS and this BSOD comes up very occasionally.
    All programmes on this OS are at a minimum.
    Your opinion much appreciated as too what is the cause......
    Jim
    Also, check to see if you have an overheating problem in the computer. If you do have an overheating problem, you'ld likely see the BSOD more often than you are seeing it. Nevertheless, it's worth checking.

    An easy way to check it is by using Speedfan.

  5. The Following User Says Thank You to mrjimphelps For This Useful Post:

    jimboba (2013-05-29)

  6. #4
    Lounger
    Join Date
    Dec 2009
    Location
    Somerset
    Posts
    26
    Thanks
    3
    Thanked 0 Times in 0 Posts
    Sorry for the delay in reply, have been to the US for a holiday!!
    Have updated the ASACPI.sys only at the mo.
    I will do one driver at a time.
    The Nvidea Package will only let me update the Ethernet drivers!
    Which assumes that the drivers installed are already newer than theirs?
    The adaptec 3920 Driver is there only one for this Card.
    Will let you know what happens.
    Thanks for your input to date.
    Regards
    Jim

  7. #5
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Re the nForce chipset drivers, yours wouldn't be more recent than theirs, more likely the same version repackaged by the motherboard maker.

    So you really have a SCSI adapter and drives?

  8. The Following User Says Thank You to satrow For This Useful Post:

    jimboba (2013-05-29)

  9. #6
    Lounger
    Join Date
    Dec 2009
    Location
    Somerset
    Posts
    26
    Thanks
    3
    Thanked 0 Times in 0 Posts
    Yes, the drives are Seagate 4 x ST37355LW's in Raid 0. The drive OS's are XP 32 bit, Vista 32bit, Win7 32bit and Win7 64 bit.
    All the other OS's are fine, so this is some driver issue I suspect. As this 64bit is running ok at the mo I will leave it as the default.
    Will let you know if it goes again!
    Thanks
    Jim

  10. #7
    Lounger
    Join Date
    Dec 2009
    Location
    Somerset
    Posts
    26
    Thanks
    3
    Thanked 0 Times in 0 Posts
    ...also to note that the ASACPI.sys driver in win7 32 bit is the 2009 version, but in Win7 64bit it was 2004 version!
    Makes me feel very hopeful.
    Jim

  11. #8
    Lounger
    Join Date
    Dec 2009
    Location
    Somerset
    Posts
    26
    Thanks
    3
    Thanked 0 Times in 0 Posts
    sadly..a bit short lived. BSOD came up is shown as the fault caused by Acpi.sys driver!
    The driver you sent me said it was not 64bit compatible so I downloaded and installed the only update from Asus.
    Is there a 64bit compatible driver?
    I can zip the BSOD files and send them if you like.
    Thanks
    Jim

  12. #9
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Yes, zip and attach the dumps, Jim.

  13. #10
    Lounger
    Join Date
    Dec 2009
    Location
    Somerset
    Posts
    26
    Thanks
    3
    Thanked 0 Times in 0 Posts

    Further BSOD dmp files

    Here is the two latest files
    Thanks
    Jim
    Attached Files Attached Files

  14. #11
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    The Asacpi.sys driver looks fine now, 2009 - the best you can hope for.

    The 0x50 BSODs all look close to identical, now that the known bad driver is eliminated, update the 2007/2008 Adaptec/Marvell drivers next.

    Svchost is the running process in all 3 crashes, it may be a bad Windows Service causing it, or bad hardware allied to that Service - if only we knew which Service.

    Antivirus interference is also a possibility, uninstall ESET (I've seen it blamed in a number of BSODs elsewhere), also use the removal tool here http://kb.eset.com/esetkb/index?page...&id=SOLN2788#t then install MSE during testing: http://windows.microsoft.com/en-US/w...tials-download

    These may be down to hardware problems - disk/paging file errors, memory errors (RAM, GPU memory, CPU cache) or an old or bad BIOS version. Hardware diags here: http://www.carrona.org/diag.html

    WinDbg Help File Entry:

    The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.
    Parameters

    The following parameters are displayed on the blue screen.
    Parameter Description
    1 Memory address referenced
    2 0: Read operation

    1: Write operation

    3 Address that referenced memory (if known)
    4 Reserved

    If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.
    Cause

    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

    Another common cause is the installation of a faulty system service.

    Antivirus software can also trigger this error, as can a corrupted NTFS volume.
    Resolving the Problem

    Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

    Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

    Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

    Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

    Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.
    Comments

    Typically, this address is in freed memory or is simply invalid.

    This cannot be protected by a try - except handler it can only be protected by a probe.

Posting Permissions

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