STOP: 0x0000001A ???

[Bee9ner]

I am receiving this BSOD time & time again:

STOP: 0x0000001A (0x0000000000041284, 0x0000000005628001, 0x0000000000000EBD, 0xFFFFF7000108000)

Can anyone isolate what is triggering this reoccuring.

I blew out dust, removed one ram card, swapped, cleaned area, system restored, memtested, purchased new ram, updated vid card driver, removed new programs, all after a fresh install of w7 x64.
At times, it has no problems for days.
Today, left it alone after a few BSODs an restarts so nothing I am actively doing has triggered it today 3-5xs.

Appreciate any guidance in the right direction, thanks.

Edit:

Latest bsod in order to currently update the thread after waiting a while and trying to use IE:

1A (x41284 again, xFFFf8A0069cc001, 000000000000c878, xFFFFF781c000000)

& once more about 2 hrs after the op, triggered after I shut down IE
1A (x00000000061940, x0000000000147000, 0000000000000000, 0000000000000)

Any help appreciated.
Thanks in advance.

 

[johnbl]

the error 0x41284 = A PTE or the working set list is corrupted.
the error 0x061940 = A PDE has been unexpectedly invalidated.
https://en.wikipedia.org/wiki/Page_table

the problem is going to be in your virtual memory subsystem or maybe power problems to the processor.
I would update the BIOS, update the motherboard sata drivers, you might check the drive data cables or move the data cable to a second controller if your machine had two sata controllers.
if you can, you might update firmware on SSD, turn off special cacheing on HDD

otherwise you have to turn on debug flags, change the memory dump type to kernel, hit a bugcheck, copy the memory.dmp file to a server, share it as public, post a link to it and find someone to take a look at it with a windows debugger. kind of a painful process because most people don't know what to look for in the debugger.

 

[johnbl]

you need to change your memory dump type from minidump to kernel memory dump. Copy the c:\windows\memory.dmp file to a cloud server like Microsoft one drive, share the file as public, then post a link to your shared file. I can look at the diagnostic dump in a windows debugger and get an idea as to why windows shut down the system.

the error codes you send via pm, still indicate that something is wrong with your virtual memory. (the data structures that map locations in your c:\pagefile.sys to physical ram locations is being corrupted)

this can be a bad driver, a bios version that does not match your sata driver version, it could be malware attacking the pagefile.sys. It could be bugs in firmware of the actual drive. It could be a separate unrelated driver overwriting another drivers memory and causing corruption. I have even see this with bugs in BIOS sleep calls. You can not tell with out looking at the memory dump, even then there is a lot of guesswork until you turn on debugging flags.

 

[Deleted member 1898488]

0x0000001A looks like bad ram (that happened to me and ram was the troublemaker)

Quote from microsoft: "The main possible cause of all of those is memory probems though there can be other causes."

 

[johnbl]

windows is a paging operating system, it uses virtual memory a process where a block of data in RAM is copied to the hard drive (pagefile.sys) in this case the mapping between the RAM locations and the place it was copied to inside the pagefile.sys was corrupted. It could be a problem with RAM, but it can also be anywhere in the storage system or even a virus attempting to make modifications to the pagefile.sys or to modify the data contained in RAM.
generally when there is a RAM timing error in BIOS or defective RAM, you will get a different error sub code (0xc0000005) that just indicated a bad memory address being used.
in this case the windows memory manager reported a error that would indicate that a device was expectantly invalidated.
This can happen for a lot of reasons now that devices tend to share a common interface like the PCI/e
You can have a video card break because of a USB device with a bad driver. All because they share a common interface.

0x0000001A looks like bad ram (that happened to me and ram was the troublemaker)

Quote from microsoft: "The main possible cause of all of those is memory probems though there can be other causes."