BSOD when in Skype video call

[Jake0Kulp]

BSOD while in game (Fallout:NV)

Hey, I've been recently encountering some rude disconnectedness during most of my Skype calls. Over the past few weeks I've had about 6 BSOD's and 4 of them occurred while in a Skype video call. The other two were video driver related and haven't occurred since (from what I believe)

Just a warning that I'm not extremely good with Tech vocabulary so dumbing it down a bit will be appreciated.

 

[cipley]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1200007, 2, 1, fffff8800511483e}

Unable to load image \SystemRoot\system32\drivers\cmudaxp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
Probably caused by : cmudaxp.sys ( cmudaxp+5983e )

Followup: MachineOwner
---------

cmudaxp.sys looks like refers to your ASUS Xonar DG Audio Device

-------------
Sound Devices
-------------
            Description: Speakers (ASUS Xonar DG Audio Device)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_13F6&DEV_8788&SUBSYS_84671043&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: cmudaxp.sys
         [B][COLOR="Red"]Driver Version: 5.12.0001.0008 (English)[/COLOR][/B]
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          [B][COLOR="red"]Date and Size: 3/10/2011[/COLOR][/B] 03:44:16, 2725376 bytes
            Other Files: 
        Driver Provider: ASUSTeK
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Latest version is Version 7.12.8.1794
Should update those: ASUSTeK driver download page

 

[koolkat77]

In addition to the above:

Overclocking

If you are overclocking any hardware, STOP. Reset any changed values back to default.

[B]Start Menu\Programs\ASUS	Public:Start Menu\Programs\ASUS	Public
Start Menu\Programs\ASUS\AI Suite II	Public:Start Menu\Programs\ASUS\AI Suite II	Public
Start Menu\Programs\ASUS Xonar DG Audio	Public:Start Menu\Programs\ASUS Xonar DG Audio	Public[/B]

This is overclocking software and can lead to system instability and BSOD's. Please reset all components to their stock speeds and then remove the software.

[B]Start Menu\Programs\avast! Free Antivirus	Public:Start Menu\Programs\avast! Free Antivirus	Public
Start Menu\Programs\AVG	Public:Start Menu\Programs\AVG	Public[/B]

Security App

Running two antivirus software is never a good idea. Remove Avast! and AVG and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

   Information

DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
2. Disk check for errors on the hard drive - http://www.sevenforums.com/tutorials/433-disk-check.html
3. Troubleshoot applications by a clean boot - http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
4. Memtest86+ paying close attention to part 3 - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Hope this helps for now, good luck.

 

[Jake0Kulp]

More issues D:

Hey there guys, I've been going along fine for a while now but have recently encoutered a couple crashes that I've logged for you and need someone to take a look at, thanks!

EDIT:
Crashed once more, please I would like some help with this, it's getting a bit bothersome :/
This crash was NOT while playing Fallout so I believe it may be from something else.

 

[Jake0Kulp]

Hey guys no good signs since my recent post, only two more crashes, and those were complete freezes. Need help ASAP!

 

[koolkat77]

Have you followed anything from post 3.

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

   Tip

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80103b8028, f2000040, 10005}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80103b8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

1: kd> !errrec fffffa80103b8028
===============================================================================
Common Platform Error Record @ fffffa80103b8028
-------------------------------------------------------------------------------
Record Id     : 01ce67b6b7380e08
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/13/2013 23:58:13 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80103b80a8
Section       @ fffffa80103b8180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80103b80f0
Section       @ fffffa80103b8240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : a9 06 03 00 00 08 10 02 - bf e3 9a 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80103b8138
Section       @ fffffa80103b8280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 1 Bank 0)
  Status      : 0xf200004000010005