Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Intermittent BSODs with no obvious commonality

18 Dec 2014   #11
Saraiguma

Windows 7 Home Premium x64
 
 



Another bluescreen, no memory dump created


My System SpecsSystem Spec
.
18 Dec 2014   #12
Gator

Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
 
 

The last one seems to indicate a disc error

See "Ntfs.sys"

Run extensive tests on your Hard drive with the utility provided by the hard drive manufacturer

Bug Check 0x24


Cause


One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.


To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.
To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.


Also, see here:
Code:
Event[10376]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2014-07-15T12:28:50.978
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Serket
  Description: 
A fatal hardware error has occurred.
Explanation


This error indicates that there is a hardware problem. A machine check exception indicates a computer hardware error that occurs when a computer's central processing unit detects a hardware problem.

Note: WHEA stands for Windows Hardware Error Architecture.

Some of the main hardware problems which cause machine check exceptions include:


  • System bus errors (error communicating between the processor and the motherboard)
  • Memory errors that may include parity and error correction code (ECC) problems. Error checking ensures that data is stored correctly in the RAM; if information is corrupted, then random errors occur.
  • Cache errors in the processor; the cache stores important data and code. If this is corrupted, errors often occur.
  • Poor voltage regulation (i.e. power supply problem, voltage regulator malfunction, capacitor degradation)
  • Damage due to power spikes
  • Static damage to the motherboard
  • Incorrect processor voltage setting in the BIOS (too low or too high)
  • Overclocking
  • Permanent motherboard or power supply damage caused by prior overclocking
  • Excessive temperature caused by insufficient airflow (possibly caused by fan failure or blockage of air inlet/outlet)
  • Improper BIOS initialization (the BIOS configuring the motherboard or CPU incorrectly)
  • Installation of a processor that is too much for your motherboard to handle (excessive power requirement, incompatibility)
  • Defective hardware that may be drawing excessive power or otherwise disrupting proper voltage regulation
User Action

  • Update the BIOS and the drivers for the motherboard chipset.
  • Update all the hardware drivers, if updates are available from your manufacturer.
  • Check the temperature inside the computer to make sure your processor and related peripherals are not overheating.
  • Check the fan on your CPU to make sure it is properly attached to the CPU.
  • If you have overclocked your CPU, reset your settings to the default settings.
  • Make sure you power supply fan is working correctly
My System SpecsSystem Spec
19 Dec 2014   #13
Saraiguma

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by Gator View Post
The last one seems to indicate a disc error

See "Ntfs.sys"

Run extensive tests on your Hard drive with the utility provided by the hard drive manufacturer

Bug Check 0x24


Cause


One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.


To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.
To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.


Also, see here:
Code:
Event[10376]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2014-07-15T12:28:50.978
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Serket
  Description: 
A fatal hardware error has occurred.
Explanation


This error indicates that there is a hardware problem. A machine check exception indicates a computer hardware error that occurs when a computer's central processing unit detects a hardware problem.

Note: WHEA stands for Windows Hardware Error Architecture.

Some of the main hardware problems which cause machine check exceptions include:


  • System bus errors (error communicating between the processor and the motherboard)
  • Memory errors that may include parity and error correction code (ECC) problems. Error checking ensures that data is stored correctly in the RAM; if information is corrupted, then random errors occur.
  • Cache errors in the processor; the cache stores important data and code. If this is corrupted, errors often occur.
  • Poor voltage regulation (i.e. power supply problem, voltage regulator malfunction, capacitor degradation)
  • Damage due to power spikes
  • Static damage to the motherboard
  • Incorrect processor voltage setting in the BIOS (too low or too high)
  • Overclocking
  • Permanent motherboard or power supply damage caused by prior overclocking
  • Excessive temperature caused by insufficient airflow (possibly caused by fan failure or blockage of air inlet/outlet)
  • Improper BIOS initialization (the BIOS configuring the motherboard or CPU incorrectly)
  • Installation of a processor that is too much for your motherboard to handle (excessive power requirement, incompatibility)
  • Defective hardware that may be drawing excessive power or otherwise disrupting proper voltage regulation
User Action

  • Update the BIOS and the drivers for the motherboard chipset.
  • Update all the hardware drivers, if updates are available from your manufacturer.
  • Check the temperature inside the computer to make sure your processor and related peripherals are not overheating.
  • Check the fan on your CPU to make sure it is properly attached to the CPU.
  • If you have overclocked your CPU, reset your settings to the default settings.
  • Make sure you power supply fan is working correctly

I've run chkdsk several times with no errors of any type reported, Samsung claims that their Hutil tool works on my model of drive but the tool itself claims my model is not supported.
I have 12g of physical memory and rarely even approach utilizing it all.
Unless I'm mistaken Services for Macintosh is a tool for Windows servers to allow Apple computers to connect to them and is not applicable here.
All drivers including BIOS are up to date, all fans are fully seated and functional, all temperatures are within manufacturer's specifications, no hardware is overclocked in any way.

Here are two more bluescreens though


My System SpecsSystem Spec
.

