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

BSODs Often every single day.


  • Please log in to reply
5 replies to this topic

#1 hasai

hasai

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:42 AM

Posted 29 June 2016 - 01:15 AM

Hello everyone, i've been having a lot of issues with my pc for awhile now and it feels like its been getting worse =/. Here are some of the info from the dump files.
I have been trying to figure out a solution for so long now, hopefully someone here can fix it for me :( thanks 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 6/29/2016 5:38:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062816-6281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801AD53BF85, 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 Wed 6/29/2016 5:17:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062816-4234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB84F2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8024E8CD4F2, 0xFFFFD00020F8E7D8, 0xFFFFD00020F8DFE0)
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 Wed 6/29/2016 5:17:16 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: brdriver64.sys (BRDriver64!BRfFileTruncated+0x1B51)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8024E8CD4F2, 0xFFFFD00020F8E7D8, 0xFFFFD00020F8DFE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: brdriver64.sys .
Google query: brdriver64.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Wed 6/29/2016 5:07:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062816-4390-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x745CF)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8007C15F5CF, 0xFFFFD00113A85A88, 0xFFFFD00113A85290)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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 Wed 6/29/2016 4:59:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062816-4171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x1A (0x41284, 0xFFB001EC440000, 0x70D, 0xFFFFF79940000000)
Error: MEMORY_MANAGEMENT
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 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.



On Wed 6/29/2016 4:57:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062816-4328-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6A6D6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8001C31C6D6, 0xFFFFD000C190DF80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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 Wed 6/29/2016 4:30:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062816-4140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8003F2CD948, 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 Mon 6/27/2016 3:38:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062616-8843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8005726B0DF, 0xFFFFD000274A9B30, 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 Fri 6/24/2016 12:17:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062316-4078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x18 (0xFFFFE000F95EFAB0, 0xFFFFE00102C1DE20, 0x1, 0x8000000000000000)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.



On Thu 6/23/2016 11:55:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062316-4046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000C3FE12F0, 0xFFFFD000C3FE1248, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

44 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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)
brdriver64.sys 
 



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:42 PM

Posted 29 June 2016 - 06:52 AM

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.

#3 hasai

hasai
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:42 AM

Posted 29 June 2016 - 07:40 PM

there you go, i recently frefreshed my windows again just to see if it would make a difference and updated all my stuff again back to the latest stuff, but not even 15 mins after i refreshed i got a bsod again, thats why you'll only see 3 minidump files there, i can update the minidump if you need more information once i get more bsods, thanks for the help. Also before the fresh i had issues when i did the sfc /scannow and using the dism restore health thing to fix my stuff but it didnt work, i scanned again after refreshing windows and it says there were no integrity violations, still getting bsods though...Should have checked this post before i refreshed so i could have given better information

Attached Files


Edited by hasai, 29 June 2016 - 07:50 PM.


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:42 PM

Posted 02 July 2016 - 08:06 AM

Your UEFI/BIOS (version 0704) dates from 2015.  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.

No Windows Update hotfixes installed.  Most systems have 180 or more.  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).

This device needs to have it's drivers installed:

 

SM Bus Controller    PCI\VEN_8086&DEV_8CA2&SUBSYS_85341043&REV_00\3&11583659&0&FB    The drivers for this device are not installed.

This most likely belongs to the chipset drivers for your system.  Please download them from the manufacturer's support website and install them.

 

Beyond these things, this seems to be a hardware problem to me (could also be a compatibility issue or a low-level driver problem).
Please start with these free, hardware diagnostics:  http://www.carrona.org/hwdiag.html

If these tests reveal nothing, then please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Analysis:

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

