BSOD - Win7 - Usually when running several programs

Discussion in 'Software' started by saabinmash, Jul 7, 2011.

  1. saabinmash

    saabinmash Private E-2

    Windows 7 Home Premium 64bit
    Intel Core2 Quad CPU Q9550 @ 2.83GHc
    4 GB RAM
    NVIDIA GeForce GTX 260

    I have attached the dump. if anyone here can help me interpret them, that would be very appreciated!
     

    Attached Files:

  2. satrow

    satrow Major Geek Extraordinaire

    ASACPI.sys: part of several Asus utilities, a known cause of BSOD's in W7, uninstall it or update the utilities to the latest version(s).

    PxHlpa64.sys: Sonic DVD driver, update or uninstall. <- flagged as a cause.

    lvrs64.sys: Logitech camera driver, update or uninstall. <- flagged as a cause.

    Fix those and test until you get a new BSOD ;)
     
  3. saabinmash

    saabinmash Private E-2

    I updated the Logitech camera driver, which was really old.

    I also updated the firmware for my Pioneer DVD-RW, I'm not sure what you mean by Sonic DVD. The firmware update wasn't a huge one.

    I've yet to update utilities, I don't know how. I know Asus has an updater but it doesn't seem to work after i install it, it's just a blank image where the normal buttons and options would be overlayed. I found some tutorials on upgrading the BIOS itself for ASUS, but nothing about the utilities, i'm not sure if it's the same.
     
  4. augiedoggie

    augiedoggie The Canadian Loon - LocoAugie (R.I.P. 2012)

    Personally speaking, I would never update the BIOS unless my specific issue was addressed in the change logs on the ASUS site. They're pretty good about updates but their servers suck big time. Try later.
     
  5. saabinmash

    saabinmash Private E-2

    I wish I had read that before I did it. I used the AsusUpdate application.

    Now even though it boots up eventually, I get a checksum error on bootup. [​IMG] It looks exactly like this.

    I've never had this happen before. Do you have any suggestions on where to proceed from here?
     
  6. thisisu

    thisisu Malware Consultant

    The CMOS battery is most likely going bad

    CMOS battery looks like this
    [​IMG]

    You could try going into the BIOs, setting the correct Time/Date, reboot, see if it continues to show you this message.

    They are very cheap, about 4$ in a retail store. If you're not comfortable with installing it, labor should be ~10$.
     
  7. augiedoggie

    augiedoggie The Canadian Loon - LocoAugie (R.I.P. 2012)

    Ya, just about every megamart stocks them these days. #CR2032 They only last some 3 years according to an Intel study. If that's not it(I hope it is) then we move on.
     
  8. thisisu

    thisisu Malware Consultant

    hrm, going through your BSODs logs. Based on the error code alone:

    Those are some notes i have on 0x4e which occured more than 5 times.
    Is the computer taking forever to boot up?
     
  9. augiedoggie

    augiedoggie The Canadian Loon - LocoAugie (R.I.P. 2012)

    Based on what thisisu just said, have you checked your RAM yet? Try running Memtest86 to see how good it is, even 1 error means replacement of that stick.
     
  10. saabinmash

    saabinmash Private E-2

    Other than that first bootup, I get no booth up checksum errors. What gives? How could this have fixed itself (or not)?
     
  11. satrow

    satrow Major Geek Extraordinaire

    From memory, BIOS updating instructions normally carry info to the effect that you should enter the BIOS and set it to defaults after an update. Effectively just entering the BIOS clears the message, which is a valid one because the BIOS itself has changed.

    The Sonic driver, PxHlpa64.sys, is installed with many other softwares, including:
    Please track it down and uninstall or update it.

    Hold off on tracking down and updating the ASUS ASACPI.sys (it might be the driver for the ATK0110 ACPI utility, under System devices in Device manager), on my W7 it's from August 2004, doesn't appear to be causing any problems so I'm leaving it as is.
     
  12. saabinmash

    saabinmash Private E-2

    Alright, well I used ASUS update and updated the BIOS, I also got new drivers for my DVD drive, and I just got another BSOD, this time I have no idea why, it happened in the middle of the night when I was sleeping.

    I had not yet disabled PxHlpa64.sys or ASUS ASACPI.sys or lvrs64.sys

    Are these drivers still flagged as causes? I have disabled PxHlpa64.sys now. Please let me know if it's still flagged as a cause though.

    Attached are the last 3 dumps. Thanks!
     

    Attached Files:

  13. satrow

    satrow Major Geek Extraordinaire

    So, you updated 1 of the 3 drivers I originally pointed to as being at fault/likely to cause BSOD's (1 of which was already flagged as being at fault back in November!); updated firmware and BIOS which you hadn't been asked to.

    Revisit #2 and remove or update the remaining problem drivers/potential problem drivers please.

    Once you've succeeded, download and install DriverSweeper and use it to uninstall your nVidia graphics drivers. Reboot and install the ones from here.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8008d8e320, fffff8800f8bdf10, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+801f10 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8008d8e320, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f8bdf10, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+801f10
    fffff880`0f8bdf10 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02ed9b88 fffff880`02cc2000 : 00000000`00000116 fffffa80`08d8e320 fffff880`0f8bdf10 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`02ed9b90 fffff880`02c95867 : fffff880`0f8bdf10 fffffa80`06ab3000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02ed9bd0 fffff880`02cc1e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`08d8e320 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`02ed9c80 fffff880`02d90ec1 : fffffa80`0776ca10 00000000`00000080 00000000`00000000 fffffa80`06ab2010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`02ed9d00 fffff800`02f7732e : 00000000`046c09c0 fffffa80`06ab08c0 fffffa80`039e99e0 fffffa80`06ab08c0 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`02ed9d40 fffff800`02ccc666 : fffff800`02e4de80 fffffa80`06ab08c0 fffff800`02e5bcc0 fffff880`01239384 : nt!PspSystemThreadStartup+0x5a
    fffff880`02ed9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+801f10
    fffff880`0f8bdf10 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  nvlddmkm+801f10
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
     
  14. saabinmash

    saabinmash Private E-2

    When using DriverSweeper, it asks to clean and analyze Nvidia Chipset, Nvidia Display, and Nvidia PhysX, should I analyze and clean all 3? Are they drivers or groups of drivers?
     
  15. satrow

    satrow Major Geek Extraordinaire

    Display and PhysX only, the chipset is not related to graphics.
     
  16. falconattack

    falconattack Command Sergeant Major

    When you clean the system reboot your machine go into bios and run driver swepper as said here

    How to use ?

    There are two methods to use Driver Sweeper.
    Both methods achieve the same results. This method is always able to clean all files.

    This method will delete remaining files upon reboot (if deleting failed). You can clean your drivers this way:

    Use the official uninstaller(s) of the driver(s) you want to uninstall.
    Reboot your PC in Safe Mode.
    Run Driver Sweeper and select what to clean.
    Analyse lists all the entries possible to remove, cleaning removes the entries selected.
    More drivers can be selected for the same cleaning process.


    It is the best way to clean all leftover items , do it !! :-o
     
  17. saabinmash

    saabinmash Private E-2

    Is it a problem if after uninstalling drivers, and rebooting, Windows automatically installs generic drivers? I suppose being in safe mode with no internet access would prevent that though, I had internet access still.
     
  18. saabinmash

    saabinmash Private E-2

    Ok drivers were removed, then cleaner was used, then the new drivers you linked me to were installed.

    And now we wait?
     
  19. satrow

    satrow Major Geek Extraordinaire

    Don't wait ;) actively use the machine, try to trigger another BSOD.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds