Multiple BSODs each day :(

Toggle sidebar Toggle sidebar
Rivelta

Rivelta

Commendable
Aug 25, 2016
11
0
1,510
I've had Bluescreens with this PC for a long time but recently they started appear more frequently. :pfff:
I am not an expert with computers and here seems to be very professional people so please someone, more knowledgeable than me, I need help. Also the computer doesn't seem to be able to restart by itself after the Bluescreen, instead it's stuck on 100%.

Here are some filedumps from WhoCrashed:

System Information (local)
--------------------------------------------------------------------------------

Computer name: FLAMERV3
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., M5A97
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8533749760 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 25.8.2016 11:49:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082516-20875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8016F63AA32, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25.8.2016 11:49:00 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xCDA8)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8016F63AA32, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: NT File System 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 25.8.2016 8:06:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082516-21281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801CA0DF924, 0xFFFFD00022FE5960, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 24.8.2016 18:10:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082416-21812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803B143EA32, 0xFFFFD0017002DD90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 24.8.2016 12:34:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082416-21890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8033ACAFA32, 0xFFFFD00022EEDDB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 24.8.2016 10:27:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082416-26796-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35F1F)
Bugcheck code: 0x124 (0x0, 0xFFFFE000E8504028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 23.8.2016 14:25:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-29093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802392A9A32, 0xFFFFD00022FAEC60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 22.8.2016 15:00:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082216-23046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x61924)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802FE46D924, 0xFFFFD000D5FFE678, 0xFFFFD000D5FFDE90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 22.8.2016 9:34:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082216-21703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800A5024A32, 0xFFFFD00021626430, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 20.8.2016 19:38:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-22156-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x4226)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801CAB74226, 0xFFFFD000220C65A8, 0xFFFFD000220C5DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: USB 1.1- ja USB 2.0-portin ohjain
Bug check description: This indicates that a system thread 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

21 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 372.54 , NVIDIA Corporation)

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.




 
Solution
J
I looked at the last 5 bugchecks each had a bad memory address applied to a driver.
this means you should also download and run memtest to confirm that your memory timings are set correctly in bios.

