Windows 10: Unpredictable and random BSODs - Frustration Factor: Chainsaw

Hello, I hope you are well,

Are the BSOD's in Win10 now, "sad screens of death"? :`(

They are making me quite sad, as I have entered dark territory that is beyond my comprehension of computing. I do not know where to start with the ".cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace)" stuff that windows bug check is telling me to do...

I will attach the .zip file and also some examples of the blue screens that I have been getting more and more frequently.

Today, I came in to find the machine was unable to start (it had been on all night, and often breaks after extended idle periods), and after a few reboots, it got to the desktop. The display would flick black, and resume with a small loading icon on the cursor momentarily.

Another reboot cleared this problem, but then came a few different blue screens that I did not recognise (pertaining to, rdr_file_system_error). Attached is a collection of some over the time I've been using Win10. There are more, often daily, but I don't catch all of them. Today it has gotten me really mad, so I'm hoping someone will take the time to help me with this. I did train as an MCSE and CCNA, but this was a long time ago now, and much of this is unfamiliar to me.

Thanks in advance,

Pete

Attachment 35126

:)

 

Nokia E7 won´t start

I bought it in spain (europe) I live in Argentina, (bottom Latin America). Avoiding hardware servicing discuss. Do you think my sim holder could be broken? I could take it to some random electronic service,but I don´t feel confortable leaving it to an
uneducated dude who would try to open it with a hammer and a chainsaw

 

My calendar appointment reminders are not working.

Apologies for not updating this thread... It seemed to work for a while, but eventually the same problem started creeping up and some repeating events would not fire. It's a very unpredictable bug. I've really tried to unravel the conditions that precipitate
a failed event but it seems random.

 

It might be worth adding that, when upgrading from Win7sp1 to Win10, I had some trouble...

Win7 WU was broken. I would fix it occasionally.
I couldn't get Win7 discs to repair WU to download Win10.
Online archive is closed for Win7 iso.
MS download only wants to give me French Win7.
Tried to force WU download of Win10 using CMD; fail.
I pirate Win10 iso of earlier build (not release).
Decide to use Media Creation Tool install instead.
Win10 is installed.
Windows update is fixed (i think, so far...).
Adobe software doesn't crash as much during high memory use or video encoding.
Bioshock2 runs for first time in 4 years.

Anyway - long story short:

It's not a clean install, but an upgrade over a bit of a busted copy of Win7 (that appeared to fix it).



I hope it's not hardware. Removing disc drives doesn't seem to help (I have tried to run windows primary partition on both SSD's), removing half of the RAM doesn't seem to do much other than slow things down a little, and they are all in the right slots.

Sometimes the computer will turn itself on... and when the screen was going black and flicking back on with the loading icon, i started to worry if my machine was being hijacked by someone, who would use its processing time for bitcoin mining or something...

Since these issues have kind of plagued me in other ways ever since I build this machine, back in the 90's - even though all the hardware has changed in it several times, and the operating system has been cleaned and reinstalled and upgraded several times - these errors remain. I have always had the same keyboard - perhaps the keyboard is possessed by the devil, and carrying the curse..?

The most common are BAD_POOL_HEADER, and MEMORY_MANAGEMENT.
I would get these in Win7 as well.

Any ideas anyone?
The stability of the machine is such that it is making it very difficult to work.

 

Do you think it is possible that the BSOD's are caused by the fact that the two pairs of RAM in the machine are at different frequencies..?


Attachment 35130

Additionally, sfc /scannow reported that there were corrupt files and repaired them.
The logs make me even more worried that my machine is being hijacked by dark forces, as they report many permission errors, and duplicate folder owner warnings. I've attached the log so you can see.

The hard drives all pass the short tests using Seatools.

Thank you.

 

Please check {windows partition}\windows\minidump and check if there are any dump files saved.
The zip is empty of dump files.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

 

Thanks axe0, I have done this - when there is something in the folder, I will post it here.

 

Hello,

Please find attached a mini dump from this morning (IRQ_NOT_LESS_THAN_EQUAL: cdrom.sys)

The dmp file suggests code / memory corruption, but i cannot tell where.

The machine had switched on and idled for less than a minute :`(

 

Please use the tool again and upload the zip file, this for up to date information about your system.
Only dump files isn't enough.

 

Hi axe01,

Here is the zip - it contains 2 minidumps.

You guys can't tell what i've been browsing from here..? Just, cos my girlfriend is away so.. you know... I didn't clear my browser yet.

 

There was another crash, but there was no minidump. On checking the settings, it says, "windows might not be able to make a dump file because the paging size is set to less than 1mb".

However, the paging file is system managed on all drives and is currently allocated 13433MB.

This crash today also occoured after the machien was a few moments idling. Sometimes I don't notice it, so I have turned off automatic restart (it was then that windows said about the problem).

 

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window








Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Realtek RT640 NT driver has been flagged, update may be found here
Code: 5: kd> lmvm rt640x64 start end module name fffff800`b7960000 fffff800`b79f3000 rt640x64 (deferred) Image path: rt640x64.sys Image name: rt640x64.sys Timestamp: Wed Apr 01 16:34:31 2015 (551C01F7) CheckSum: 0009D4EA ImageSize: 00093000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

Nvidia Video driver has been flagged, update may be found here
Code: 5: kd> lmvm nvlddmkm start end module name fffff800`b7bd0000 fffff800`b86b8000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Thu Jul 23 02:15:19 2015 (55B03217) CheckSum: 00AAF49B ImageSize: 00AE8000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Thanks for the advice,

The memtest ran for 15 and 1/2 hours, after 4 passes found 0 errors.
I cannot give it any more time than this right now.

Nvidia drivers got to the unloading and loading part of installation, and caused BSOD (.zip attached).

The Realtek drivers were hard to locate.
I saw another guy had similar issues - sorry for posting in his thread (there is nothing in the BSOD forum rules to say, "do not post in another person's thread") - I was hoping that he had found a download.

The drivers cannot be found using term, "RT640 NT". They are Realtek GBE PCIe drivers: here

I am installing the drivers again now.
Hopefully the graphics driver will not cause BSOD on installing again.

 

Posting in others thread isn't against the rules, but I thought you were someone who had a new problem *Redface

Memtest with 4 passes isn't enough for conclusive results, all dump files are pointing to memory corruption.
The graphics drivers are also getting involved, but I'm not sure if it is due to accessing corrupted memory or if there is a problem with the graphics drivers.

 

Hi again,

A different one this time, RDR_FILE_SYSTEM and KERNAL_SECURITY_CHECK failure.

Currently, I am using teamspeak 3. The machine seems to crash more often when this is used, or music is streamed through a browser. I was hoping it was network drivers, but...

I will run the memtest again later, and leave it for a longer time.

Thanks!