Loading...
> >

Two Stop Codes in three days

2»

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,864
    kenshaw011267 said:
    Richard Haseltine said:

    There is a message related to the recovery in Event Viewer (which i hadn't remembered to check, thank you for the reminder), though it is cryptic:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000be (0xffffebf240008000, 0x8a00000003c00021, 0xffff850b97eae350, 0x000000000000000b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 5150605f-1235-4ede-bb5b-0b0fd8adc0c2.

    I also seem to have occasional blocks of yellow triangle messages telling me that "Disk # has been surprise removed" running through several numbers, though I've not noticed any access issues (and the blocks of warnings don't coincide with the stop-errors). Scrolling back they seem to start happening, usually once every day or two, at the beginning of July - I don't see any for the second half of June, at which point I stopped scrolling

    How many disks do you have? Does it run through all of them, think of them as 0 = C etc.?

    That it least indicates you might not be having an issue related to a static discharge. If you're getting the error for all your HDD's and SSD's that's one of those not good errors. If it's just for one drive, that's been partitioned or the like that's not nearly as bad. If it's one physical drive run chkdsk /r and then any other drive tests you have (just run that on all your drives anyway although it will take some time). Check the power and data connections (both ends).

    Then check to see if any app has created any ghost drives, I vaguely recall an article about the Xbox app creating fake drives when installing games. This could, I think, cause errors like what you're having.

    The disc errors are from well before the stormy daya, and other issues. The numbers seem to start 5 or 6 up to 13, sometimes skipping one, while the physical drives go from 0 to 4 - so that doesn't look like the errors are the physical drives if they count the same way. Only the boot drive has partitions. I did install the XBox app, in very late June (last chance to sign up for three free months that came with the CPU,) so - although I think there are a few days between installation and start of the blocks of disc errors - that may well be it.

    nicstt said:
    Richard Haseltine said:

    There's no hardware or process listed in the BSOD screen, just the stop code message itself. I was hoping it might be possible to extract the culprit from the data it says it is gathering.

    Now, what I meant to mention is that I did have the system shut down unexpectedly a couple of days before the first error, twice. We had had thunmder storms rumbling around in the far distance but nothing close - the system didn't seem to be getting hot when i checked after the first one - after the second the CD player (on the same circuit) also reset so I assumed it was something external to the house, though the UPS should have blocked that. The real oddity is that in retrospect I'm pretty sure the power light was still on on the PC on the second occasion, even though it was off as far as restarting went. So, that might indicate a hardware issue (UPS?) but it might also have been enough to break a driver or something like that. Very sorry for missing this from my first post.

    I had surge protection and still do, but I forgot to include the phone line in that; it came in through the phone line and fried the motherboard, PSU and router. Just to cheer you up further. I suppose it is possible that a slight surge caused minor damage?

    The ethernet cable from the router to the PC goes through the UPS, and the phone line into the router has a passive surge protector too. I did, many years ago now, lose a router and one of the network ports on the PC to a nearby strike - that PC is otherwise still working I think.

    PerttiA said:
    Richard Haseltine said:

    There is a message related to the recovery in Event Viewer (which i hadn't remembered to check, thank you for the reminder), though it is cryptic:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000be (0xffffebf240008000, 0x8a00000003c00021, 0xffff850b97eae350, 0x000000000000000b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 5150605f-1235-4ede-bb5b-0b0fd8adc0c2.

    I also seem to have occasional blocks of yellow triangle messages telling me that "Disk # has been surprise removed" running through several numbers, though I've not noticed any access issues (and the blocks of warnings don't coincide with the stop-errors). Scrolling back they seem to start happening, usually once every day or two, at the beginning of July - I don't see any for the second half of June, at which point I stopped scrolling

    Two things came to mind as you mentioned thunder...

    Does your motherboard have a backup bios, you could try using that one incase the "primary" one has somehow been damaged

    Do you have external USB devices with their own power sources (transformer or battery), if the voltage levels don't match between the computer and the external device, it can cause miscellaneous problems - The battery overheated and died on my mobile 4G Router and it caused problems in POST, until I caught an error message pointing to USB voltage differencies. Got a new router, but the old one had already done some damage to the "primary" bios, switched to the backup bios and the problems went away.

    Yes, it has a back-up BIOS. I was a little wary of doing anything to the BIOS while there are doubts over stability. The only powered devices connected are speakers (audio jack - they are really old) and the monitor (USB hub). Other than those it's just keybpard, mouse, and Wacom tablet.

    mambanegra said:

    You probably do this already, but it's definitely worth downloading something to watch for SMART errors if you don't have something already. My machine was acting really weird and something in the event viewer hinted to me that it may be disk related (maybe it was the "disk has been removed" error? I really don't remember) I downloaded a tool and found that one of my disks had enough SMART errors to be marked as bad. Even after I removed that disk, I had to scan/repair another disk that had some files get corrupted due to the handful of hard resets that happened. 

    I'll have to check - I have had SMART monitoring in the past but not sure it's on this system. (I don't see the Seagate folder in All programmes so probably needs adding back - though it does sound as if the disc errors may be a red herring.)

  • Richard HaseltineRichard Haseltine Posts: 102,864

    Seatools seems to give the SMART OK, SFC said it found and repaired some corrupt files but I can't figure out which from the log it produced - searching for Repair produces lots of lines about verify and repair service but they don't seem tied to a particular module.

  • nonesuch00nonesuch00 Posts: 18,333

    I had a LED TV ruined somehow from an electrical surge. The house itself wasn't directly struck & the TV and all devices were on surge protectors but apparently the amount of voltage that surge protector let through was still enough to ruin the TV. I guess there might of technically been a huge inductance on the antenna wire without a lightning strike that could of caused it although I've never read of such a thing.

    If a computer was on a UPS though and only it, then that wouldn't be a possibility I'm pretty sure. 

    My current house has primitive non-code standard electrical wiring so I guess everything in my house is a risk. We've had a transformer station within 2 miles get blown in the last 2 year too. I thought it had blown up my monitor as it refused to work for a week but duh, the video cable came loose on me, coincidently at the same time.

  • kenshaw011267kenshaw011267 Posts: 3,805
    nonesuch00 said:

    I had a LED TV ruined somehow from an electrical surge. The house itself wasn't directly struck & the TV and all devices were on surge protectors but apparently the amount of voltage that surge protector let through was still enough to ruin the TV. I guess there might of technically been a huge inductance on the antenna wire without a lightning strike that could of caused it although I've never read of such a thing.

    If a computer was on a UPS though and only it, then that wouldn't be a possibility I'm pretty sure. 

    My current house has primitive non-code standard electrical wiring so I guess everything in my house is a risk. We've had a transformer station within 2 miles get blown in the last 2 year too. I thought it had blown up my monitor as it refused to work for a week but duh, the video cable came loose on me, coincidently at the same time.

    Lopsing a TV through the antenna is very possible. An antenna is basically just a big lightning rod. If you DIY your own TV antenna you need to include what is called a lightning arrester in the line. It's should divert static into ground. Just follow the instructions that come with it (your cable company should have something similar in the line leading to your modem as well).

  • Kev914Kev914 Posts: 1,115
    edited August 2020

    I'm not sure if anyone already suggested this, but have you searched for 0x000000be. I've done that when I've gotten one of those and found information to tell me what the issue was. Some times it tells you what file is causing the issue on the BSOD. Sometimes it's hard to spot it even when it's there. But in the example sited in the link below, there was no file listed.

    I found this website that has some things you try

    Note: I'm not sure if you are allowed to post a link, so I edited my post. I searched for 0x000000be and the first one started with...

    neosmart.net/wiki/0x000000

    if you want to.

    If you have a Dell computer, they have a program called Dell Update which will tell you which drives need updated. Other brands might have a program like that too. You can also go to the manufacters website and look up you pc and check the drivers again the ones you have.

    Post edited by Kev914 on
  • outrider42outrider42 Posts: 3,679
    nonesuch00 said:

    I had a LED TV ruined somehow from an electrical surge. The house itself wasn't directly struck & the TV and all devices were on surge protectors but apparently the amount of voltage that surge protector let through was still enough to ruin the TV. I guess there might of technically been a huge inductance on the antenna wire without a lightning strike that could of caused it although I've never read of such a thing.

    If a computer was on a UPS though and only it, then that wouldn't be a possibility I'm pretty sure. 

    My current house has primitive non-code standard electrical wiring so I guess everything in my house is a risk. We've had a transformer station within 2 miles get blown in the last 2 year too. I thought it had blown up my monitor as it refused to work for a week but duh, the video cable came loose on me, coincidently at the same time.

    Modern TVs are quite sensitive items, they are basically computers. This stuff happens a lot. A surge can get through anything that is connected, not just the power. You can get surges through your signal as well as Ethernet. I've seen Ethernet ports with burn marks on them, but a lot of times you do not see any clear signs of damage. If you know which part failed, that may point to the cause. If the power board board failed, it was likely through the power, if the main board failed it more likely came through a connected device. A lot of times it seems like the connected devices are fine...they just pass the surge through. But sometimes the devices get disabled, or the HDMI ports fail. The device (or TV) may be fine otherwise.

    Most people don't think to place their the signal on protection. Antennas and satellite dishes are literal lightening rods and can easily pass electricity through. It doesn't have to be a direct strike. The air can be quite charged without us being able to see a visible shock. Like static electricity, you feel it, but you do not see it unless it is several thousand Volts, which is plenty enough to kill components. It is less common through cable since such lines are buried, but it can still happen with a cable line, especially if it is not well grounded.

    Surge protectors are only a measure of protection, and they will wear down over time. They need to be replaced periodically. Battery backups are better, assuming it is UPS. But nothing is a guarantee to stop a powerful surge.

  • NylonGirlNylonGirl Posts: 1,939

    Maybe there's a system restore point that predates the first crash.

  • nonesuch00nonesuch00 Posts: 18,333
    kenshaw011267 said:
    nonesuch00 said:

    I had a LED TV ruined somehow from an electrical surge. The house itself wasn't directly struck & the TV and all devices were on surge protectors but apparently the amount of voltage that surge protector let through was still enough to ruin the TV. I guess there might of technically been a huge inductance on the antenna wire without a lightning strike that could of caused it although I've never read of such a thing.

    If a computer was on a UPS though and only it, then that wouldn't be a possibility I'm pretty sure. 

    My current house has primitive non-code standard electrical wiring so I guess everything in my house is a risk. We've had a transformer station within 2 miles get blown in the last 2 year too. I thought it had blown up my monitor as it refused to work for a week but duh, the video cable came loose on me, coincidently at the same time.

    Lopsing a TV through the antenna is very possible. An antenna is basically just a big lightning rod. If you DIY your own TV antenna you need to include what is called a lightning arrester in the line. It's should divert static into ground. Just follow the instructions that come with it (your cable company should have something similar in the line leading to your modem as well).

    Thanks, I had a copper lighting rod but I didn't get it connected in time. I'm not sure it was via the antenna the TV was ruint. It was a very expensive Samsung 40" TV too. 

  • nonesuch00nonesuch00 Posts: 18,333
    outrider42 said:
    nonesuch00 said:

    I had a LED TV ruined somehow from an electrical surge. The house itself wasn't directly struck & the TV and all devices were on surge protectors but apparently the amount of voltage that surge protector let through was still enough to ruin the TV. I guess there might of technically been a huge inductance on the antenna wire without a lightning strike that could of caused it although I've never read of such a thing.

    If a computer was on a UPS though and only it, then that wouldn't be a possibility I'm pretty sure. 

    My current house has primitive non-code standard electrical wiring so I guess everything in my house is a risk. We've had a transformer station within 2 miles get blown in the last 2 year too. I thought it had blown up my monitor as it refused to work for a week but duh, the video cable came loose on me, coincidently at the same time.

    Modern TVs are quite sensitive items, they are basically computers. This stuff happens a lot. A surge can get through anything that is connected, not just the power. You can get surges through your signal as well as Ethernet. I've seen Ethernet ports with burn marks on them, but a lot of times you do not see any clear signs of damage. If you know which part failed, that may point to the cause. If the power board board failed, it was likely through the power, if the main board failed it more likely came through a connected device. A lot of times it seems like the connected devices are fine...they just pass the surge through. But sometimes the devices get disabled, or the HDMI ports fail. The device (or TV) may be fine otherwise.

    Most people don't think to place their the signal on protection. Antennas and satellite dishes are literal lightening rods and can easily pass electricity through. It doesn't have to be a direct strike. The air can be quite charged without us being able to see a visible shock. Like static electricity, you feel it, but you do not see it unless it is several thousand Volts, which is plenty enough to kill components. It is less common through cable since such lines are buried, but it can still happen with a cable line, especially if it is not well grounded.

    Surge protectors are only a measure of protection, and they will wear down over time. They need to be replaced periodically. Battery backups are better, assuming it is UPS. But nothing is a guarantee to stop a powerful surge.

    The TV still turned on but there were very large scattered magenta pink rectangles all over the screen. The TV was thrown out as after that one was bought (in 2008) larger ones became quite inexpensive.

  • Richard HaseltineRichard Haseltine Posts: 102,864
    KevinH said:

    I'm not sure if anyone already suggested this, but have you searched for 0x000000be. I've done that when I've gotten one of those and found information to tell me what the issue was. Some times it tells you what file is causing the issue on the BSOD. Sometimes it's hard to spot it even when it's there. But in the example sited in the link below, there was no file listed.

    I found this website that has some things you try

    Note: I'm not sure if you are allowed to post a link, so I edited my post. I searched for 0x000000be and the first one started with...

    neosmart.net/wiki/0x000000

    if you want to.

    If you have a Dell computer, they have a program called Dell Update which will tell you which drives need updated. Other brands might have a program like that too. You can also go to the manufacters website and look up you pc and check the drivers again the ones you have.

    The thing is, there wasn't actually a code on the stop screen

    NylonGirl said:

    Maybe there's a system restore point that predates the first crash.

    Hmm, that's a thought - though with luck some of the stuff I've done in response to suggestions here will have cleared any software issue 9and with luck that's all there was).

  • kenshaw011267kenshaw011267 Posts: 3,805

    If you haven't had another BSOD since Monday I'd just let it be. If you keep having them then I'd worry.

  • Richard HaseltineRichard Haseltine Posts: 102,864
    kenshaw011267 said:

    If you haven't had another BSOD since Monday I'd just let it be. If you keep having them then I'd worry.

    Unfortunately I did have another just as I was putting the computer into sleep mode this afternoon.

    The WhoCrashed application said:

    On Wed 19/08/2020 16:06:11 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\081920-14953-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
    Bugcheck code: 0xBE (0xFFFF82B900008000, 0x8A00000003C00021, 0xFFFFB204C054D420, 0xB)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    and the same for both earlier crashes - which is mildly reassuring. I could buy the application that reports on issues, but it might be simpler just to reinstall Windows and see if that fixes things; if not I suppose it's time to start buying parts and see which, if any, fixes the issue.

  • mambanegramambanegra Posts: 586

    Did you poke around in event viewer to see how many times this error shows up (it should be in there in some form) and see if there is a common entry always very soon before it? That may point you to the root cause...If you can find that core dump, you may be able to glimpse at a process name that caused it, though, I haven't ever worked with windows cores, only those from unix GCC....many years ago:) Most likely it's binary, but if you can open it up in an editor that doesn't mind binary blobs, you may see some readable text in there. 

  • PerttiAPerttiA Posts: 10,024

    Using the Yandex translator, I checked what the sites in the east were saying... Didn't you tell that you had a Gigabyte motherboard?

    https://generd.ru/fix/oshibka-attempted_write_to_readonly_memory-v-windows-10/

    "Users have reported that the cause of this error is Gigabyte's On/Off software, so if you have This software installed, be sure to uninstall it."
    "Another common cause of BSoD errors may be antivirus software. Users reported that tools such as NoVirusThanks could cause this type of error, and according to them, the problem was resolved after deleting this tool."

  • kenshaw011267kenshaw011267 Posts: 3,805
    Richard Haseltine said:
    kenshaw011267 said:

    If you haven't had another BSOD since Monday I'd just let it be. If you keep having them then I'd worry.

    Unfortunately I did have another just as I was putting the computer into sleep mode this afternoon.

    The WhoCrashed application said:

    On Wed 19/08/2020 16:06:11 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\081920-14953-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
    Bugcheck code: 0xBE (0xFFFF82B900008000, 0x8A00000003C00021, 0xFFFFB204C054D420, 0xB)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    and the same for both earlier crashes - which is mildly reassuring. I could buy the application that reports on issues, but it might be simpler just to reinstall Windows and see if that fixes things; if not I suppose it's time to start buying parts and see which, if any, fixes the issue.

    :(

    As much as I hate to recommend a Windows reinstall, they're such a PITA, that may be your best option. It being consistently the same error instead of random ones leans, IMO, toward it being bitrot in the file over some issue in HW. If it was me I'd give it a shot, or at least try a system restore point if you have one.

  • Richard HaseltineRichard Haseltine Posts: 102,864

    Just a note to say that having reinstalled Windows (if not yet all my appications) I haven't had a recurrence for two weeks, so it looks reasonably safe to think it was a driver or similar file corrupted by the power failures. Thank you all for your help and suggestions, they were very useful in establishing that it probably was a driver issue and that the Windows reinstall might well fix it.

    (Hastily touching wood.)

Sign In or Register to comment.