[phillpower2]

To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of  jcgriff2 

 

1. Create a Windows System Restore Point -

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
 

2. Run Driver Verifier -

- Windows 7 & Vista - START | type verifier 
- Windows 10/8.1/8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier 

Make these selections - 
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -

▪ Special Pool 
▪ Pool Tracking 
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8) 
▪ Miscellaneous Checks

4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish 
8. Re-boot

 

 

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

 

- After re-start, you may not be able to log on to normal Windows

... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

... • Select "System Restore"

... • Choose the restore point that you created in step #1

 

- For Driver Verifier status

--- select last option, 1st screen -or-

--- type verifier /query (in a cmd/DOS screen)

- To turn Driver Verifier off - verifier /reset then re-boot

 

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.

- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

 

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

 

Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.  

[Advertisements]

ok i did the verifier and rebooted and nothing happened is there meant to be a status screen that shows the verifiers progress or you just start windows normally

 

also there was no "Concurrency Stress Test (new as of Windows 8)" and their were two DDI compliance checking.

 

*DDI compliance checking

*DDI compliance checking (Additional)

 

Spoiler

Microsoft Windows [Version 10.0.10586]
© 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x000a092b

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[X] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Extensions:

wdm: rules.all

Verified Drivers:

kl1.sys
cm_km.sys
jraid.sys
scsiport.sys
klbackupdisk.sys
mv91xx.sys
mvxxmm.sys
dump_mvxxmm.sys
klbackupflt.sys
klflt.sys
klpd.sys
klif.sys
klhk.sys
klwfp.sys
ndis.sys
klim6.sys
klwtp.sys
cfosspeed6.sys
kneps.sys
nvlddmkm.sys
cmudaxp.sys
rt640x64.sys
asacpi.sys
nvvad64v.sys
nvhda64v.sys
cork70.sys
klkbdflt.sys
klmouflt.sys
rzendpt.sys
rzudd.sys
dump_diskdump.sys
dump_mv91xx.sys
dump_dumpfve.sys
atmfd.dll
kldisk.sys
rzpmgrk.sys
rzpnk.sys
speedfan.sys
nvstreamkms.sys
hiber_mvxxmm.sys

C:\WINDOWS\system32>

Edited by Toombs, 21 April 2016 - 04:02 AM.

[Toombs]

ok i did the verifier and rebooted and nothing happened is there meant to be a status screen that shows the verifiers progress or you just start windows normally

 

also there was no "Concurrency Stress Test (new as of Windows 8)" and their were two DDI compliance checking.

 

*DDI compliance checking

*DDI compliance checking (Additional)

 

Spoiler

Microsoft Windows [Version 10.0.10586]
© 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x000a092b

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[X] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Extensions:

wdm: rules.all

Verified Drivers:

kl1.sys
cm_km.sys
jraid.sys
scsiport.sys
klbackupdisk.sys
mv91xx.sys
mvxxmm.sys
dump_mvxxmm.sys
klbackupflt.sys
klflt.sys
klpd.sys
klif.sys
klhk.sys
klwfp.sys
ndis.sys
klim6.sys
klwtp.sys
cfosspeed6.sys
kneps.sys
nvlddmkm.sys
cmudaxp.sys
rt640x64.sys
asacpi.sys
nvvad64v.sys
nvhda64v.sys
cork70.sys
klkbdflt.sys
klmouflt.sys
rzendpt.sys
rzudd.sys
dump_diskdump.sys
dump_mv91xx.sys
dump_dumpfve.sys
atmfd.dll
kldisk.sys
rzpmgrk.sys
rzpnk.sys
speedfan.sys
nvstreamkms.sys
hiber_mvxxmm.sys

C:\WINDOWS\system32>

Edited by Toombs, 21 April 2016 - 04:02 AM.

[phillpower2]

