I got this following error after a fresh install of windows 10 home 32bit, the model of the pc is dx7300 slimtower with 2gb of ram and 3.40 dual core processor. I ran the dism restore health and sfc /scannow which seemed to fix it but im wanting to know if theres away i can reassure myself?
Thread Rating:
|
Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED
|
Hey,
Can you please give me a list of your windows drivers You can do that in 2 ways: 1. Open Command Prompt and type: driverquery
<left><form action="https://www.paypal.com/cgi-bin/webscr" method="post">If you are satisfied with my help, consider a donation. Thank you so much for your continued support!
<input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="Y4ZDLXGFS4F8Q"> <input type="image" src="https://www.paypalobjects.com/en_US/GB/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal — The safer, easier way to pay online."> <img alt="" border="0" src="https://www.paypalobjects.com/en_GB/i/scr/pixel.gif" width="0" height="0"> </form> </div></left> 
08-10-2016, 04:24 PM
08-10-2016, 10:44 PM
Smirk24 I would like to know how many updates were installed if any? If you were installing updates that could be the blue screen. If it continues to happen try uninstalling the most recent updates.
WannaBeGeek
08-10-2016, 11:02 PM
It seems to only happen after its about to logon to the desktop which i got 2 more bluescreens also including the posted above and i have another one that im trying to get on here if i can fix the picture size that is It almost seems like it has to do with my memory (ram) or the hard drive but we'll see. And ill post the blue screen report soon 2nd blue screen. All together 3 blue screens. Could this be do to how much quicker the windows 10 media creation tool created the iso file i mean the 32bit iso downloaded way faster the 64bit iso both were verified and successful. The 32bit file seemed way to quick specially when i only have 12 megs of internet and the 32bit file was a little over 2gb 
driverquery.txt (Size: 184.93 KB / Downloads: 3)
Minidump.zip (Size: 253.34 KB / Downloads: 0)
Zip file of all minidumps System Information (local) -------------------------------------------------------------------------------- Computer name: DESKTOP-7971UA0 Windows version: Windows 10 , 10.0, build: 14393 Windows dir: C:\Windows Hardware: HP Compaq dx7300 Slim Tower, Hewlett-Packard, 0A54h CPU: GenuineIntel Intel® Pentium® D CPU 3.40GHz Intel586, level: 15 2 logical processors, active mask: 3 RAM: 2121588736 bytes total -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 8/11/2016 2:26:37 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081016-12265-01.dmp This was probably caused by the following module: oem05afx.sys (OEM05Afx+0x1C34C) Bugcheck code: 0xBE (0xFFFFFFFF808E9651, 0x7C971121, 0xFFFFFFFF8BB30B44, 0xB) Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY file path: C:\Windows\system32\drivers\oem05afx.sys company: Creative Technology Ltd. description: Advanced Audio FX Driver Bug check description: This is issued if a driver attempts to write to a read-only memory segment. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.). Google query: Creative Technology Ltd. ATTEMPTED_WRITE_TO_READONLY_MEMORY On Thu 8/11/2016 2:26:37 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: oem05afx.sys (OEM05Afx+0x1C34C) Bugcheck code: 0xBE (0xFFFFFFFF808E9651, 0x7C971121, 0xFFFFFFFF8BB30B44, 0xB) Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY file path: C:\Windows\system32\drivers\oem05afx.sys company: Creative Technology Ltd. description: Advanced Audio FX Driver Bug check description: This is issued if a driver attempts to write to a read-only memory segment. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.). Google query: Creative Technology Ltd. ATTEMPTED_WRITE_TO_READONLY_MEMORY On Wed 8/10/2016 10:37:33 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081016-9687-01.dmp This was probably caused by the following module: oem05afx.sys (OEM05Afx+0x1C34C) Bugcheck code: 0x50 (0xFFFFFFFF8B4575C0, 0x10, 0xFFFFFFFF8B4575C0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\oem05afx.sys company: Creative Technology Ltd. description: Advanced Audio FX Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.). Google query: Creative Technology Ltd. PAGE_FAULT_IN_NONPAGED_AREA On Wed 8/10/2016 10:37:32 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081016-12234-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Wed 8/10/2016 7:11:21 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081016-11828-01.dmp This was probably caused by the following module: oem05afx.sys (OEM05Afx+0x1C34C) Bugcheck code: 0x1E (0xFFFFFFFFC0000006, 0xFFFFFFFF8B4575C0, 0x8, 0xFFFFFFFF8B4575C0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\oem05afx.sys company: Creative Technology Ltd. description: Advanced Audio FX Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.). Google query: Creative Technology Ltd. KMODE_EXCEPTION_NOT_HANDLED On Wed 8/10/2016 6:18:21 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080916-9765-01.dmp This was probably caused by the following module: oem05afx.sys (OEM05Afx+0x1C34C) Bugcheck code: 0x1E (0xFFFFFFFFC0000006, 0xFFFFFFFF8B4575C0, 0x8, 0xFFFFFFFF8B4575C0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\oem05afx.sys company: Creative Technology Ltd. description: Advanced Audio FX Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.). Google query: Creative Technology Ltd. KMODE_EXCEPTION_NOT_HANDLED On Wed 8/10/2016 6:04:41 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080916-12468-01.dmp This was probably caused by the following module: oem05afx.sys (OEM05Afx+0x1C34C) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF814AF6BD, 0x1, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\oem05afx.sys company: Creative Technology Ltd. description: Advanced Audio FX Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.). Google query: Creative Technology Ltd. KMODE_EXCEPTION_NOT_HANDLED On Wed 8/10/2016 2:26:36 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081016-16250-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 8 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: oem05afx.sys (Advanced Audio FX Driver, Creative Technology Ltd.) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 
WhoCrashedOutput.htm (Size: 17.09 KB / Downloads: 6)
08-11-2016, 05:36 AM
08-11-2016, 11:54 AM
einstall your audio driver that causing the problem the main problem lots people are using a generic driver from Microsoft because your motherboard don, t have driver support for Windows 10 I would now recommend to people if your motherboard don, t support windows 10 drivers don, t use it\
no driver support for windows 10 : HP Compaq dx7300 Slim Tower, Hewlett-Packard, open device manager select sound video game controller select your audio driver right click select Uninstall restart your system
Advanced Audio FX Driver, Creative Technology Ltd is not compatible with Windows 10
Is this a on-board sound or separate sound card you installed? Things you can do:
<left><form action="https://www.paypal.com/cgi-bin/webscr" method="post">If you are satisfied with my help, consider a donation. Thank you so much for your continued support!
<input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="Y4ZDLXGFS4F8Q"> <input type="image" src="https://www.paypalobjects.com/en_US/GB/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal — The safer, easier way to pay online."> <img alt="" border="0" src="https://www.paypalobjects.com/en_GB/i/scr/pixel.gif" width="0" height="0"> </form> </div></left> |
| Users browsing this thread: |
| 1 Guest(s) |