also, you have the microsoft generic USB 3 drivers installed but your BIOS is dated in 10/25/2012
since the USB 3 specs were changed in 2013 you bios is not likely supporting the generic drivers correctly.
This means you need to install the USB 3 drivers for your motherboard or you will just get a bunch of strange things going on.
or you can disable your usb 3.0 support in BIOS.
your motherboard has usb 3 drivers at : https://www.asus.com/Motherboards/M5A97/HelpDesk_Download/
Asmedia_USB3_V1.16.35.1 dated 2016/08/02 (i think asus knows...
Sort by date Sort by votes
LukeFatwalker

LukeFatwalker

Reputable
Dec 29, 2015
733
1
5,660
There's been a critical driver failiure, more than likely tied to your boot process. You'll need to run Startup Repair (Guide here: http://www.techrepublic.com/article/rescue-an-ailing-system-launch-windows-10-startup-repair-from-the-recovery-drive/)

If Startup Repair doesn't work, you'll need to reformat the machine. Which will wipe everything off the machine, including all of your data.

Once you're up and running you may want to grab a disk imager (Macrium Reflect Free) or a Snapshot tool (Rollback Rx) and start running regular backups.
 
Upvote 1 Downvote
Rivelta

Rivelta

Commendable
Aug 25, 2016
11
0
1,510
Just to clarify, when the computer bluescreens it is not able to restart like usual after collecting all the error-data.
Instead, I need to hold the power-button to shut it down and then it runs just like usual.

Update: I have ASUS M5A97 motherboard that has AMD 970 chipset so I assume this is the one I needed to download:
http://support.amd.com/en-us/download/chipset?os=Windows%2010%20-%2064 (please correct if I'm wrong)
Even after installing them l got another KMODE_EXCEPTION_NOT_HANDLED bluescreen.
Ran memtest86 with both sticks on and they passed 5 times out of 5 tests. Not sure should I do some more testing overnight.

 
Upvote 0 Downvote
Rivelta

Rivelta

Commendable
Aug 25, 2016
11
0
1,510


Guess I'll try the repair... I don't get for what this disk imager is for in the second step tho...?

 
Upvote 0 Downvote
LukeFatwalker

LukeFatwalker

Reputable
Dec 29, 2015
733
1
5,660


Just to create a backup. You'll have a clean state once you repair/reformat so it's recommended you capture that in a disk image or snapshot.

Programs like Macrium Reflect Free and Rollback Rx are free, but of course with disk imager you need to pay for storage media, so a snapshot tool is good if you want absolutely free.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
error code 0xC0000005 means a bad memory address is being given to a driver. Your first test should be to run memtest to confirm your memory timings are correct. if memtest works without errors, then you would remove any overclocking drivers installed or copy the memory dump from c:\windows\minidump directory to a cloud server like microsoft onedrive, share the files for public access and post a link.
most likely you have a BIOS memory timing issue or a problem with overclocking. (just based on the memory address used)

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I looked at the last 5 bugchecks each had a bad memory address applied to a driver.
this means you should also download and run memtest to confirm that your memory timings are set correctly in bios.

also, you have the microsoft generic USB 3 drivers installed but your BIOS is dated in 10/25/2012
since the USB 3 specs were changed in 2013 you bios is not likely supporting the generic drivers correctly.
This means you need to install the USB 3 drivers for your motherboard or you will just get a bunch of strange things going on.
or you can disable your usb 3.0 support in BIOS.
your motherboard has usb 3 drivers at : https://www.asus.com/Motherboards/M5A97/HelpDesk_Download/
Asmedia_USB3_V1.16.35.1 dated 2016/08/02 (i think asus knows there was a problem and update the driver)

this could account for the memory errors (bad driver can over write other drivers memory) to debug usb problem you have to provide a kernel memory dump but I would just update the driver and see if it help.

you could get some of the bugchecks (2 of them ) if your drive is having errors or you ran out of virtual memory. IE you hard drive was filled, or you page file was turned off or somehow limited and prevented from growing in size. you can download crystaldiskinfo.exe to read the errors from the SMART data from the drive to see if the drive is failing. (i guess the old sata drivers could cause these errors also)
(again, the usb problem can account for all of the bugchecks I looked at, while the drive problem could only account for 2 of the bugchecks)




----------
second bugcheck was also a bad memory address applied to a driver. memory management, freeing virtual memory.
system up time 30 mins
--------------
the error code of the first bugcheck is 0xc0000005 which is a bad memory address passed to a driver. (system up time 14 hours)
this could be a general memory timing problem or could be caused by one of the old drivers making a programming mistake.
try updating the below drivers if you can, I will look at a few other bugchecks to see if there is a pattern.

bios looks like the current version but the motherboard drivers are a year old. pick up the new ones
https://www.asus.com/Motherboards/M5A97/HelpDesk_Download/

old drivers: these look like old amd chipset drivers, you might go to amd to get new ones
http://support.amd.com/en-us

normally you would find them on your motherboard vendors website but it looks like they kind of stopped updating the drivers for this board.
generally you would go back and install the drivers from the previous version of the operating system but they did not have them listed there either. first listing of the chipset drivers were for window 7 64 bit. I would try the amd website.
\SystemRoot\System32\drivers\amd_sata.sys Fri Mar 4 12:45:41 2011
\SystemRoot\System32\drivers\amd_xata.sys Fri Mar 4 12:45:44 2011
\SystemRoot\System32\drivers\amdiox64.sys Thu Feb 18 07:17:53 2010

Focusrite audio USB 2.0 driver
\SystemRoot\system32\DRIVERS\ffusb2audio.sys Mon Sep 10 03:16:34 2012
see if you can get a new driver for this http://global.focusrite.com/downloads

Native Instruments ISO Mounter Driver (this should not be needed for windows 10, i would remove it)
\SystemRoot\System32\drivers\NIWinCDEmu.sys Tue Aug 9 01:25:29 2011

you might look for a update for this driver http://www.carrona.org/drivers/driver.php?id=tap0901.sys
\SystemRoot\System32\drivers\tap0901.sys Thu Aug 22 05:40:01 2013

Sonic CD/DVD driver (used by many different CD/DVD programs) (I would remove this driver)
\SystemRoot\System32\Drivers\PxHlpa64.sys Tue Apr 24 10:26:29 2012

machine info:
BIOS Version 1605
BIOS Starting Address Segment f000
BIOS Release Date 10/25/2012
Manufacturer ASUSTeK COMPUTER INC.
Product M5A97
Version Rev 1.xx
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz



 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom