Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD while using computer Dirt Rally


  • Please log in to reply
2 replies to this topic

#1 JackTerrier3000

JackTerrier3000

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North Wales, UK
  • Local time:12:19 PM

Posted 09 February 2018 - 09:30 AM

Hi i hope i have done this right   sorry if not, 

  I have had 2 BSODS today  and i think its the same cause  soemthing to do with watchdog violation,    it seemed to start after i did somed windows updates on sunday   i have attached the updates  screenshot in case this helps

 

Other information requested

Its an own build PC  built in August 2017  windows 8.1 pro 64bit   it`s the only intallation of windows its had

   Again i hope all informations here   i am not brilliant at this sort of stuff   :o/   if you need more info just ask   

 Thanks in advance

  

 

 

 

Attached File  SysnativeFileCollectionApp.zip   445.09KB   2 downloadsAttached File  Updates.jpg   52KB   0 downloads



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:19 AM

Posted 10 February 2018 - 04:10 PM

Your UEFI/BIOS (version 0502) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 177 Windows Update hotfixes installed.  Most systems have more than this  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

You have 3 hard drives.  What is the make/model/wattage and age of your Power Supply?
The purpose of this question is to get you to evaluate your PSU.
- PSU's tend to get less efficient with age
- adding components over time may decrease the ability of the PSU to support the entire system (Maybe remove some stuff to see if that helps?)
- while you can measure the output of a PSU with a multimeter, the readings may change dramatically when the PSU is put under load.  PSU testing instructions (by dc3) here:  https://www.bleepingcomputer.com/forums/t/654994/pc-is-crashingfreezing-up-multiple-times-daily/page-2#entry4341756
- there's a free PSU test in the OCCT program at http://www.ocbase.com/

Please do not use disk cleaners (such as CCleaner) while we're troubleshooting.

With some settings it deletes the error records/events/reports.

This looks like a hardware problem to me.  The BSOD's seem to be suggestive of a video problem.

I'd suggest:

 

My suggested way to diagnose a hardware problem (3 steps):

 

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:

 

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


Step #2)  If all the tests pass, then try to perform a clean install of Windows:

 

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [ :(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Fri Feb  9 08:55:00.608 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020918-10453-01.dmp]
Windows 8.1 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.18896.amd64fre.winblue_ltsb_escrow.180108-1534
System Uptime:0 days 1:05:06.328
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  drt.exe
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  0502   
  BIOS Release Date             11/18/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK Computer INC.
  Product Name                  System Product Name
  Baseboard Product             M5A78L-M PLUS/USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb  8 13:15:24.187 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020818-8968-01.dmp]
Windows 8.1 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.18896.amd64fre.winblue_ltsb_escrow.180108-1534
System Uptime:0 days 1:23:23.906
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  0502   
  BIOS Release Date             11/18/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK Computer INC.
  Product Name                  System Product Name
  Baseboard Product             M5A78L-M PLUS/USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Feb  4 15:07:31.654 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020418-9062-01.dmp]
Windows 8.1 Kernel Version 9600 MP (6 procs) Free x64
Built by: 9600.18896.amd64fre.winblue_ltsb_escrow.180108-1534
System Uptime:0 days 1:43:08.375
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  PowerDVD.exe
FAILURE_BUCKET_ID: 0x133_ISR_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  0502   
  BIOS Release Date             11/18/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK Computer INC.
  Product Name                  System Product Name
  Baseboard Product             M5A78L-M PLUS/USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Fri Feb  9 08:55:00.608 2018 (UTC - 5:00)**************************
PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
ASACPI.sys                  Thu Nov  1 21:54:34 2012 (509327DA)
Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
IOMap64.sys                 Wed Oct 22 20:52:12 2014 (5448513C)
CLVirtualBus01.sys          Wed Nov  5 04:11:18 2014 (5459E9B6)
LHidEqd.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LEqdUsb.Sys                 Tue Jun  9 15:25:30 2015 (55773DAA)
LMouFilt.Sys                Tue Jun  9 15:25:39 2015 (55773DB3)
LHidFilt.Sys                Tue Jun  9 15:25:40 2015 (55773DB4)
000.fcl                     Thu May 19 01:25:38 2016 (573D4E52)
GeneStor.sys                Mon Aug 15 02:24:20 2016 (57B16014)
RTKVHD64.sys                Tue Nov  8 05:44:57 2016 (5821ACA9)
cthda.sys                   Tue Dec 20 02:12:40 2016 (5858D9E8)
mbae64.sys                  Wed Jan 11 12:08:00 2017 (58766670)
cthdb.sys                   Mon Feb  6 22:41:06 2017 (589941D2)
farflt.sys                  Tue Sep  5 19:44:07 2017 (59AF36C7)
mwac.sys                    Thu Sep  7 12:04:14 2017 (59B16DFE)
iocbios2.sys                Fri Sep 15 06:22:21 2017 (59BBA9DD)
mbam.sys                    Thu Oct 12 11:23:13 2017 (59DF88E1)
mbamswissarmy.sys           Fri Oct 13 14:58:51 2017 (59E10CEB)
MbamChameleon.sys           Tue Nov 28 23:17:27 2017 (5A1E34D7)
nvlddmkm.sys                Wed Jan  3 18:39:48 2018 (5A4D69C4)

http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
CLVirtualBus01.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=000.fcl
http://www.carrona.org/drivers/driver.php?id=GeneStor.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=cthda.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=cthdb.sys
http://www.carrona.org/drivers/driver.php?id=farflt.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=mbamswissarmy.sys
http://www.carrona.org/drivers/driver.php?id=MbamChameleon.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 


Edited by usasma, 10 February 2018 - 04:10 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 JackTerrier3000

JackTerrier3000
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North Wales, UK
  • Local time:12:19 PM

Posted 11 February 2018 - 06:46 AM

HI Thanks for you reply  -

   I have read through it and i  hope i understand what i need to do   i will have to do them later

    YOu ask about the updates I have updated all windows updates except the last few weeks  - i updated on the 4th and thans when the problem started so i have removed them and it seems to have fixed the problem - maybe it was a rogue update?

 My power supply is a Corsair CX750M  it was about in may last year to replace the failing one from my old system and i got this one in anticipation of this new build

   I will have a look into updating the BIOS now   (if i can remember how to do it ) 

As for reinstallation of windows   I REALLY dont want to do that  i have loads of stuff that would need reinstalling and downloading :(

I have run the GPU stress test  it went up to 46oC  then dropped to a steady 31oC   after its fans started up

   Again thanks for your reply


Edited by JackTerrier3000, 11 February 2018 - 07:06 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users