Skype Causes BSOD on login

Similar Questions

• Latest Skype causes Blue Screen of Death

  Whenever I have install/update Skype on windows 7 to the current version, I get a blue screen as I can't use older versions because he says "Skype cannot connect." Any help on any of these questions is accepted. Thank you.

  You have the well known problem of the Webcam HP HD [Fixed] .

  The last 6.16/6.18 Skype are causing BSOD on HP laptops with this installed webcam.

  You can try to uninstall the version 6.18 and install the previous 6.14.0.104 Skype version using the download links provided here:

  http://community.Skype.com/T5/Windows-desktop-client/ASUS-USB2-0-webcam-not-recognized-by-Skype-6-18...

  Be sure to turn off the automatic updates.

  Tools-> Options-> Advanced-> automatic updates-> turn off automatic updates

  The other option is to uninstall the HP drivers and install generic Microsoft webcam drivers.

  http://community.Skype.com/T5/Windows-desktop-client/query-about-BSOD-fix/m-p/3589407#M295633

• Latest Version causes BSOD

  Hi I read posts about 6.18 aheap version is not compatible with the HP webcam not

  It seems I have the same problem

  There were proposals for links to download 6.16, but none of them work

  I spent hours trying to uninstall reinstall etc etc,

  Very frustrating and a waste of my time.

  Please provide me a link to an older version so that I can continue to use Skype.

  Thank you very much

  http://community.Skype.com/T5/Windows-desktop-client/Skype-6-18-update-error-BSOD/m-p/3522835#M29259...

  If your laptop has the webcam HP HD Webcam [Fixed] installed, this may cause BSOD with the latest versions of Skype 6.16/6.14.

  The solution is to uninstall the currently installed version and install Skype 6.14.0.104 version.

  You can use the like posted download link here:

  http://community.Skype.com/T5/Windows-desktop-client/ASUS-USB2-0-webcam-not-recognized-by-Skype-6-18...

  Don't forget to turn off the automatic updates:

  Tools-> Options-> Advanced-> automatic updates-> turn off automatic updates

• Geniune Intel causing BSOD

  MS community,

  I added some hardware from Razer (Blackwidow Ultimate keyboard & DeathAdder mouse) my system, a month or two before, and Synapse 2.0 caused BSOD regularly, so I took out starter, and my system has worked very well, until the last two weeks. I am not usually the addition or removal of hardware or software, so maybe I'm picking up cyber-Carbuncles in surfing on... not sure. In any case the last two .dmp files are on OneDrive: http://1drv.ms/1tpXPpW. I hope one of you very smart people can help me understand what is causing my plant.

  Thank you all in advance!

  Baird

  Original title: BSOD are back...

  WBM

  These 2 are called BCC124 and are related to the material.  Since the real interest is mentioned I would run the cpu stress test first

  I would also remove the app associated with Bus Marvin/MarvinPro MarvinBus.sys from Pinnacle Systems enumerator.  (yours is 2005)

  Try this free stress test: http://www.mersenne.org/freesoft/

  
  Prime95 Setup program;
  -Extract the contents of the zip file into a directory of your choice
  -Double-click on the executable file
  -Select "all stress testing.
  -Select the test of 'Blend '.  If you have already run MemTest overnight, you can run the test of "Small FFFS" instead.
  "Number of threads of torture test run" must equal the number of processors multiplied by 2 (if you use hyperthreading).
  The best way to do this is to go to the Manager of the tasks of the figure... The performance tab - and see the number of boxes that appear under the CPU usage history
  Then run the test of 6 to 24 hours - or until you get errors [b](whichever comes first)
  The selection of Test and the file stress.txt box describes the components that insists on the program.
  Stop 0 x 124 is a hardware error

  If you are overclocking try to reset your settings to standard processor and see if that helps.

  If you keep getting the BSOD here are things more than you may want.
  This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
  
  Stop 0 x 124 - what it means and what to try
  Synopsis:
  A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
  Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.
  

  Generic troubleshooting ' Stop 0 x 124 ":

  1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
  (2) ensure that the machine is sufficiently cooled.
  If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
  3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
  It is best to run the latest drivers anyway.
  (4) update the BIOS of your motherboard according to the manufacturer's instructions and clear CMOS.
  Their website should provide detailed instructions on the brand and model-specific procedure.
  (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
  At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.

  
  6) trying (stress) test these hardware components that can be put to the test artificially.
  The most obvious examples are the RAM and HDD (s).
  For the RAM, use the 3 rd-party memtest86 utility to run several hours a test value. (6-8 passes to stress the ram)
  For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
  Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
  7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
  Who stops working mitigate the problem of the 0 x 124, jump to the next step.
  If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
  Smash back, obviously the latest addition of software may be somehow connected to the root cause.
  If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
  Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
  (8) clean and carefully remove the dust inside the machine.
  Reinstall all memory modules and connectors.
  Use a can of compressed air to clean the RAM DIMM supports as much as possible.
  (9) If all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
  Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

  If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

  
  
  More advanced reading can be found here from a MS MVP IT PRO
  http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/

  

