Как правило, ошибки devAMD64.exe возникают в результате повреждения, заражения или отсутствия исполняемого файла и обычно наблюдаются во время запуска Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver. Как правило, решить проблему можно заменой файла EXE. Если ошибка devAMD64.exe возникла в результате его удаления по причине заражения вредоносным ПО, мы рекомендуем запустить сканирование реестра, чтобы очистить все недействительные ссылки на пути к файлам, созданные вредоносной программой.
Формат Windows Executable File с расширением файла EXE классифицируют в качестве Исполнимые файлы. Ниже представлен список самых последних версий файлов практически для всех версий Windows (а также для некоторых %%os%%), которые вы также можете скачать. Если у нас нет необходимой копии версии devAMD64.exe, вы можете просто нажать кнопку Request (Запрос), чтобы её запросить. В нашей обширной базе представлены не все версии файлов; в этом случае вам следует обратиться к Dell Inc..
Правильное расположение файла devAMD64.exe является решающим фактором в успешном устранении ошибок подобного рода. Однако, не будет лишним выполнить быструю проверку. Мы рекомендуем повторно запустить Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver для проверки того, возникает ли проблема.
devAMD64.exe Описание файла | |
---|---|
Расширение файла: | EXE |
Категория: | Drivers |
Софт: | Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver |
Версия программного обеспечения: | 12.0.0.448 |
Разработчик: | Dell Inc. |
File: | devAMD64.exe |
Размер (в байтах): | 70144 |
SHA-1: | 6651103fca002687bf93a1be47794f1ad3296781 |
MD5: | 1a5c0bcd6530c64cd452e14463a3e003 |
CRC32: | ba0037b9 |
Продукт Solvusoft
Загрузка
WinThruster 2023 — Сканировать ваш компьютер на наличие ошибок реестра в devAMD64.exe
Windows
11/10/8/7/Vista/XP
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
EXE
devAMD64.exe
Идентификатор статьи: 556206
DevAMD64.exe
Имя | Контрольная сумма MD5 | Размер | Загрузить | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
+ devAMD64.exe | 1a5c0bcd6530c64cd452e14463a3e003 | 68.50 KB | ||||||||||||||||
|
||||||||||||||||||
+ devAMD64.exe | 1a5c0bcd6530c64cd452e14463a3e003 | 68.50 KB | ||||||||||||||||
|
||||||||||||||||||
+ devAMD64.exe | 1a5c0bcd6530c64cd452e14463a3e003 | 68.50 KB | ||||||||||||||||
|
||||||||||||||||||
+ devAMD64.exe | 1a5c0bcd6530c64cd452e14463a3e003 | 68.50 KB | ||||||||||||||||
|
Классические проблемы DevAMD64.exe
Общие проблемы devAMD64.exe, возникающие с Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver:
- «Ошибка DevAMD64.exe. «
- «Ошибка программного обеспечения Win32: devAMD64.exe»
- «DevAMD64.exe должен быть закрыт. «
- «К сожалению, мы не можем найти devAMD64.exe. «
- «DevAMD64.exe не найден.»
- «Проблема при запуске приложения: devAMD64.exe. «
- «DevAMD64.exe не выполняется. «
- «DevAMD64.exe остановлен. «
- «Ошибка в пути к программному обеспечению: devAMD64.exe. «
Ошибки DevAMD64.exe EXE возникают во время установки Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver, при запуске приложений, связанных с DevAMD64.exe (Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver), во время запуска или завершения работы или во время установки ОС Windows. При появлении ошибки devAMD64.exe запишите вхождения для устранения неполадок Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver и чтобы HelpDell Inc. найти причину.
DevAMD64.exe Истоки проблем
Проблемы DevAMD64.exe могут быть отнесены к поврежденным или отсутствующим файлам, содержащим ошибки записям реестра, связанным с DevAMD64.exe, или к вирусам / вредоносному ПО.
Особенно ошибки devAMD64.exe проистекают из:
- Недопустимая (поврежденная) запись реестра devAMD64.exe.
- Вредоносные программы заразили devAMD64.exe, создавая повреждение.
- Вредоносное удаление (или ошибка) devAMD64.exe другим приложением (не Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver).
- Другое приложение, конфликтующее с devAMD64.exe или другими общими ссылками.
- Поврежденная установка или загрузка Qualcomm QCA61x4A QCA9377 WI-FI and Bluetooth Driver (devAMD64.exe).
Updated March 2023: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
- Download and install the repair tool here.
- Let it scan your computer.
- The tool will then repair your computer.
devamd64.exe is a part of Microsoft® Windows® Operating System program developed by MicrosoftCorporation.Some applications or games may need this file to work properly. If devamd64.exe is error, whenever you start the application/game you may experience various kinds of errors. To fix those errors, please read the Recommended Solution below:
- Company: MicrosoftCorporation
- Product: MicrosoftWindowsOperatingSystem
- Version: 5.2.3790.1812
- MD5: not found
- Size: 70144.00 Byte
Is devamd64.exe a virus
The legit devamd64.exe process is located in the c: \programfiles \airties \air2410 \ folder. If it is located elsewhere, it could be malware as a virus can have any name. Some virus can pretend to be devamd64.exe and reside in the Windows or the System32 folder. One way to confirm would be to right-click on the file and use anti-virus software to scan it — download anti-virus here
What is devamd64.exe is error mean?
There are multiple reasons that may cause devamd64.exe errors. These include Windows registry issues, malicious software, faulty applications, etc.Error messages related to the devamd64.exe file can also indicate that the file has been incorrectly installed, corrupted or removed.
Other common devamd64.exe errors include:
- “devamd64.exe is missing”
- “devamd64.exe error loading”
- “devamd64.exe crash”
- “devamd64.exe was not found”
- “devamd64.exe could not be located”
- “devamd64.exe Access Violation”
- “The procedure entry point devamd64.exe error”
- “Cannot find devamd64.exe”
- “Cannot register devamd64.exe”
Recommended Solution to Fix devamd64.exe error
To quickly resolve your problem, we recommend download and use devamd64.exe Fix Tool,this tool perform a scan for devamd64.exe issues and other system errors. It will also check if all .dll and .exe files are registered in the system and scan for other issues that may be preventing system from working properly. After the scan process, it will allow you to repair the errors.
Step 1: Click the “Download Here” button to get an automatic tool.
Step 2: Install the utility by following simple installation instructions.
Step 3: Launch the program to fix your devamd64.exe errors and other issues.
Download Fix Tool to Remove devamd64.exe Error
Contents
- 1. What is devamd64.exe?
- 2. Is devamd64.exe safe, or is it a virus or malware?
- 3. Can I remove or delete devamd64.exe?
- 4. Common devamd64.exe error messages
- 5. How to fix devamd64.exe
- 6. September 2023 Update
- 7. Download or reinstall devamd64.exe
Updated September 2023: Here are three steps to using a repair tool to fix exe problems on your computer: Get it at this link
- Download and install this software.
- Scan your computer for exe problems.
- Repair the exe errors with software tool
devamd64.exe is an executable file that is part of Microsoft® Windows® Operating System developed by Microsoft Corporation. The Windows 7 version of the software: 5.2.3790.1812 is usually about 70144 bytes in size, but the version you have may differ.
The .exe extension of a file name displays an executable file. In some cases, executable files can damage your computer. Please read the following to decide for yourself whether the devamd64.exe file on your computer is a virus or malware that you should delete, or if in fact it is a valid Windows operating system file or reliable application.
Recommended: Identify devamd64.exe related errors
(optional offer for Fortect)
Is devamd64.exe safe, or is it a virus or malware?
The first thing that will help you determine if a particular file is a legitimate Windows process or a virus, is the location of the executable itself. With devamd64.exe for example, it’s path will probably be something like C:\Program Files\Microsoft Corporation\Microsoft® Windows® Operating System\devamd64.exe
To determine it’s path, open Task Manager, go to View -> Select Columns and select «Image Path Name» to add a location column to your Task Manager. If you find a suspicious directory here, it may be a good idea to investigate this process further.
Another tool that can sometimes help you detect bad processes is Microsoft’s Process Explorer. Start the program (it does not require installation) and activate «Check Legends» under Options. Now go to View -> Select Columns and add «Verified Signer» as one of the columns.
If the «Verified Signer» status of a process is listed as «Unable to Verify», you should take a moment look at the process. Not all good Windows processes have a Verified Signature label, but neither do any of the bad ones.
The most important facts about devamd64.exe:
- Name: devamd64.exe
- Software: Microsoft® Windows® Operating System
- Publisher: Microsoft Corporation
- Expected Location: C:\Program Files\Microsoft Corporation\Microsoft® Windows® Operating System\ subfolder
- Expected Full Path: C:\Program Files\Microsoft Corporation\Microsoft® Windows® Operating System\devamd64.exe
- SHA1: 6651103fca002687bf93a1be47794f1ad3296781
- SHA256: 8eccf47482df3d8d0497b8b4f82e7c631b56ef8198a4cef1d21a58399482529c
- MD5: 1a5c0bcd6530c64cd452e14463a3e003
- Known to be up to 70144 bytes in size on most Windows;
If you had any difficulties with this executable, you should determine if it’s trustworthy before deleting devamd64.exe. To do this, find this process in Task Manager.
Find its location and compare the size etc with the above facts.
If you suspect that you may be infected with a virus, then you must attempt to fix it immediately. To delete the devamd64.exe virus, you must download and install a full security application like this. Note that not all tools can detect every type of malware, so you may need to try several options before you’re successful.
In addition, the functionality of the virus may itself affect the deletion of devamd64.exe. In this case, you must enable Safe Mode with Networking — a secure environment that disables most processes and loads only the most required services and drivers. When there, you can run a security program and a complete system analysis.
Can I remove or delete devamd64.exe?
You should not delete a safe executable file without a valid reason, as this may affect the performance of any associated programs that use that file. Be sure to keep your software and programs up to date to avoid future problems caused by corrupted files. With regard to software functionality issues, check driver and software updates more often, so there is little or no risk of such problems occurring.
The best diagnosis for these suspicious files is a complete system analysis with either ASR Pro or this antivirus and malware remover. If the file is classified as malicious, these applications will also delete devamd64.exe and get rid of the associated malware.
However, if it is not a virus and you need to delete devamd64.exe, then you can uninstall Microsoft® Windows® Operating System from your computer using its uninstaller. If you cannot find it’s uninstaller, then you may need to uninstall Microsoft® Windows® Operating System to completely delete devamd64.exe. You can use the Add/Remove Program function in the Windows Control Panel.
-
1. In the Start menu (for Windows 8, right-click the screen’s bottom-left corner), click Control Panel, and then under Programs:
o Windows Vista/7/8.1/10: Click Uninstall a Program.
o Windows XP: Click Add or Remove Programs.
- 2. When you find the program Microsoft® Windows® Operating System, click it, and then:
o Windows Vista/7/8.1/10: Click Uninstall.
o Windows XP: Click the Remove or Change/Remove tab (to the right of the program).
- 3. Follow the prompts to remove Microsoft® Windows® Operating System.
Common devamd64.exe error messages
The most common devamd64.exe errors that can appear are:
• «devamd64.exe Application Error.»
• «devamd64.exe failed.»
• «devamd64.exe has encountered a problem and needs to close. We are sorry for the inconvenience.»
• «devamd64.exe is not a valid Win32 application.»
• «devamd64.exe is not running.»
• «devamd64.exe not found.»
• «Cannot find devamd64.exe.»
• «Error starting program: devamd64.exe.»
• «Faulting Application Path: devamd64.exe.»
These .exe error messages can occur during the installation of a program, during the execution of it’s associate software program, Microsoft® Windows® Operating System, during the startup or shutdown of Windows, or even during the installation of the Windows operating system. Keeping a record of when and where your devamd64.exe error occurs is important information when it comes to troubleshooting.
How to fix devamd64.exe
A clean and tidy computer is one of the best ways to avoid problems with devamd64.exe. This means performing malware scans, cleaning your hard disk with cleanmgr and sfc /scannow, uninstalling programs you no longer need, monitoring any auto-start programs (with msconfig), and enabling automatic Windows updates. Don’t forget to always make regular backups or at least define recovery points.
If you have a bigger problem, try to remember the last thing you did or the last thing you installed before the problem. Use the resmon command to identify the processes that are causing your problem. Even in case of serious problems, instead of reinstalling Windows, you should try to repair your installation or, in the case of Windows 8, by executing the command DISM.exe /Online /Cleanup-image /Restorehealth. This allows you to repair the operating system without data loss.
To help you analyze the devamd64.exe process on your computer, you may find the following programs useful: Security Task Manager displays all Windows tasks running, including built-in hidden processes such as keyboard and browser monitoring or auto-start entries. A single security risk rating indicates the probability that it is spyware, malware or a potential Trojan horse. This anti-virus detects and removes spyware, adware, Trojans, keyloggers, malware and trackers from your hard disk.
Updated September 2023:
We recommend you try using this new tool. It fixes a wide range of computer errors, as well as protecting against things like file loss, malware, hardware failures and optimizes your PC for maximum performance. It fixed our PC quicker than doing it manually:
- Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
- Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
- Step 3 : Click “Repair All” to fix all issues.
(optional offer for Fortect)
Download or reinstall devamd64.exe
It is not recommended to download replacement exe files from any download sites, as these may themselves contain viruses etc. If you need to download or reinstall devamd64.exe, then we recommend that you reinstall the main application associated with it Microsoft® Windows® Operating System.
Operating system information
devamd64.exe errors can occur in any of the following Microsoft Windows operating systems:
- Windows 10
- Windows 8.1
- Windows 7
- Windows Vista
- Windows XP
- Windows ME
- Windows 200
-
Forums
-
Microsoft Windows Boards
-
Windows 7
You should upgrade or use an alternative browser.
Can’t figure out what this error code means and how to fix it.
-
Thread starterDrakeMcLain
-
Start date
-
#1
DrakeMcLain
C:\\Windows\system32\config\SYSTEM~1\AppData\Local\Temp\{1E9BBF75-A463-4802-94AD-8517ECE12C4D}\{4BAE4C76-44C3-418F-B715-6BBF5A65323E}\devAMD64.exe , C:\temp\devAMD64.exe
I installed a PCI Network Adapter to the motherboard and have been trying to install the drivers for the PCI but I keep getting meet with this (Bold letters) error code. This is my first attempt at building a PC and its all off of old parts, the newest part has to be this PCI cause the one i had wasnt working. Can someone help and tell me how to fix this. Here is the name of the PCI too
TP-Link 300mbps Wireless N PCI Adapter
Model No. : TL-WN851ND
Continue reading…
Similar threads
-
Forums
-
Microsoft Windows Boards
-
Windows 7
-
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
You should upgrade or use an alternative browser.
-
#1
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#2
that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#4
-
- Jun 29, 2017
-
- 7,978
-
- 1,572
-
- 41,590
-
#5
@PC Tailor can you look at that for me? Gardenman is getting too many errors off the dumps
Just give me a couple minutes my friend.
I think there are a lot of changes happening in the background, I would too be getting Symbol errors, but I’ve found a solution on my end for all the symbol errors, but it also means I’ve had to remove any link to a local cache of symbols, meaning the debug takes a little bit longer than one would usually like!
-
- Jun 29, 2017
-
- 7,978
-
- 1,572
-
- 41,590
-
#6
I have run the report and you can see the full report here: https://pste.eu/p/2Qhm.html
Summary of Findings:
BugCheck 3B, {c0000005, fffffa443ebd49c3, ffffa583525fe470, 0}
* Kernel symbols are WRONG. Please fix symbols to do analysis.SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Unable to identify faulting module
- If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
- Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
- Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
- If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
Some things to consider:
- The summary above will have some general tips
- I believe there is an updated BIOS (10/07/18) available for your MB: Link
- If I am not mistaken, I noticed you are using 2 different packs of RAM (mixed modules not from the same pack) this can be an easy cause for BSOD and corruption
- Are you running any overclock at all? It may be worth resetting your BIOS to ensure all overclocks are removed first (RAM is running at 2400 for example).
- MSI Afterburner can cause BSOD in some settings
- You’ll also want to ensure that your Intel Management Engine driver is also updated with your BIOS, as these 2 should be «aligned».
- You’ll also want to check if your Broadcom wireless driver is up to date as this can cause common BSOD errors too.
- As a final note, due to the corruption found, a memtest may be necessary, but wait for @Colif to feedback.
-
#7
Right well despite many looks, I had a multitude of symbol errors too, which might indicate some corruption. However I think I have been able to do enough to get a reasonable report out.I have run the report and you can see the full report here: https://pste.eu/p/2Qhm.html
Summary of Findings:
Some things to consider:
- The summary above will have some general tips
- I believe there is an updated BIOS (10/07/18) available for your MB: Link
- If I am not mistaken, I noticed you are using 2 different packs of RAM (mixed modules not from the same pack) this can be an easy cause for BSOD and corruption
- Are you running any overclock at all? It may be worth resetting your BIOS to ensure all overclocks are removed first (RAM is running at 2400 for example).
- MSI Afterburner can cause BSOD in some settings
- You’ll also want to ensure that your Intel Management Engine driver is also updated with your BIOS, as these 2 should be «aligned».
- You’ll also want to check if your Broadcom wireless driver is up to date as this can cause common BSOD errors too.
- As a final note, due to the corruption found, a memtest may be necessary, but wait for @Colif to feedback.
I did just update bios still nothing.
I am using mixed memory unfortunately
I’m not sure but I got my i5-7600k our the box and was already overclocked to 4.2ghz and bios reads normal
I don’t even have afterburner installed
I updated the intel management driver and still
And the Broadcom is the latest driver for my network adapter not sure if there’s much I can do there
I already did memtest and said it’s was fine but I’ll check again
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#8
What make/model is the wifi adapter as the 2014 drivers are likely rebadged Win 7 drivers.
Wifi adapters are one thing that has been tripping people over all year, older ones that were released with Win 7 are unlikely to actually have win 10 drivers. MIght be time to get a new one, I would aim for one that supports latest Wifi version (802.11ac or higher) as its less likely to have win XP drivers which I use to tell how old an adapter really is.
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#10
see if this works
Alright, so to help you, I’ll put as clear of a path as possible that I took. It’s taken me 3 hours to work this out for myself. I also have Windows 10 64Bit and bought this card and had tons of problems getting it installed.
- Download and install latest drivers from TP-Link’s website for Archer T6E Windows 10.
- Extract and Install the ‘Setup.exe’ (I ran this in Windows 8 Compatibility Mode as an Administrator)
- Locate «SetupController_Log.txt» in C:\ProgramData\TP-Link\
- Locate line similar to «17:44:26: OS is 64-bit. g_bvIsOS64 = TRUE, g_szWINSYSDIR = C:\WINDOWS\system32\, g_szDevcon = C:\Users\Brian\AppData\Local\Temp\{84CF8374-E9D9-4487-9619-E2C723DE617C}\{2716E9BF-1A34-45DE-B657-541F4AED9858}\devAMD64.exe»
- I suggest following the directions on TP-Link’s website for the Windows 8 Manual Install of the driver. When it states to look for the *.INF, direct the installer to the same location as the temp folder in step 4. For me it was «C:\Users\Brian\AppData\Local\Temp\{84CF8374-E9D9-4487-9619-E2C723DE617C}\{2716E9BF-1A34-45DE-B657-541F4AED9858}\»
- This should locate the proper drivers for the card and allow you to properly install and use the card.
I’d love to have someone confirm this works for them.
https://forums.tomshardware.com/threads/tp-link-archer-ac1300-not-recognised-by-pc.2655741/
i know your card is seen, it might help though. Seems latest drivers are from 2015
-
#14
-
- Jun 29, 2017
-
- 7,978
-
- 1,572
-
- 41,590
-
#15
Summary of findings:
BugCheck 192, {ffffe6046c9dc080, ffffe6046c203b88, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquirePushLockExclusiveEx+145 )KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.Arguments:
Arg1: ffffe6046c9dc080, The address of the thread.
Arg2: ffffe6046c203b88, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.Technical Cause:
The caller cannot be blocking on a lock above APC_LEVEL because the lock may be held exclusively by the interrupted thread, which would cause a deadlock.PROCESS_NAME: Spotify.exe
MODULE_NAME:nt
IMAGE_NAME: ntkrnlmp.exe
This is a less common bugcheck from my experience. The obvious difference in thirs aprty drivers is Norton being present during this.
Is any overclock being used anywhere at all? I noticed XTU and more, so you’ll want to ensure all OC is removed first.
I will also wait, my initial post stated how the mixed modules can cause problems, so this could well still be the cause.
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#16
so im using one of my sticks of ram and havent got any crashes im gonna run my pc all day to see if thats it if so im gonna need to my a dual channel ram set
I was about to suggest this. My bad for not noticing ram modules weren’t the same, not used to reading PC tailors reports, used to the layout of gardenmans…
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors
as my 1st response to weird errors is check ram
-
#17
ive been running my pc with 1 stick of ram from both of them and it hasnt crashed once
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#18
Well this error in Windows is not common and if you are facing this error then there are two main reasons as to why you are seeing this error. One being Bluetooth drivers and other is your wireless adapter.
https://troubleshooter.xyz/wiki/fix-kernel-auto-boost-lock-acquisition-windows-10/
there isn’t a great time difference between these 2, I was expecting the Dec 2015 drivers to be a little newer than that?
Old
bcmwl63a.sys | 06/02/2014, 09:57:28 | Broadcom | Broadcom Wireless Network Adapter |
New
bcmwl63a.sys | 2/5/2014, 10:25:42 AM | Broadcom | Broadcom Wireless Network Adapter |
So they could still be the cause
So can you run using Ethernet cable rather than WIfi and remove adapter and see if you still get bsod?
there is an alternative, you can read the 2nd thread in this post and run driver verifier and see what Microsoft shows is cause — https://forums.tomshardware.com/thr…nclude-in-blue-screen-of-death-posts.3468965/
-
#19
I wonder if its a coincidence the 1st fix here is remove wireless Adapter drivershttps://troubleshooter.xyz/wiki/fix-kernel-auto-boost-lock-acquisition-windows-10/
there isn’t a great time difference between these 2, I was expecting the Dec 2015 drivers to be a little newer than that?
Old
bcmwl63a.sys 06/02/2014, 09:57:28 Broadcom Broadcom Wireless Network Adapter New
bcmwl63a.sys 2/5/2014, 10:25:42 AM Broadcom Broadcom Wireless Network Adapter So they could still be the cause
So can you run using Ethernet cable rather than WIfi and remove adapter and see if you still get bsod?
there is an alternative, you can read the 2nd thread in this post and run driver verifier and see what Microsoft shows is cause — https://forums.tomshardware.com/thr…nclude-in-blue-screen-of-death-posts.3468965/
i dont really have access to my ethernet so i use wireless so i tried the other option which is my ram and i havent gotten a single error yet so i might have to order dual channel matched sets and not individual.
-
#20
https://db.tt/OsRN7ZLYDQ
Could dual channel have something to do with this?
Last edited:
-
#21
Specs:
Msi z270 a-pro
i5-7600k
EVGA Geforce GTX 1060 6gb
16 gb ram
-
- Oct 7, 2009
-
- 51,285
-
- 4,093
-
- 173,390
-
#22
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS: which version of the OS
Are you on the latest BIOS update for your motherboard?
-
- Jun 12, 2015
-
- 62,819
-
- 5,625
-
- 168,090
-
#23
merged
I saw your dump in here earlier but I was waiting for PC tailor to convert it
-
- Jun 29, 2017
-
- 7,978
-
- 1,572
-
- 41,590
-
#24
Summary of findings:
BugCheck 3B, {c0000005, ffffb960c01d4d40, ffffca037fdc6b50, 0}
Probably caused by : win32kbase.sys ( win32kbase!W32GetThreadWin32Thread+2c )SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)
Usually caused by drivers.PROCESS_NAME: svchost.exe
MODULE_NAME:win32kbase
IMAGE_NAME: win32kbase.sys
This is typically caused by drivers. Some things to consider:
- I could not verify BIOS information, you may find an update for this.
- You should also verify your Intel Management Engine driver is up to date with your BIOS as these 2 should be aligned.
- I am not aware of normal integrity (stability) of cfosspeed6.sys
- I am not aware of normal integrity (stability) of semav6msr64.sys and could not identify it
- You may want to remove MSI Afterburner as this can cause BSOD.
- You can disable drivers using Autoruns without uninstalling them as a test.
- Should all else fail, driver verifier may need to be used.
Await further feedback from others.
-
#25
Similar threads
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions