BSOD Intermittent Problem

[MIKEKAHN]

Dear Forum Fellows;
For last 3 months I am having BSOD problem intermittently. After the BSOD I restart the computer in safe mode followed by a normal re-start. System works for several days then all of a sudden I get BSOD.
I re-installed the OS two months ago I re-installed the OS (Windows 7 Home Premium x64). It was a full install. System worked without any problem but today again I confronted with BOD. I got the following error message:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 20
BCP1: 0000000000000000
BCP2: 000000000000FFFF
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


I have attached a ZIO file that contains Windows_NT6_BSOD_jcgriff2 and PERFMON HTML.

System Info:
Computer: Gateway Desktop
Age: 3 years
OS: Windows 7 Home Premium x64
Fresh full reinstall of OS about two months ago.

Please help.

 

[HonorGamer]

Hello MIKEKAHN! Welcome to SF!

Well looking at the crash files it seems you have Daemon Tools installed. Please uninstall these tools as it is a common reason for BSODs.

I also noticed that your display drivers are out of date.

Your version: 8.15.10.2555
Newer Version: 9.3.0.1019

Update here:
http://downloadcenter.intel.com/Det...sion=Windows 7 (64-bit)*&DownloadType=Drivers

You roughly have about 87 windows updates. The amount of updates roughly range from 75-105. So try a Windows update.

After doing the following, Please post back results!

 

[writhziden]

It is difficult to reach any true conclusions without your .dmp files. Make sure they are configured properly to create minidumps: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html -> OPTION ONE step 6. or OPTION TWO step 2. should allow you to get minidumps. Also refrain from using any disk cleanup utilities for the duration of troubleshooting as they can delete the .dmps we need for analysis.

From $evtx_sys_dump.txt:

Event[139]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-07-20T23:12:08.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="Red"]0x00000020[/COLOR][/B] (0x0000000000000000, 0x000000000000ffff, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072012-18704-01.

Event[2600]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-06-27T21:05:28.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x0000004e[/COLOR][/B] (0x000000000000009a, 0x0000000000085846, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Event[11571]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-06-24T12:29:32.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x0000000a[/COLOR][/B] (0x0000005000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80002f10cf2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062412-43836-01.

Event[11794]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-06-24T11:12:07.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x0000009f[/COLOR][/B] (0x0000000000000004, 0x0000000000000258, 0xfffffa80054f9660, 0xfffff80000b9c4d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062412-31137-01.

Event[12156]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-06-23T23:37:02.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="Red"]0x00000050[/COLOR][/B] (0xfffffa854a484a30, 0x0000000000000000, 0xfffff80002f030d9, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062312-38501-01.

Event[14154]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-06-02T22:56:59.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x00000119[/COLOR][/B] (0x0000000000000001, 0x0000000000001500, 0x00000000000015bf, 0x00000000000015be). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060212-21309-01.

Event[15201]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-06-02T13:52:09.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x000000d1[/COLOR][/B] (0xfffffff880047f30, 0x0000000000000002, 0x0000000000000000, 0xfffff880033eed0a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060212-22807-01.

Event[15245]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-05-31T20:52:34.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x0000001e[/COLOR][/B] (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053112-28860-01.

Event[15882]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-05-29T22:01:43.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x0000000a[/COLOR][/B] (0x000000e800000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80002b13d22). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Event[16446]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-05-28T09:23:11.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="red"]0x0000000a[/COLOR][/B] (0x0000002000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80002b12d22). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052812-32136-01.

Event[17275]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-05-27T21:36:32.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DRMASOODKHAN-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: [B][COLOR="Red"]0x0000001a[/COLOR][/B] (0x0000000000005001, 0xfffff70001080000, 0x0000000000019fa9, 0x00019dacffffff50). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052712-17784-01.

As you can see, you have a variety of different BugCheck codes (the codes highlighted in red). The commonality between them is a hardware problem (likely memory incompatibility or faulty memory, but it could be something else) or a driver issue. Updating your graphics driver is a good first step, as outlined by HonorGamer.


If you are interested in looking up the BugCheck codes, usasma provides information about them on his site. Read what the usual causes are and see what is common between most of the BugCheck codes:

STOP 0x00000020: KERNEL_APC_PENDING_DURING_EXIT
STOP 0x0000004E: PFN_LIST_CORRUPT
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
STOP 0x00000119: VIDEO_SCHEDULER_INTERNAL_ERROR
STOP 0x100000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
STOP 0x0000001A: MEMORY_MANAGEMENT​

First, we should check the memory. Then drivers.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• Check memory compatibility:
  Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.​
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 222633
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

Before you run Verifier, make sure your .dmps are properly enabled as described at the top of this post. Also, Verifier should run for 24-36 hours before you upload the crash reports here. 36 hours is preferable so there are more .dmps to find a pattern with.

 

[MIKEKAHN]

My dear HonorGamer & Writhziden
Thank you much for your prompt attention to my request. I will follow your recommendations and report the results when available.

Thanks again.