• Skype causes Blue Screen of Death after a while in a call.

  Hello, I am currently having a problem with my Skype where it will make my computer BSOD after a while in a call, it only occurs during Skype calls, not during other communications programs of voice as the voice of steam call and the blue screen is more likely to happen when I'm in Firefox.

  The blue screen error I get is "clock interrupt was not receieved a secondary processor in the time interval allowed."

  Any help would be appreciated.

  I did clean install applicable drivers and even tried to Exchange pieces of equipment (including the negotiation on an old CPU and RAM value) and no change.

  Fortunately, a solution to the problem, which has been swicthing on Google Hangouts. They work much better because there is no decrease in performance, even streaming, has more features and does not cause a blue screen after a couple of hours.

• 7.22 BSOD on Login Win10

  Every time I try to sign in to Skype from 10 to win my PC BSOD and I get this error an attempt was made to run memory not executable asmthub3.sys. But Skype works fine on my laptop to win 10. Any ideas?

  The BSOD is caused by ASMedia USB3.0 eXtensible Host Controller (asmtxhci.sys).

  Try to downgrade the ASMedia driver:

  https://community.Skype.com/T5/Windows-desktop-client/BSOD-every-time-I-log-in-to-Skype/m-p/4304407/...

• Skype, causing the audio crash

  I narrowed down it to just for Skype. When I get a call, if it is call me and someone answer or I pick up a call, within 10 seconds, my Windows Audio Service crashes. I find the updated driver, Skype version updates, Windows updates. Everything. I started Skype, when a call is picked up, it causes the Audio Service from my Windows to stop working and then Skype crashes. I did nothing to my computer it would probably cause. If any additional info is needed, I would be happy to provide it.

  EDIT: Windows 7 Professional

  Try to uninstall the DroidCam application.

• Cannot set up Skype. Freezes on login

  I'm trying to install Skype on a new computer. Windows 7-64.

  The installer crashes when it gets to the connection. I have read several posts that seem similar, but the problem is that I can't see the login screen of the House. I have two computers, a Tablet and a phone. None of them will display the homescreen msn.com or hotmail.com. They switch to whatever is the current "live" domain name, but the page is empty, without any error. I don't have any problem connect from work. Outlook continues to send and receive e-mail from these accounts and Skype account works on the other computer.

  I tried to get support for the e-mail account, but there is no place to report. I spent a few hours looking.

  I wireless now, but not on the same subnet as my wired computers. I guess I had an IP address conflict.

• Skype causes the freezing of the screen when I make a call.

  I read so many subjects of this, everything tried and Skype still causes my screen to freeze, resulting in a reboot when I try to call someone or vice versa. I use the latest version of Skype. I tried different versions, reinstall several times and I do not know what to do now.

  Try to uninstall the currently installed version of Skype and install the previous 6.14.0.104 version by using the download links provided here:

  http://community.Skype.com/T5/Windows-desktop-client/ASUS-USB2-0-webcam-not-recognized-by-Skype-6-18...

  Be sure to turn off the automatic updates:

  Tools-> Options-> Advanced-> automatic updates-> turn off automatic updates

• 32GB SD card update causes BSOD

  The Ko in question is 976422. Once the update has been installed, my system flashes a BSOD then it is trying to start Windows too. It's a such quick flash that I am unable to get information from it. After reboot, I got to start restore. This has happened three times now.

  This time though, my system restore to a restore point while one I had just done. I don't know if the restoration was the cause, but a part that's Avast stop working properly.

  System details:

  OS: Windows 7 Ultimate x 64

  Motherboard: Gigabyte GA-790XTA-UD4

  Well, I put this turned off for a long time, mainly because the servers are running. I ended up uninstalling SDK for Windows Phone 7 development and had the same problem with a BSOD at startup. However, I does not change the option of BSOD in time. Anyway, he has finally (and unfortunately) came down to do a repair installation. Which fixed the problem entirely.

