I have been getting BSOD on my Alienware 15 r3 that happens mostly at reboots. I think its my Nvidia driver. Need some help with the error. Thanks
Attachment 147220
Windows 10: BSOD on Alienware 15r3 during reboot error
-
New 04 Aug 2017 #1
BSOD on Alienware 15r3 during reboot error
-
-
New 04 Aug 2017 #2
Hi goldstar324,
There was 1 bsod mini dump file.
When it was debugged there was no definitive malfunctioning driver.
There were other crashes noted in the event logs.
1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) open device manger > sound video and game controllers and audio inputs and outputs > look for Realtek audio > update all Realtek devices listed.
7) windows driver verifier is a tool that is used to find misbehaving drivers.
8) make a brand new restore point
9) backup your files
10) make a backup image using Macrium
Macrium Software | Your Image is Everything
11) Open file explorer > this PC > local disk C: and search for the memory.dmp file
Please post a share link using one drive or drop box into the thread. Its located in C:\Windows\MEMORY.DMP
12) Depending on the finding in the memory.dmp the next step may be windows driver verifier.
https://answers.microsoft.com/en-us/...d-e95ee5d8669d
https://answers.microsoft.com/en-us/...3-c48669e4c983
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
Code:BugCheck 3B, {c0000005, fffff8022b2f802a, ffffc280e4801d30, 0}Probably caused by : ntkrnlmp.exe ( nt!CmNotifyRunDown+1b2 )Code:8/2/2017 9:55 PM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xb2c Faulting application start time: 0x01d30bda16f36b18 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: a72c23c3-e2f3-471d-b049-204097c51a34 Faulting package full name: Faulting package-relative application ID:8/5/2017 12:56 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xb34 Faulting application start time: 0x01d30d85bdb7e899 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: 362f4cbc-359d-4a82-8e5a-e490de464492 Faulting package full name: Faulting package-relative application ID:8/1/2017 12:56 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xb3c Faulting application start time: 0x01d30a6101f23a5f Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: 6e940301-0d78-4b5d-b7fe-b74b8408c8b4 Faulting package full name: Faulting package-relative application ID:7/31/2017 10:11 PM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xb50 Faulting application start time: 0x01d30a49fa2a0d61 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: fd0f5486-8931-4129-988e-77508b4cb323 Faulting package full name: Faulting package-relative application ID:8/5/2017 12:48 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xbc0 Faulting application start time: 0x01d30d849dd8b031 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: ab1af9aa-50e3-4e51-920b-45407116edea Faulting package full name: Faulting package-relative application ID:7/31/2017 11:18 PM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xbd8 Faulting application start time: 0x01d30a534ea480ff Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: a7986f07-436f-46af-8d1b-4348b4c4d571 Faulting package full name: Faulting package-relative application ID:8/2/2017 1:25 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x000000000033636a Faulting process id: 0xc38 Faulting application start time: 0x01d30b2e3d03e083 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: 1a0596e7-6aae-4e80-8dc7-cb4005880ead Faulting package full name: Faulting package-relative application ID:8/5/2017 1:14 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x0000000000338a3d Faulting process id: 0x9bc Faulting application start time: 0x01d30d883a87b455 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: a040c86c-1e1c-4902-ab43-a2d2657caabf Faulting package full name: Faulting package-relative application ID:8/5/2017 12:42 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x0000000000338a3d Faulting process id: 0xb44 Faulting application start time: 0x01d30d83bd296c18 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: e78cad24-3dbe-466c-ae3d-c49b5d1d4c66 Faulting package full name: Faulting package-relative application ID:8/5/2017 12:38 AM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x0000000000338a3d Faulting process id: 0xbd0 Faulting application start time: 0x01d30d831a6f0401 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: f064db9a-8c30-4618-a4fe-ac448a85ccd3 Faulting package full name: Faulting package-relative application ID:8/2/2017 10:03 PM Application Error Faulting application name: AUDIODG.EXE, version: 10.0.15063.447, time stamp: 0xe365c782 Faulting module name: NAHIMICV3apo.dll, version: 6.3.9600.17246, time stamp: 0x587def09 Exception code: 0xc0000005 Fault offset: 0x0000000000338a3d Faulting process id: 0xc1c Faulting application start time: 0x01d30bdb29f5f046 Faulting application path: C:\Windows\system32\AUDIODG.EXE Faulting module path: C:\Windows\system32\NAHIMICV3apo.dll Report Id: 22c73081-56bd-49ee-8dc0-1973a847e2fa Faulting package full name: Faulting package-relative application ID:
Code:Diagnostics---------------Windows Error Reporting:+++ WER0 +++:Fault bucket 120787365299, type 4Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 0000000000338a3dP9: P10: +++ WER1 +++:Fault bucket , type 0Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 0000000000338a3dP9: P10: +++ WER2 +++:Fault bucket 120787364615, type 4Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 000000000033636aP9: P10: +++ WER3 +++:Fault bucket , type 0Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 000000000033636aP9: P10: +++ WER4 +++:Fault bucket 120787364615, type 4Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 000000000033636aP9: P10: +++ WER5 +++:Fault bucket , type 0Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 000000000033636aP9: P10: +++ WER6 +++:Fault bucket 120787365299, type 4Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 0000000000338a3dP9: P10: +++ WER7 +++:Fault bucket , type 0Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 0000000000338a3dP9: P10: +++ WER8 +++:Fault bucket 120787365299, type 4Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 0000000000338a3dP9: P10: +++ WER9 +++:Fault bucket , type 0Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: AUDIODG.EXEP2: 10.0.15063.447P3: e365c782P4: NAHIMICV3apo.dllP5: 6.3.9600.17246P6: 587def09P7: c0000005P8: 0000000000338a3dP9: P10:
Last edited by zbook; 04 Aug 2017 at 23:29.
-
New 05 Aug 2017 #3
Thanks for you help here is the info you requested. I don't have a MEMORY.DMP file the mini dump file is all I have at this time.
Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online/cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Error: 87The online/cleanup-image option is unknown.For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is OS.Stage 1: Examining basic file system structure ... 223744 file records processed.File verification completed. 5709 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 298626 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 37442 data files processed.CHKDSK is verifying Usn Journal... 38960304 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 243617791 KB total disk space. 41980472 KB in 150226 files. 103576 KB in 37443 indexes. 0 KB in bad sectors. 338479 KB in use by the system. 65536 KB occupied by the log file. 201195264 KB available on disk. 4096 bytes in each allocation unit. 60904447 total allocation units on disk. 50298816 allocation units available on disk.C:\Windows\system32>
-
-
New 05 Aug 2017 #4
Open administrative command prompt and type or copy and paste this command:
shutdown /r /o /f /t 00
It will reboot to the windows recovery or advanced troubleshooting menu.
Navigate through the menu to startup options
It will restart.
Then choose option #6 safe mode with command prompt.
Then type or copy and paste this command:
shutdown /r
It will reboot to the desktop
The above step is the most critical step when using windows driver verifier.
Getting to safe mode with command prompt will allow you to type:
verifier /reset
to turn off Windows driver verifier.
In case safe mode with commmand prompt command verifier /reset does not turn off windows driver verifier navigate in the windows advanced trouble shooting menu to command prompt.
This is where you will see X:\windows \system32\cmd.exe
Enter the command: verifier /bootmode resetonbootfail to turn off windows driver verifier.
Windows 10 & 7 - START | type create | select "Create a Restore Point"
c:\windows\minidump
Window driver verifier will stimulate all non-Microsoft drivers to find misbehaving drivers. The misbehaving drivers will produce bsods. The bsods should create minidump files that can be debugged.
Download and install whocrashed and Bluescreenview:
http://www.resplendence.com/whocrashed
Blue screen of death (STOP error) information in dump files.
When a bsod occurs with windows driver verifier there will be a stop code. Typically it is driver verifier detected violation. Sometimes it will also display the misbehaving driver: *.sys
If you see the driver on the bsod please record it.
The system settings need to be modified to not automatically restart so that you have ample time to view the bsod window. Follow the settings in this link:
BSOD Finding and fixing them - Microsoft Community
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart
See this link: BSOD Finding and fixing them - Microsoft Community: https://answers.microsoft.com/en-us/...d-e95ee5d8669d
To setup and start using Windows driver verifier use the settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
When you have time to troubleshoot the bsod you will turn on Windows driver verifier by typing verifier in the left lower corner search.
When Widows driver verifier produces a bsod. You will record the driver if displayed on the bsod. Then you will turn off Windows driver verifier by navigating to the windows recovery or advanced troubleshooting menu, choosing startup options, then safe mode with command prompt and then typing verifier /reset.
When you return to the desktop you will run both Whocrashed and Bluescreenview. Most often they produce the same analysis and result but one may offer insights that the other missed. Once you have information about the driver or the application you will uninstall the driver or the application.
You then have a choice. You can reinstall the driver now using the most up to date driver or you can continue using Windows driver verifier to find the next misbehaving driver.
Once you no longer have any bsod you will run Windows driver verifier for 36 hours of typical computer use. If you get to this point you have successfully addressed the bsod and performed preventative maintenance. You may be able to find drivers or applications that would not have produced bsod for months.
Sometimes software produces bsod. On one of my computers I was unable to uninstall and reinstall Cyberlink and not get a bsod using windows driver verifier. In this case you could use VLC player or use Cyberlink knowing that it may produce a bsod. Antivirus software is another source of bsod. For all the tests while using Windows driver verifier make sure you have turned off all antivirus software other than Windows defender.
Sometimes hardware produces bsod. The bsod minidump files may display information about possible hardware problems.
As you get bsod please update your zip file so we can view the minidump and other logs and guide you through the management:
BSOD - Posting Instructions - Windows 10 Forums
Quote
Related Threads
BSOD Alienware 15 R1, Error 0x124 and 0x133 hal.dll and ntoskrnl.exe in BSOD Crashes and Debugging
Hello! I'm having BSOD problems like DPC_WATCHDOG_VIOLATION and WHEA_UNCORRECTABLE_ERROR caused by hal.dll and ntoskrnl.exe. I'm using an Alienware 15 R1 with Intel i7 4710HQ with GTX980M and 16GB DDR3 RAM. This started somewhere around the middle...
Thread stuck in driver BSOD, bugcheck reboot error in event viewer in BSOD Crashes and Debugging
So I've been having these random Thread Stuck In Driver errors in my poor laptop for a good while now. This time around I had Skype Preview open, Chrome, and League. It happened when I wasn't even in a game on League--- I was responding to a friend...
BSOD CRITICAL_PROCESS_DIED w/error 0xc000000e on reboot in BSOD Crashes and Debugging BSOD Alienware 13 R2 in BSOD Crashes and Debugging
I bought a second hand alienware and it has been constantly blue screening. It seems to be whenever the processor switches power state. If you could help me figure out which driver is playing up it would be greatly appreciated.
The computer is an...
NVIDIA 353.45 causing TDR Error and other BSOD when reboot-how to fix? in General Support
Computer was running fine then I decided to update to the newest driver since it said it was more stable-had an error during installation...tdr error.... then when I rebooted it kept giving me errors like dx error and couldn't get to desktop kept...
