Different msg BSOD every first Startup of each day

[Greewn]

Hi everybody, I have multiple BSODs showing up every first Startup of each day. It only happens the first time I turn on the computer each day and the BSOD messages vary.

Once the BSOD appears I just restart the PC and everything runs smoothly.

I have attached DM generated zip file. Please help

 

[koolkat77]

Welcome to the forum Greewn,

Allot of important info is missing from your zip, please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html to grab all and upload a new report here.

For starters, you could take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

 

[Greewn]

Thank you koolkat, I have uploaded the correct file and left memtest running overnight with no errors reported this morning.

What's next?

 

[koolkat77]

How many passes did you take memtest for?

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO
Perform a Clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Remove Avast! antivirus, use MSE instead.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability
compared to other antivirus or internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes: Removes malware including viruses, spyware, worms and trojans, plus it protects your computer
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

 

[Greewn]

ok koolkat i have tried every step with no success. i have uploaded a more recent dump collection. where do we go from here?

 

[koolkat77]

What about the RAM.

How many passes of memtest did you take.

 

[Greewn]

8 passes overnight.

Is it helpful if I write down each BSOD that shows up everyday? (There are like 3 or 4 recurring ones) Or can you see that info in DUMP files?

 

[Arc]

Hi.

The BSODs are highly indicating that something is going wrong with the hardware environment, and RAM is the primary suspect.

BugCheck 3B, {c0000096, fffff880018697ba, fffff880040a3a00, 0}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff880040a3a00 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_stride

FAILURE_ID_HASH:  {54f6a81e-bd17-9afc-f167-0352818951c1}

Followup: memory_corruption
---------

BugCheck 50, {fffff50013803112, 0, fffff80003287eb8, 7}


Could not read faulting driver name
[COLOR=Red]Probably caused by : hardware[/COLOR] ( nt!KiCheckForKernelApcDelivery+14 )

Followup: MachineOwner
---------

BugCheck D1, {72, a, 1, fffff880010a1ea6}

[COLOR=Red]Probably caused by : atapi.sys [/COLOR]( atapi!AtapiHandleAtaCommand+a )

BugCheck 50, {fffff87ff724f86d, 1, fffff8800124f7b6, 5}

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

Followup: memory_corruption
---------

fffff880`0378e410 fffff880`010b381f ataport!IdeDispatchChannelRequest+0xef
fffff880`0378e440 fffff880`010b3684 ataport!IdeStartChannelRequest+0x113
fffff880`0378e4c0 fffff880`010b4a16 ataport!IdeStartDeviceRequest+0x2c4
fffff880`0378e580 fffff880`010b04ee ataport!IdePortPdoDispatch+0xb6
fffff880`0378e5b0 fffff880`00f1f7a7 ataport!IdePortDispatch+0x16

If memory is tested good, do two more things.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And, there is one possible BIOS update to your motherboard. BIOS Update [JGIBX10J.86A]. Plan to apply it.

As hardware is reported as a probable cause, do some more hardware tests.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Test the HDD using Data Lifeguard Diagnostic for Windows. Take bot the short test and the extended test.

Let us know the results.

 

[Greewn]

Thank you arc for your input, I will look into it.