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

Multiple BlueScreens crashes


  • Please log in to reply
9 replies to this topic

#1 fedlix

fedlix

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:04:16 PM

Posted 27 June 2016 - 11:15 AM

Hi, I'm looking for help, I have been looking around a lot to solve my problems but didn't find a solution. 
I'll post here my Who crashed analysis 
The last two crashes are the most relevant since I did a fresh install of my NVIDIA drivers and the crashes related to those drivers stoped after.
Also, I ran memTest, And gpu stress test for a while without any crashes. 
Thanks for the help If you need more information you can ask for it, I really want to get done with this problem and I'm also wanting to learn how to deal with this kind of problems.

Edit: I atached the Other files 

Os: windows 10

64 bit

Original os :windows 7

Retail Os

Age of system : 4 years 

Age of os Installation : 1 month ( window 10) Problems present before windows 10 installation 

 

Cpu:intel i3570k 

Gpu: gtx 970

Motherboard: ga z77x d3h

Desktop pc 

 

I have experienced two crashes while running driver verifier 

No blueScreen tough the computer just freezed i had to restart both times

 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 6/27/2016 10:03:21 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062716-17968-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x56)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFF800FE123180, 0x0)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 Mon 6/27/2016 10:03:21 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x56)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFF800FE123180, 0x0)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 Sun 6/26/2016 5:44:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062616-18140-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x158ECD, 0x2, 0x0, 0xFFFFF803D2B03A62)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 6/12/2016 4:07:14 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061116-22515-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x16E085)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8017B9AE085, 0xFFFFD00148C6DB58, 0xFFFFD00148C6D370)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 368.39
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 368.39
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.39 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 6/3/2016 9:28:24 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060316-22828-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8009C554F67, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.



 

Conclusion

5 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.39 , 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.



 

Attached Files


Edited by fedlix, 27 June 2016 - 02:54 PM.


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:07:16 PM

Posted 28 June 2016 - 06:25 AM

Out of 4 memory dumps there were 4 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):  Please note that the first 2 reported are the same (one's the minidump that was extraced from the MEMORY.dmp file)

 

- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html

Your UEFI/BIOS (version F18i) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.

Only 7 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

There are many, many Windows Update failures in the WER section of the MSINFO32 report.

 

This wireless device is disabled in Device Manager:

 

Realtek RTL8192CE Wireless LAN 802.11n PCI-E NIC    PCI\VEN_10EC&DEV_8178&SUBSYS_817810EC&REV_01\4&355A308D&0&00E1    This device is disabled.

If not using it, it's best to disable this in the BIOS.  But, if you want to keep it, please re-enable it and then update the drivers for it.  Then, if you'd like, feel free to disable it again AFTER it's been updated (the drivers load into memory before the device is disabled).

 

MSI Afterburner (along with EVGA Precision and Riva Tuner) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

 

**************************Mon Jun 27 06:03:21.691 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062716-17968-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
System Uptime:0 days 16:17:30.359
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, fffff800fe123180, 0}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff800fe123180, The PRCB address of the hung processor.
Arg4: 0000000000000000, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
  BIOS Version                  F18i
  BIOS Release Date             01/06/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77X-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 26 13:44:40.874 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062616-18140-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
System Uptime:1 days 2:46:40.542
Probably caused by :memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+c2 )
BugCheck A, {158ecd, 2, 0, fffff803d2b03a62}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000158ecd, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803d2b03a62, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_nt!MiUnlinkFreeOrZeroedPage
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
  BIOS Version                  F18i
  BIOS Release Date             01/06/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77X-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 12 00:07:14.502 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\061116-22515-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
