Solved BSOD watching stream error 0X0000010E

[Danaeris]

Hi, new to this forum, been getting BSOD's for quite some time and figured this would be a good place to get some help.

Last BSOD I had was error 0X0000010E, I've attached 2 DM Log Collector files for the last 2 BSOD's I've had, the BSOD's tend to vary each time I don't get the same one constantly. Any help would be greatly appreciated.

Possibly related, windows will try to install 110 updates upon shutdown, when starting up the comp it will try to configure the updates, after several minutes, it will fail and revert the changes every time.

 

[Danaeris]

Another BSOD today. refering to IRQ not less or equal.

 

[koolkat77]

Kaspersky is contributing to the BSOD's. Please uninstall and replace with MSE.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

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.

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

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

Upload a screenshot of your hard disk using Crystal Disk Info.

 

[Danaeris]

Hi, thanks for the suggestions. I have removed Kaspersky and replaced with MSE and Malwarebytes. Performed a clean boot and removed most of the startup items.
System File Checker turns shows no integrity violations.

The SSD in this comp is brand new, and I was getting the BSOD's before my previous was replaced so I doubt it's a HDD issue.

I have attached the crystaldiskinfo screenshot as requested regardless. I will try this for a few days and if I get any more BSOD's I'll add it here, thank you.

 

[Danaeris]

Seems I'm still getting BSOD's after doing as you suggested. Kaspersky is no longer on my system and I'm running few processes. Error 0x00000019 Bad Pool Header

 

[Danaeris]

another last night during computer shutdown.

 

[koolkat77]

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.

 

[Danaeris]

Ran Memtest86+ for 8 passes with all sticks in with no errors. Should I run it with each individual stick in a time for 6 passes each also?

 

[koolkat77]

We'll pause memtest.

Any new BSOD?

 

[Danaeris]

New BSOD just now. IRQ not less or equal, refered to dxgmms1.sys

 

[Danaeris]

Another one this morning.

 

[Danaeris]

Another one today.

 

[koolkat77]

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

SPTD Removal:

• 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.
• DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO

[FONT="Lucida Console"]Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Nov  9 08:55:32.332 2014 (UTC + 6:00)
System Uptime: 0 days 0:06:52.534
BugCheck 116, {fffffa800d3aa010, fffff8800fdcec84, ffffffffc000009a, 4}
*** 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+91dc84 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu Nov  6 23:14:41.692 2014 (UTC + 6:00)
System Uptime: 0 days 8:16:09.520
BugCheck 50, {fffff0a0035f46d8, 0, fffff80002ffd127, 7}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+517 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue Nov  4 17:07:29.553 2014 (UTC + 6:00)
System Uptime: 0 days 2:43:34.755
BugCheck 1000007E, {ffffffffc0000005, fffff88001a11314, fffff880032c0508, fffff880032bfd60}
*** WARNING: Unable to verify timestamp for SamsungRapidDiskFltr.sys
*** ERROR: Module load completed but symbols could not be loaded for SamsungRapidDiskFltr.sys
Probably caused by : SamsungRapidDiskFltr.sys ( SamsungRapidDiskFltr+11314 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue Nov  4 00:36:00.443 2014 (UTC + 6:00)
System Uptime: 0 days 1:37:47.270
BugCheck 50, {fffff8a20277a200, 0, fffff8800768deb0, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Nov  2 06:29:41.893 2014 (UTC + 6:00)
System Uptime: 0 days 9:59:04.721
BugCheck 119, {7000000, fffffa8012799410, fffffa805cae4af0, fffffa805772de90}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
BUGCHECK_STR:  0x119
PROCESS_NAME:  Wow-64.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

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

Uninstall any Samsung related software for testing purpose, as you can see its causing BSODs.

Driver Reference Table

Revo Uninstaller:

Use Revo Uninstaller to uninstall stubborn software.

• Download and install the software
• Opt for Advance Mode while uninstalling which allows you to remove leftover registry.
• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Make scans with the following:

Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Hard Drive Diagnostics

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.

 

[Danaeris]

Done a clean boot, ran scannow, ran hard drive diagnostics and seatools on all drives. All tests completed with no errors. There's a crystaldiskinfo screenshot on my drive with windows on in the previous page of this thread, do you need ones of my other drives also?
Also ran Kaspersky TDDSKiller and ESET.

Latest BSOD attached.
New BSOD Log added

 

[Danaeris]

Another one today log file attached

 

[Arc]

Three totally different BSODs in a very short span. So memory becomes the primary suspect.

[COLOR=Red]BugCheck 119[/COLOR], {7000000, fffffa801103f410, fffffa80125a8010, fffffa8011d3c470}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )

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

[COLOR=Red]BugCheck A[/COLOR], {fffff88000bf2730, 2, 1, fffff80002ed9343}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+433 )

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

[COLOR=Red]BugCheck 1A[/COLOR], {41201, fffff6800048eb00, f250000188d32867, fffffa8011b3dbc0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )

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

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

 

[Danaeris]

I have already ran memtest86+ for as requested 8 passes as to a request by koolkat77 Arc, and had zero errors. Do I need to run this again or for more passes?

 

[Arc]

No memory error still so many different bugchecks? Well, let us try to minimize some other possibilities.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[Danaeris]

Ran stress test and benchmark with furmark
ran stresstest with prime95 (max CPU temp 73˚C)
temps on speccy screenshot.

Not overclocking on anything.

 

[Arc]

All is OK. Still there is so many versatile bugchecks!

We should take a drastic step at this point. Let us go for a clean reinstall, to make it sure that a corrupt OS installation is not the source of the issue.

http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

If the issue continues even after performing a clean reinstall, we will have some very minimum hardware components to blame for those BSODs which we cannot take in hand.