You would not even know DV was running unless a crash occurs, just a case of wait and see now I`m afraid.

 

- For Driver Verifier status

--- select last option, 1st screen -or-

--- type verifier /query (in a cmd/DOS screen)

 

 

also there was no "Concurrency Stress Test (new as of Windows 8)" and their were two DDI compliance checking.

 

 

Thats ok 

[Toombs]

ok cheers. the waiting game begins lol. 

[phillpower2]

You are welcome 

 

Will look out for an update over the weekend.

[Toombs]

speaking of updates is it ok to install drivers during the verification period? ie. nvidia driver.

[phillpower2]

Please see my canned text below regarding driver updates;

 

Avoid using any software that automatically updates your system.

 

Please note that drivers should never be updated unless it is to address a known issue, if a driver is installed needlessly you can end up creating the very issue that the updated driver was intended to correct, rolling back to the previous driver does not always work and waiting for the next driver update can take some time and also not work. 

 

Always obtain drivers directly from the provider of your hardware/software and only use drivers or patches from third parties for older or no longer supported hardware/software

 

 

 

[Toombs]

ok dota 2 seems to be working fine now as i tried using openGL instead of the usual directX on steam launch options with "-gl".

Edited by Toombs, 24 April 2016 - 12:01 AM.

[phillpower2]

No crashes is good but have you checked that DV is still running.

[Toombs]

yes its still running and it has been 72hours.

 

 

Attached Files

•  042416-43125-01.zip   13.07KB   300 downloads

[phillpower2]

Best Answer

Debug session time: Sun Apr 24 00:16:00.085 2016 (UTC - 4:00)
System Uptime: 0 days 0:00:27.921
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001d0072228, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
ffffd001`b85b96f0 fffff802`1922b7b1 : 00000000`00000000 ffffe001`d0072200 fffff802`1914d6a0 fffff802`1920e340 : nt!WheapCreateLiveTriageDump+0x81
ffffd001`b85b9c20 fffff802`1908bc10 : ffffe001`d0072200 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffd001`b85b9c50 fffff802`1908cd55 : fffff802`1914d640 fffff802`1914d640 fffff802`1914d6a0 fffff801`3e5332c0 : nt!WheapProcessWorkQueueItem+0x48
ffffd001`b85b9c90 fffff802`18ecc6a9 : fffff802`1920e200 ffffe001`cddad040 fffff801`00000000 ffffe001`cef67c68 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd001`b85b9cc0 fffff802`18f5e895 : 00000004`ad1b3ffe 00000000`00000080 ffffe001`cc462540 ffffe001`cddad040 : nt!ExpWorkerThread+0xe9
ffffd001`b85b9d50 fffff802`18fc2906 : ffffd001`beb6d180 ffffe001`cddad040 fffff802`18f5e854 bf7fbf7f`8d948d94 : nt!PspSystemThreadStartup+0x41
ffffd001`b85b9da0 00000000`00000000 : ffffd001`b85ba000 ffffd001`b85b4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

 

 

Possible causes include overheating, too much voltage going to the CPU (also causes overheating) and a bad BIOS setting.

 

When was the last time you cleaned out the insides of the case.

 

Do you know how to go into the BIOS and restore the MBs default factory settings, they are sometimes listed as "most stable" or "factory default" and if available the "optimized settings" should not be used as it is a form of OCing and leads to instability.

 

Please take expanded screenshots and only use the method below to attach them.

Download Speedfan and install it.  Once it's installed, run the program and post here the information it shows.  The information I want you to post is the stuff that is circled in the example picture I have attached.

If you are running on a vista machine, please go to where you installed the program and run the program as administrator.

 

 (this is a screenshot from a vista machine)

 

Download then run HWMonitor and post a screenshot so that we have a comparison to the Speedfan results, details from here

 

To capture and post a screenshot;

Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... Click on the More Reply Options tab then after typing in any response you have... click on Choose File...desktop...find the screenshot..select it and click on Attach This File...on the lower left...after it says upload successful...click on add reply like you normally would.

 

Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.

[Toombs]

Last time i replaced my cpu's thermal paste was a month or two even did my gpu's as well with my old arctic mx-4 (do thermal paste have expiry dates? lol). As for BIOS my cpu is stock clocked but my ram is set to xmp to unlock my rams normal 1600mhz instead of intel down clocking it to 1333mhz. I updated my bios ages but i forgot the reason why not sure if it was a marvel controller issue wth usb3 or with the xmp profile for my ram last bios update was (2012/08/29). but ill check if i did a good job on the thermal paste lol or if my cpu coolers clamps are loose.

 

speedfan 2016-04-25

 

 

speedfan 2016-04-17 (screenshot when dota2 crashed shouldve posted it earlier   )

 

 

 

Edited by Toombs, 24 April 2016 - 06:37 PM.

[phillpower2]

Please run HWMonitor and attach the screenshot for us so that we have a comparison to Speedfan.

 

Looking at Speedfan you have have high CPU temps and usage for a computer not under any load, there is a strong possibility that both are being caused by an ineffective CPU cooling fan, note the 100% setting but the fan only running at 746/747rpm.

 

I updated my bios 

 

 

Was not suggesting a BIOS update only restoring the MBs default voltage and fan speed settings.

 

The high AUX temp that you can see could be for either the PSU or Southbridge, HWMonitor should tell us which.

[Toombs]

As far as I know I haven't tinkered with any voltages, just the fans. 

The aux has always been like that ever since lol. As for ineffective cpu cooling I'm using Zalman CNPS10X Performa with a Noctua NF-P12 fan.

 

Edited by Toombs, 25 April 2016 - 02:17 AM.

[phillpower2]

As far as I know I haven't tinkered with any voltages, just the fans.  

 

 

HWMonitor reports the same high CPU temps, low CPU fan speed + additionally over voltage to the Ram which should only be 1.5V but is reportedly receiving 1.7+V

 

Ram specs here

 

Please see section 3.10 here for how to load the failsafe default values for your MB in the BIOS.

 

As for ineffective cpu cooling I'm using Zalman CNPS10X Performa with a Noctua NF-P12 fan.

 

 

The Noctua NF-P12 cooling fan should be running at between 900 and 1300rpm specs here

 

Last time i replaced my cpu's thermal paste was a month or two even did my gpu's as well 

 

 

Did you properly clean off the old thermal compound with industrial strength alcohol and how old exactly was the compound that you used, I suspect that a tired cooling fan or one that has been slowed down in the BIOS is causing this but have to ask the questions about the thermal compound etc.