System Uptime:0 days 1:21:00.174
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+16e085 )
BugCheck 1000007E, {ffffffffc000001d, fffff8017b9ae085, ffffd00148c6db58, ffffd00148c6d370}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8017b9ae085, The address that the exception occurred at
Arg3: ffffd00148c6db58, Exception Record Address
Arg4: ffffd00148c6d370, Context Record Address
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_BAD_IP_nvlddmkm!Unknown_Function
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
  BIOS Version                  F18i
  BIOS Release Date             01/06/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77X-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun  3 17:28:24.548 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\060316-22828-01.dmp]
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
System Uptime:1 days 22:00:34.218
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a9e2 )
BugCheck 1E, {ffffffffc0000005, fffff8009c554f67, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8009c554f67, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  backgroundTask
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
  BIOS Version                  F18i
  BIOS Release Date             01/06/2014
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             Z77X-D3H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 




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:

**************************Mon Jun 27 06:03:21.691 2016 (UTC - 4:00)**************************
povrtdev.sys                Wed Feb 24 05:51:44 2010 (4B8504C0)
mvxxmm.sys                  Thu Jan 19 01:50:44 2012 (4F17BD44)
mvs91xx.sys                 Thu Jan 19 01:51:00 2012 (4F17BD54)
iusb3hcs.sys                Tue Mar 27 04:11:21 2012 (4F717629)
L1C60x64.sys                Tue Jul 16 02:56:56 2013 (51E4EEB8)
iaStorA.sys                 Thu Aug  1 21:39:52 2013 (51FB0DE8)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
TeeDriverx64.sys            Thu Sep  5 14:02:18 2013 (5228C72A)
viahduaa.sys                Mon Dec 16 00:58:56 2013 (52AE96A0)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
dc1-controller.sys          Thu Oct 29 22:46:54 2015 (5632DA1E)
DevAuthE.sys                Thu Oct 29 22:47:14 2015 (5632DA32)
SCDEmu.SYS                  Wed Feb 10 05:44:15 2016 (56BB147F)
xboxgip.sys                 Tue Feb 23 04:20:35 2016 (56CC2463)
nvhda64v.sys                Thu Mar 24 15:26:36 2016 (56F43F6C)
xinputhid.sys               Tue Mar 29 04:16:55 2016 (56FA39F7)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
NvStreamKms.sys             Sun May  1 17:00:16 2016 (57266E60)
nvlddmkm.sys                Thu Jun  2 23:11:28 2016 (5750F560)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 12 00:07:14.502 2016 (UTC - 4:00)**************************
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
jvtlt.sys                   Tue Aug 11 13:35:18 2015 (55CA3256)
nvlddmkm.sys                Thu May 19 21:34:38 2016 (573E69AE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun  3 17:28:24.548 2016 (UTC - 4:00)**************************
RTCore64.sys                Fri Apr 24 03:01:47 2015 (5539EA5B)
rtwlane_13.sys              Fri Jul 10 07:54:32 2015 (559FB278)

http://www.carrona.org/drivers/driver.php?id=povrtdev.sys
http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys
http://www.carrona.org/drivers/driver.php?id=mvs91xx.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=L1C60x64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=dc1-controller.sys
DevAuthE.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=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=xboxgip.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
xinputhid.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=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
jvtlt.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=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
rtwlane_13.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.
 

 


Edited by usasma, 28 June 2016 - 06:26 AM.

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 fedlix

fedlix
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:04:16 PM

Posted 28 June 2016 - 06:46 PM

The Gpu has alredy been tested and the ram too. the 2014 bios is the last version. I started having this problem when they installed my new gpu after my old one died. it worked for some time then the computer was stuck at start up. I had to remove the card and replug it for the pc to be able too boot. After reInstalling the card i updated the bios. after several BSOD i took the computer to the company that selled me the card and they tested it. they said that the card was fine and the problem was with the computer ( they tested it for a long time and it didnt crash ).  

The windows updates that fails are the ones related to office. they fail because my windows office is not official.

 

I have unistalled MSI and im going to do cpu stress test and hdd tough i have been monitoring the temps for a long time and there is no sign of overheating 

 

different crash today 

 

On Tue 6/28/2016 11:28:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062816-23593-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x402, 0xFFFFC001EF5F2E38, 0x80000000153F3882, 0xFFFFF601EF5F2E38)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


Edited by fedlix, 28 June 2016 - 06:49 PM.


#4 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:07:16 PM

Posted 29 June 2016 - 06:41 AM

Please zip up and upload the contents of the C:\Windows\Minidump directory.
If you have difficulties zipping it, copy it to your Desktop and zip it up from there.

While waiting for a reply, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 


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.

#5 fedlix

fedlix
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:04:16 PM

Posted 29 June 2016 - 12:09 PM

I have run Driver Verifier yesterday it crashed several times faster than usual but the computer crashed witouth creating a minidump ( no blueScreen ) 

Im not going to be here today il run it again tomorow 

Attached Files


Edited by fedlix, 29 June 2016 - 12:09 PM.


#6 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:07:16 PM

Posted 29 June 2016 - 02:57 PM

Nothing new in the minidumps.

I'll wait to run them after you post the next set.


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.

#7 fedlix

fedlix
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:04:16 PM

Posted 30 June 2016 - 09:14 AM

This time computer crashed on startup while driver verifier was on with the setting indicated in the website you gave me.

I reconfigured the driver verifier options the way this website says to do it and i was able to boot.

No minidumps created.


Edited by fedlix, 30 June 2016 - 09:18 AM.


#8 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:07:16 PM

Posted 02 July 2016 - 09:03 AM

Did the BSOD give any information?

 

Try to let it crash 2 or 3 times with verifier running,

Then check C:\Windows/Minidump

If nothing there, then check C:\Windows for the date/time stamp on MEMORY.dmp


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.

#9 fedlix

fedlix
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:04:16 PM

Posted 02 July 2016 - 08:33 PM

the computer just freezes when it crashes while driver verifier is on i have to restart it manually. Im thinking of doing a clean install on windows since this is probably driver related.

Im uploading the minidumps again there is a new one ( not while driver verifier is on tough).

Attached Files


Edited by fedlix, 02 July 2016 - 08:33 PM.


#10 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:07:16 PM

Posted 03 July 2016 - 05:47 AM

The uploaded minidump.zip file is empty.

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/



 


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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users