kernel mode heap coruption BSOD

I got a kernel mode heap coruption BSOD

I was asleep for 4 hours and when I awoke, the PC had rebooted.

https://www.google.com/search?client...heap+coruption

It's the first time so it's no big deal. Not unless it keeps happening.

But still, any suggestions?

One page or more said a driver problem. How could I need a new driver
when nothing has changed? (Maybe I get that: They changed windows and
now a good driver isn't good enough? Though I don't think I've even had
a windows change for quite a while.)


THE ONLY THING I CAN THINK OF, I have a hard drive dock that I turned
off. I didn't run USB Safely Remove or anything else first, but I
hadn't used the drive since I rebooted earlier. Is there any reason to
remove a drive that's not been used before turning it off?

On 6/7/2020 11:24 PM, micky wrote:
I got a kernel mode heap coruption BSOD

I was asleep for 4 hours and when I awoke, the PC had rebooted.

https://www.google.com/search?client...heap+coruption

It's the first time so it's no big deal. Not unless it keeps happening.

But still, any suggestions?

One page or more said a driver problem. How could I need a new driver
when nothing has changed? (Maybe I get that: They changed windows and
now a good driver isn't good enough? Though I don't think I've even had
a windows change for quite a while.)


THE ONLY THING I CAN THINK OF, I have a hard drive dock that I turned
off. I didn't run USB Safely Remove or anything else first, but I
hadn't used the drive since I rebooted earlier. Is there any reason to
remove a drive that's not been used before turning it off?


I wouldn't worry about it, if it were just the first time. Download the
Bluescreenview program and it will show you which modules were
responsible for the BSOD, assuming that you had kernel dumps enabled.
When you find out which driver may have been responsible, then you can
go search for a newer version of that.

Blue screen of death (STOP error) information in dump files.
https://www.nirsoft.net/utils/blue_screen_view.html


Yousuf Khan

On 06/07/2020 09:33 PM, Yousuf Khan wrote:
On 6/7/2020 11:24 PM, micky wrote:
I got a kernel mode heap coruption BSOD

I was asleep for 4 hours and when I awoke, the PC had rebooted.

https://www.google.com/search?client...heap+coruption

It's the first time so it's no big deal.

It's a Big Deal. If my Linux did that, I'd try a different kernel, then
a different Linux distro.

Not unless it keeps happening.

But still, any suggestions?

The smart guy here says that Win10 wallpaper crashes.

One page or more said a driver problem. How could I need a new
driver when nothing has changed? (Maybe I get that: They changed
windows and now a good driver isn't good enough? Though I don't
think I've even had a windows change for quite a while.)

THE ONLY THING I CAN THINK OF, I have a hard drive dock that I
turned off. I didn't run USB Safely Remove or anything else first,
but I hadn't used the drive since I rebooted earlier. Is there
any reason to remove a drive that's not been used before turning it
off?


I wouldn't worry about it, if it were just the first time.

Depends on what the pc is trusted to do for up to 4 whole hours unattended.

micky wrote:
I got a kernel mode heap coruption BSOD

I was asleep for 4 hours and when I awoke, the PC had rebooted.

https://www.google.com/search?client...heap+coruption

It's the first time so it's no big deal. Not unless it keeps happening.

But still, any suggestions?

One page or more said a driver problem. How could I need a new driver
when nothing has changed? (Maybe I get that: They changed windows and
now a good driver isn't good enough? Though I don't think I've even had
a windows change for quite a while.)


THE ONLY THING I CAN THINK OF, I have a hard drive dock that I turned
off. I didn't run USB Safely Remove or anything else first, but I
hadn't used the drive since I rebooted earlier. Is there any reason to
remove a drive that's not been used before turning it off?

There are autonomous things using the disk, even if
you aren't.

The error suggests something happened in Ring0. The
kernel and drivers live down there. Does your AV
live there ?

Someone got that error, with a mixture of a new
version of Dropbox.exe and Symantec Endpoint Protection.
And the latter is an enterprise tool for protecting
corporate PCs.

Games also seem to trigger it (NVidia driver).

There's Reliability Monitor and Eventvwr.msc to look at...

Paul

In alt.comp.os.windows-10, on Sun, 7 Jun 2020 22:29:55 -0700, Corvid
wrote:

On 06/07/2020 09:33 PM, Yousuf Khan wrote:
On 6/7/2020 11:24 PM, micky wrote:
I got a kernel mode heap coruption BSOD

I was asleep for 4 hours and when I awoke, the PC had rebooted.

https://www.google.com/search?client...heap+coruption

It's the first time so it's no big deal.

It's a Big Deal. If my Linux did that, I'd try a different kernel, then
a different Linux distro.

Not unless it keeps happening.

But still, any suggestions?

The smart guy here says that Win10 wallpaper crashes.

Alas, I don't use wallpaper. ;-(

One page or more said a driver problem. How could I need a new
driver when nothing has changed? (Maybe I get that: They changed
windows and now a good driver isn't good enough? Though I don't
think I've even had a windows change for quite a while.)

THE ONLY THING I CAN THINK OF, I have a hard drive dock that I
turned off. I didn't run USB Safely Remove or anything else first,
but I hadn't used the drive since I rebooted earlier. Is there
any reason to remove a drive that's not been used before turning it
off?


I wouldn't worry about it, if it were just the first time.

Depends on what the pc is trusted to do for up to 4 whole hours unattended.

More or less nothing. I leave it running most nights and this is the
first problem. First BSOD in a couple years, since it complained
several times about the RAM. I replaced (and increased) the RAM and
that went away.