**************************Wed Jun 29 20:17:05.073 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062916-3921-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
System Uptime:0 days 0:00:01.701
Probably caused by :memory_corruption ( nt!MiPfPutPagesInTransition+406 )
BugCheck A, {390002947440, 2, 1, fffff801aa128f26}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000390002947440, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff801aa128f26, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: AV_nt!MiPfPutPagesInTransition
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun 29 20:13:32.919 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062916-5968-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
System Uptime:0 days 0:01:35.547
Probably caused by :dxgmms1.sys ( dxgmms1!VidMmInterface+18553 )
BugCheck 1000007E, {ffffffffc0000005, fffff80001434503, ffffd000221065e8, ffffd00022105df0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80001434503, The address that the exception occurred at
Arg3: ffffd000221065e8, Exception Record Address
Arg4: ffffd00022105df0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: AV_dxgmms1!VidMmInterface
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3998
  BIOS Version                  0704
  BIOS Release Date             05/20/2015
  Manufacturer                  ASUS
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  All Series
  Baseboard Product             Z97-E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun 29 20:11:28.598 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\062916-5203-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
System Uptime:0 days 0:30:47.226
Probably caused by :Ntfs.sys ( Ntfs!NtfsWriteLog+593 )
BugCheck 24, {b500190637, ffffd000291b3c58, ffffd000291b3460, fffff8000098be83}
BugCheck Info: NTFS_FILE_SYSTEM (24)
Arguments:
Arg1: 000000b500190637
Arg2: ffffd000291b3c58
Arg3: ffffd000291b3460
Arg4: fffff8000098be83
PROCESS_NAME:  brwc.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsWriteLog
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3998
  BIOS Version                  0704
  BIOS Release Date             05/20/2015
  Manufacturer                  ASUS
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  All Series
  Baseboard Product             Z97-E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




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:

**************************Wed Jun 29 20:17:05.073 2016 (UTC - 4:00)**************************
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
nvlddmkm.sys                Fri Jan  9 17:22:06 2015 (54B0548E)
e1d64x64.sys                Tue Nov 24 14:10:54 2015 (5654B63E)
TeeDriverW8x64.sys          Thu Dec 24 11:24:00 2015 (567C1C20)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jun 29 20:13:32.919 2016 (UTC - 4:00)**************************
nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
nvvadarm.sys                Fri Jan  9 17:40:31 2015 (54B058DF)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
NvStreamKms.sys             Fri Jun  3 07:28:21 2016 (575169D5)


http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=e1d64x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys


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 Stafeegraph

Stafeegraph

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:09:12 AM

Posted 05 July 2016 - 04:32 AM

 

Hi BSODS can be solved by following ways:

  1. Open your System Properties. ...
  2. Click Advanced System Settings. ...
  3. Click the Settings button in the Startup and Recovery section of the Advanced tab.
  4. Uncheck the “Automatically restart' option under the “System failure' section.

 

Determine if you changed anything recently. The most common cause of the Blue Screen is a recent change in your computer’s settings or hardware. This is often related to new drivers getting installed or updated. Drivers are software that allow your hardware to communicate with Windows. If you have a restore point, try to load it and see if it helps, it may or may not.

·         Because there are essentially an infinite number of hardware configurations possible, drivers can’t be tested for every possible setup. This means that sometimes a driver will be installed that causes a critical error when communicating with the hardware.

·         Check your computer’s internal hardware. Sometimes, a poor connection inside the computer can cause a Blue Screen. Open your case and check to make sure that all the cables are firmly connected and that any cards are seated firmly in their sockets.

o    This is more difficult for laptops. You can check the hard drive and the RAM to make sure that they are connected properly. Remove the panels in the back that cover the hard drive and RAM with a small Phillips-head screwdriver. Press the components firmly into their connections.

o    Check your computer’s temperature. Overheating can lead to your hardware malfunctioning. One of the most common components to overheat is the graphics card. The second most likely culprit is the CPU.

§  You can check temperatures in most BIOS menus, or through software in Windows.

§  Test your hard drive. Run the “chkdsk” function on your hard drive to scan for errors and fix potential problems. A failing hard drive can cause Blue Screens due to corrupted files. To run chkdsk, open Computer/My Computer and right-click the disk that you want to scan. Select Properties.

§  From the Properties screen, select the Tools tab.

§  Click Check Now in the Error Checking section. Your computer will prompt you to restart in order to scan the disk.

§  Strip your computer down to the essentials. One way to narrow down what is causing the problem is to remove everything that is not essential for the PC to run. This way, if the error goes away, you know that it was one of the pieces that you disconnected.

§  A desktop computer needs the motherboard, CPU, a hard disk, power supply, RAM, and a keyboard. Plug your monitor into your motherboard’s monitor port (if it has one) so that you can disconnect the graphics card. Everything else can be removed during the diagnostic process.

§  If the computer runs fine after stripping it down, add one part back at a time until the error message appears again. This will let you know which device is causing the computer to crash.

§  This method does not apply to laptops, as you cannot strip it down.

 

 

 

Test your RAM. A common culprit in system crashes is a bad stick of RAM. When RAM fails, it causes the system to become unstable. You can test your RAM by using a program called “memtest86”. This program is available for free online, and is run by burning it to a bootable CD.

·         Reboot your computer and run the program. The memtest software will automatically begin running tests on your computer’s RAM. This may take several minutes to complete. For best results, allow several passes of the test to be completed. Memtest will run indefinitely until you stop it yourself.

 



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:42 PM

Posted 06 July 2016 - 06:48 AM

A few comments on Stafeegraph's excellent post:

 

Here's the frequency of BSOD's:
- 3rd party drivers (over 90% of BSOD's are due to this)
- hardware (less than 10% of BSOD's are due to this)
- Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).
 

You can use Driver Verifier to test your drivers.  While not 100% effective, if it's a 3rd party driver try the suggestions here:  http://www.carrona.org/verifier.html

 

Remove the battery (on a laptop) and remove the power cord from the computer (desktop or laptop) before opening the case.  Ground yourself before touching anything inside the case.

 

CHKDSK does not test the hard drive, it tests for errors in the file system on the hard drive (NTFS, FAT32, etc).  It is possible to have a failing hard drive without issues showing up in CHKDSK

Run the manufacturer's diagnostics.  If in doubt, run Seagate Seatools on the hard drive(s):  http://www.carrona.org/hddiag.html

SMART attributes are helpful, but are not 100% reliable.  That being said, they're about all you'll have if you're using an SSD (there's generally no hardware tests for SSD's).

 

"Strip your computer down to the essentials"  I have a procedure for that here:  http://www.carrona.org/strpdown.html

 

RAM....

I have found that MemTest86/86+ are great tools.  But occasionally at work we'll find that a system passed MemTest, yet fails Prime95's Blend test.  And sure enough, replacing the RAM in those instances fixes the problem.

Just recently I encountered a system that passed both MemTest86+ and Prime95's Blend test - and swapping the RAM actually fixed it also.  I have only seen this once in all my years of working on systems.

My first suggestion is to try swapping the sticks around as suggested on this page:  http://www.carrona.org/memdiag.html


Edited by usasma, 06 July 2016 - 06:50 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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users