• What causes BSOD? I have the dump file for those interested

  DUMP_HEADER32:
  MajorVersion 0000000f
  MinorVersion 00000 has 28
  DirectoryTableBase 0adc05a0
  PfnDataBase 81 b 46000
  Kernel 8055d 720
  PsActiveProcessHead 805638 b 8
  MachineImageType c 0000014
  NumberProcessors 00000002
  BugCheckCode 10000050
  BugCheckParameter1 e62a7d05
  BugCheckParameter2 00000000
  BugCheckParameter3 bf26e8b7
  BugCheckParameter4 00000001
  PaeEnabled 00000001
  KdDebuggerDataBlock 8054d2e0
  MiniDumpFields 00000dff

  TRIAGE_DUMP32:
  00000300 ServicePackBuild
  SizeOfDump 00010000
  ValidOffset 0000fffc
  ContextOffset 00000320
  ExceptionOffset 000007d0
  MmOffset 00001068
  UnloadedDriversOffset 000010 has 0
  PrcbOffset 00001878
  ProcessOffset 000024c 8
  ThreadOffset 00002728
  CallStackOffset 00002980
  SizeOfCallStack 0000052c
  DriverListOffset 00003140
  DriverCount 00000074
  StringPoolOffset 000053 b 0
  StringPoolSize 00000ff0
  BrokenDriverOffset 00000000
  TriageOptions 00000041
  TopOfStack b5ea9ad4
  DebuggerDataOffset 00002eb0
  DebuggerDataSize 00000290
  DataBlocksOffset 000063 has 0
  DataBlocksCount 00000006

  Windows XP Kernel Version 2600 (Service Pack 3) MP (2 processors) free x 86 compatible

  Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
  The debugging session: Sun May 08 20:00:09 2011
  System Uptime: 0 days 08:59:41
  start end module name
  804 d 7000 806e5000 nt Checksum: 001FA054 Timestamp: Thu Dec 09 05:
  06:55 2010 (4D00D46F)

  Unloaded modules:
  aec31000 aec3e000 DMusic.sys Timestamp: unavailable (00000000)
  aecb1000 aecbf000 c:\windows\system32\drivers\swmidi.sys Timestamp: unavailable (00000000)
  ae1f8000 ae21b000 aec.sys Timestamp: unavailable (00000000)
  ba636000 ba638000 splitter.sys Timestamp: unavailable (00000000)
  b18a8000 b18d3000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b58bd000 b58c9000 cfwids.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b1919000 b1944000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b248a000 b24b5000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b50fe000 b5129000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  ba729000 ba72a000 drmkaud.sys Timestamp: unavailable (00000000)
  b51c9000 b51ec000 aec.sys Timestamp: unavailable (00000000)
  b55e5000 b55f2000 DMusic.sys Timestamp: unavailable (00000000)
  b5675000 b5683000 c:\windows\system32\drivers\swmidi.sys Timestamp: unavailable (00000000)
  ba63c000 ba63e000 splitter.sys Timestamp: unavailable (00000000)
  b5571000 b5595000 mfeavfk01.sy Timestamp: unavailable (00000000)
  b5e0a000 b5e1a000 Serial.SYS Timestamp: unavailable (00000000)
  b58f9000 b590d000 Parport.SYS Timestamp: unavailable (00000000)
  ba1f8000 ba201000 processr.sys Timestamp: unavailable (00000000)
  ba448000 ba44d000 Cdaudio.SYS Timestamp: unavailable (00000000)
  b8ae5000 b8ae8000 Sfloppy.SYS Timestamp: unavailable (00000000)
  ba440000 ba445000 Flpydisk.SYS Timestamp: unavailable (00000000)
  ba438000 ba43f000 Fdc.SYS Timestamp: unavailable (00000000)

  Finish the dump check

  Unfortunately, even after the recent updates and updates the Microsoft Answers forum still does not prompt for any kind of information system when a new question is asked if we know anything about your system.  Not knowing the basic information a problem prolongs the frustration and the agony of these issues.

  Maybe someday the dialog box 'ask a question' forums XP will ask these questions automatically when a new thread is started so I don't have to ask every time.  It might even be possible to solve a problem in a single response when enough information is provided.

  Provide information on your system, the better you can:

  What is your system brand and model?

  What is your Version of XP and the Service Pack?

  Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..

  The afflicted system has a CD/DVD drive work?

  You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?

  If the system works, what do you think might have changed since the last time it did not work properly?

  Can you make the system crash when you want
  ?  For example, you would say that there is no specific system activity that coincides with the accidents (like watching videos, playing games, etc.).

  The next time your system crashes, provide more information on what you see.

  Here's a BSOD example showing information you provide:

  http://TechRepublic.com.com/i/tr/downloads/images/bsod_a.jpg

  Send for the nose and the Red arrows (3 to 4 lines total).

  Send all * line STOP message since there are clues in the 4 parameters.

  If there is a name of the file listed in the STOP message, don't forget to include this information too.

  Ignore the boring text unless it seems important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.
  Download BlueScreenView here:
  http://www.NirSoft.NET/utils/blue_screen_view.html
  Unzip it and run it (BSV installs nothing) and let him complete the digitization of all your crash dump files.
  If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
  BlueScreenView tries to find the right driver or module that caused the blue screen by looking inside the stack of the accident. However, be aware that the driver detection mechanism is not 100% reliable, and you should also look in the lower pane, that display all drivers/modules found in the stack.
  Select (highlight) one or more of the most recent dump files by clicking on them and hold down the CTRL key to select multiple files.  Try to select only the most recent links that relate to your problem (perhaps five or six to start dump files).
  Click on file, save selected items and save information from the dumps to a text file on your desktop called BSOD.txt
  .  Open BSOD.txt with a text editor, copy the text and paste it in your next reply.
  Here's an example of report ASB to a single BSOD I initiated on purpose that indicates the cause of the accident as the pilot i8042prt.sys belonging to Microsoft Corporation:
  ==================================================
  Dump file: Mini062110 - 01.dmp
  Crash time: 21/06/2010-11:51:31
  Bug Check String: MANUALLY_INITIATED_CRASH
  Bug check code: 0x000000e2
  Parameter 1: 0x00000000
  Parameter 2: 0x00000000
  Parameter 3: 0x00000000
  Parameter 4: 0x00000000
  Caused by the driver: i8042prt.sys
  Caused by the address: i8042prt.sys + 27fb
  Description of the file: i8042 Port driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2108)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\minidump\Mini062110-01.dmp
  ==================================================
  Send the information of the last 5 memory dumps (if you don't have 5 memory dumps yet, send the newest, you have).
  While you wait, please follow these steps:
  Perform scans for malware, and then fix any problems:

  Download, install, update and do a full scan with these free malware detection programs:

  Malwarebytes (MMFA): http://malwarebytes.org/

  SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

  They can be uninstalled later if you wish.

  Restart your computer and solve the outstanding issues.

• Diagnosis need help cause BSOD on Windows Server SP2 Standard

  Hello MS community.

  I'm looking for some help determine why my server is suddenly freezing and crashing with increasing frequency.  According to the recommendations on the Blue Screen of Death (BSOD) Wiki, I downloaded a zip file of the .dmp files three more recent crash and MSinfo32 output for information on devices and drivers on the server exposes the problem: http://1drv.ms/1O3KqJ5

  The server is a machine without brand, I had built several years running two processors Intel Xeon processor E5530 2.4 GHz with 20 GB of RAM (previously had 24 GB of RAM, but recently a SIM memory go bad then kidnapped the pair, including the problem without other problems so far).

  Members of the community with diagnostic skills, I would appreciate your help to determine what the cause of the problem, so I can keep from recurring.  The server is a production for my small business machine and I'm a bit over my head on this one.  Thank you!

  Kent

  Auditor will crash the machine when the GIS behave driver is loaded.  Just an info because it's a production machine

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  
  2-Memtest. (You can learn more about running memtest here)

• Receiver Wireless Mobile Mouse 4000 causing BSOD

  It seems to be a growing crowd of users affected by BSOD involving the Microsoft Wireless Mobile Mouses. I, for example, have the WMM4000 on a 32-bit Vista computer. If the receiver is unplugged, instant BSOD (error IRQL-type). Even in this case, at the time, the laptop will hit just the same BSOD error on its own.

  Is there a definitive answer for fixing these mice?

  TGP

  I beg of you.  These related to the SynTP.sys Synaptics Touchpad Driver.  I would like to re - install the latest driver available.

  You also have a driver that is known to cause called c:\windows\system32\drivers\sptd.sys of aft (ALcohol120 or daemon tools).  Which must be removed and replaced.

  Please remove the viewing programs of CD such as Daemon Tools and Alcohol 120%.

  They use a driver, are in your dmp, called c:\windows\system32\drivers\sptd.sys, which is known to cause a BSOD.

  Use this program to uninstall SPTD DuplexSecure
  -Http://www.duplexsecure.com downloads

  When you are finished, you can use this Freeware:

  MagicISO Virtual CD/DVD-ROM (MagicDisc) instead

  http://www.MagicISO.com/download.htm

• Need help cause BSOD

  I have a laptop that is throw random BSOD.

  I have run Chkdsk and memtest and also updated the graphics driver and it's always the case.

  The link below is for a box containing my 10 dumpfiles.  The most recent being the one that took place after the update of the gpu driver.  Any help to decipher what to avoid a reinstall would be greatly apprecoated

  https://www.dropbox.com/sh/yymjrsiblvqwbkk/AADQ--xbOdyR0aU4JHMFt30Ca?DL=0

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Please run first check
  

  If you are overclocking anything reset by default before running these tests.
  In other words STOP!

  If you don't know what it means that you're probably not

  
  

  
  

  
  1-Driver Verifier (for full instructions, see our wiki here)

  2-Memtest. (You can learn more about running memtest here)

  
  

• The game causing BSOD?

  Hello

  I am currently building my own gaming PC. I did all the research I could and brought items that are fully compatible with each other.
  I put all the parts I have currently set, and what I am missing now is a graphics card.
  Course record:
  Motherboard: ASUS P8Z77-M Pro
  CPU: Intel 3rd Gen Core i5 - 3570K (not overclocked)
  RAM: 16 GB Corsair Vengeance DDR3 1600 Mhz (4x4Go)
  Power supply: OCZ 500W ATX power supply
  HARD drive: WD Caviar Blue 500 GB SATAIII
  OS: Windows 7 Home Premium 64-bit
  Right now I use the CPU onboard graphics. These are known as Intel HD Graphics 4000.
  Now the issue I'm having is, I get BSOD everytime I play a game on high graphics settings. I am aware that the graphics on the CPU will not match that of a high-end stand alone the graphics card, and in turn reduce the graphical quality of the game to become more manageable by the CPU.
  However, even when I do that, the game will still crash or BSOD. The games I'm trying to play are MX Simulator (www.mxsimulator.com) and iRacing (www.iracing.com).
  At first, I thought that maybe it was a fault of RAM and so ran the memtest86 to verify my suspicions. This value returned without defects and after you ran the
  trial version on Photoshop CS6 extended, which seems to me to be a whole program of hunger of memory, for the past 3 weeks and not having a BSOD or falls down, I'm almost certain that this is not a memory problem.
  My PC works each routine very well. Browsing the internet, videos YouTube in HD, Microsoft Word, Excel etc. Yet, when it comes of games that it causes the game to not respond or just BSOD.
  I'm hoping that it could be solved by upgrading to a graphics card, but I would like some expert knowledge first on what other issues may cause these errors occur.
  Please, if anyone could help I would be very grateful!
  Thank you very much
  Aster
  PS - I'm not sure where this file in a topic, so I'll add it to the area 'performance and Maintenance '. Also I tried to uninstall and then reinstall the graphics drivers without success to beat the BSOD.

  RB

  Excellent work and because it was I think we have your answer.  These were verified and associated to signed the AsUpIO.sys of ASUSTeK Computer Inc.  Yours is since 2010.  Check with ASUS for an update and although it is not re - install the latest available version.

  You were also running PEUpdater.exe (another utility ASUS) which should be updated from ASUS

  BugCheck C4, {f6, 120, fffffa800df38ab0, fffff88003012766}
  Probably caused by: AsUpIO.sys (AsUpIO + 1766)
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  BugCheck C4, {f6, 120, fffffa8013023870, fffff8800318d766}
  Probably caused by: AsUpIO.sys (AsUpIO + 1766)
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  BugCheck C4, {f6, 120, fffffa8012e12060, fffff880049d5766}
  Probably caused by: AsUpIO.sys (AsUpIO + 1766)