OrigamiShawn
Extraordinary Member
- Joined
- Aug 29, 2014
- Messages
- 48
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff800074e9378, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
***...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffe581df72c028, be000000, 800400}
Probably caused by : GenuineIntel
Followup: MachineOwner
===============================================================================
Common Platform Error Record @ ffffe581df72c028
-------------------------------------------------------------------------------
Record Id : 01d41e0f00ce2801
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 7/17/2018 21:35:07 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffe581df72c0a8
Section @ ffffe581df72c180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Flags : 0x00
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000005
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffe581df72c0f0
Section @ ffffe581df72c240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000005
CPU Id : c3 06 03 00 00 08 10 05 - bf fb fa 7f ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ ffffe581df72c240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe581df72c138
Section @ ffffe581df72c2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : Internal timer (Proc 5 Bank 4)
Status : 0xbe00000000800400
Address : 0x00007ff68da8931b
Misc. : 0x00007ff68da8931b
BIOS_VERSION: 2202
BIOS_DATE: 07/11/2014
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: Z97-C
Z97-C Driver & Tools | Motherboards | ASUS GlobalVersion 2801
2016/03/
Z97-C
BIOS 2801
Improve system stability
Hi,
I'm back. So if your unsure how to proceed with the bios flash take it either to a shop or ask a friend who has experience.
Although bios flashing isn't as risky as it once was it still does carry some risk. If the flash is somehow interrupted then it can affect the motherboard so care is needed.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff800074e9378, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
Hi,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 133, {1, 1e00, fffff800074e9378, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption
nice job with the bios update.
Although the above dump file isn't opening properly I can see enough details via whats called a stack trace to see that the Nvidia gpu driver was the cause with this bsod.
You sent three dump files, one is a bugcheck 124 and two are like the above.
You may have some corruption within the gpu driver and Windows 10.
To clear the gpu corruption, uninstall the current driver using the DDU or Display Driver Uninstaller.
You must run this in safe mode (disconnect from the net too just so windows won't install a driver via Windows updates)
Once back in windows pop your driver (update to the latest version if need be) back on windows.
Run these scans which hopefully will cure any corruption within the system:
Open an administrators command prompt (you can find command prompt in the start menu under 'windows system', simply right click on it and run as admin). Type (or copy and paste):
sfc /scannow
Press enter and await results.
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
Hope this helps. Please post any new dump files after making the above changes.
Hi,
I had another look over your drivers and you could do with updating your chipset and storage drivers:
iaStorA.sys Fri Apr 4 00:00:05 2014: Intel RST (Rapid Storage Technology) driver. A later version can be found under the heading of SATA in the driver section:
Z97-C Driver & Tools | Motherboards | ASUS Global
I couldn't actually find your chipset drivers to see a date so try updating anyway.
Look under the chipset heading and you'll see drivers for both chipset and 'engine management', you want both.
Z97-C Driver & Tools | Motherboards | ASUS Global
The trouble is with TDR's is that they can caused by a multitude of issues and tracking the cause down can sometimes take a bit of trial and error.
Consider trying earlier drivers.
3D.com carries copies of recent Nvidia drivers so you can see if the issue is with every driver.
Link Removed
See if the gpu will complete the burn in test on furmark:
Furmark
Not yet..Should I consider buying a new GPU?