19 Dec 2014   #14
Gator

Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
 
 

That post was a copy/paste from the errors you are receiving. Its very difficult to troubleshoot a BSOD without a dump.

You can use Seatools or Western Digitals hard drive testing utilities to test your hard drive for errors.
My System SpecsSystem Spec
19 Dec 2014   #15
cluberti

Windows 10 Pro x64
 
 

The fact that no dump is being created should be a hint, as I mentioned before.....
My System SpecsSystem Spec
19 Dec 2014   #16
Saraiguma

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by cluberti View Post
The fact that no dump is being created should be a hint, as I mentioned before.....
It does seem logical but chkdsk doesn't report any errors and none of the short Seatools tests reported errors though the long test is still ongoing
My System SpecsSystem Spec
19 Dec 2014   #17
cluberti

Windows 10 Pro x64
 
 

I see the potential assumption of a disk or hardware issue, but if you're telling us everything, then it's more likely a driver issue. The only thing running on Windows when a system crashes is the basest of the kernel to handle the bugcheck call and write out RAM to the pagefile, and kernel-mode drivers associated with security software and disk drivers. If you aren't getting a memory dump, and the system is configured with an automatic paging file (so it should be at least 1x RAM in size and on the same volume as the \Windows install), then that eliminates the OS itself (in all likelihood) and leaves system drivers and hardware. Given that you're getting some *really* random bugcheck codes without any real consistency, and if your RAM and hard disks all pass thorough hardware checks, that eliminates that as well and leaves only drivers. Knowing which drivers are still loaded when Windows crashes reduces the possibilities there as well....

Like I said, it's a clue.
My System SpecsSystem Spec
20 Dec 2014   #18
Saraiguma

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by cluberti View Post
I see the potential assumption of a disk or hardware issue, but if you're telling us everything, then it's more likely a driver issue. The only thing running on Windows when a system crashes is the basest of the kernel to handle the bugcheck call and write out RAM to the pagefile, and kernel-mode drivers associated with security software and disk drivers. If you aren't getting a memory dump, and the system is configured with an automatic paging file (so it should be at least 1x RAM in size and on the same volume as the \Windows install), then that eliminates the OS itself (in all likelihood) and leaves system drivers and hardware. Given that you're getting some *really* random bugcheck codes without any real consistency, and if your RAM and hard disks all pass thorough hardware checks, that eliminates that as well and leaves only drivers. Knowing which drivers are still loaded when Windows crashes reduces the possibilities there as well....

Like I said, it's a clue.
The Seatools long test came back clean so this seems increasingly plausible, is there an easy way to test for driver corruption (?) or is it reinstall every driver manually/flatten and reinstall territory?
My System SpecsSystem Spec
20 Dec 2014   #19
Saraiguma

Windows 7 Home Premium x64
 
 



and another BSOD



and this since then which is new to me
My System SpecsSystem Spec
20 Dec 2014   #20
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

How much free disk space do you have on C:?
My System SpecsSystem Spec
Reply

 Intermittent BSODs with no obvious commonality




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Intermittent BSODs over the past few months
Ever since I built this PC I've had BSODs every so often. I've not been able to trace them to any particular source, but lately they seem to be getting a lot more frequent and I am getting fed up, so I figured I would try asking here. I've used the SF Diagnostic Tool to gather the requested...
BSOD Help and Support
Various BSODs, often 3b and ntoskrnl, no obvious reason
I've been having BSODs for a couple of weeks that don't appear to be triggered by anything specific. I finally decided to reformat and start over. I don't know if it helped, but it didn't get rid of them entirely. I reinstalled windows 7 (Ultimate x64) today, a few programs and drivers, and...
BSOD Help and Support
Intermittent BSODs - Please Help!
Alright, finally had another BSOD and have the dump file on it. I am hoping someone can make more sense out of it and pinpoint the issue once and for all so I can get this problem solved (praying it is NOT a hardware problem - been there and done that, don't need to shell out anymore $$$ on it...
BSOD Help and Support
Intermittent BSODs in Vista & 7
Grateful for any help. They happen often enough to make this computer practically unusable, but I haven't been able to isolate what the cause is. Gaming, browsing, sitting idle, sometimes immediately after start up. Sometimes its good for hours under heavy requirements. Occasionally a black...
BSOD Help and Support
Intermittent BSODs, unknown trigger
I'm running Win7 Home Premium x86, my box features the following components: * 4GB RAM * Intel CORE i5-750 / 2.66 GHz * Western Digital 500G Serial ATA Hard Drive * LDVR SATA 22X DVD+/-RW Drive * Radeon HD4350 512M video card I have been experiencing bluescreens on the order of every 4 to...
BSOD Help and Support
NTOSKRNL.sys Intermittent BSODs
I am running Windows 7 Pro 64-bit, it is from the Microsoft Action Pack partnership, so I think it's classified as OEM, but not sure. System is *approx.* 3 years old, except for the GFX card and 2nd HDD (see hardware on my profile if necessary) which are newer. However, the current OS install is...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:27.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App