Yes, there are actual error codes. That will help you figure out what's going.
Did you guys all forget Crowdstrike? On Thu, Aug 28, 2025 at 10:01 AM Adam Moffett <[email protected]> wrote: > Do they still put up a hex error code on the blue screen? I don't suppose > the code reveals anything useful does it? > > Hardware fault and software bug are both always plausible. If there's no > consistent behavior in the event log leading up to the blue screen, then my > guess would be hardware. Disk issues can lead to bluescreen, but I would > assume you'd have logs of other disk read failures and such. Silently > dying without warning and without any error messages would make me think > RAM. I haven't actually had to troubleshoot a PC issue in so long it's all > kind of dusty, but I guess I'd start with wiggling my RAM and any expansion > cards to make sure they're all in there solid. If you have two DIMMS I'd > maybe operate with just one for awhile and see if it stops, then operate > with just the other one for awhile and see if it stops. > > I'm sure you guys went through driver updates and all the other usual > stuff. Maybe a driver *downgrade* is worth trying if you can identify > when the issue started and there's evidence of an update around that time. > Or isn't there a way to roll windows back to an earlier state? I forget > what it's called because I haven't even thought about it since Windows 7, > and I mostly remember turning the feature off to conserve disk space. > > -Adam > > > ------------------------------ > *From:* AF <[email protected]> on behalf of Chuck <[email protected]> > *Sent:* Wednesday, August 27, 2025 7:56 PM > *To:* [email protected] <[email protected]> > *Cc:* [email protected] <[email protected]> > *Subject:* Re: [AFMUG] BSOD > > It was doing it back to back this afternoon. I think it is HW. My son is > thinking OS. > > Sent from my iPhone > > On Aug 27, 2025, at 1:50 PM, Adam Moffett <[email protected]> wrote: > > > I can't even remember the last time I saw a BSOD. > > I do get some glitches in Win11, but blue screen's haven't been a problem. > > > ------------------------------ > *From:* AF <[email protected]> on behalf of Chuck <[email protected]> > *Sent:* Tuesday, August 26, 2025 8:26 PM > *To:* [email protected] <[email protected]> > *Cc:* [email protected] <[email protected]> > *Subject:* Re: [AFMUG] BSOD > > Just a blue screen and reboot. Logs offer no clue. > Sent from my iPhone > > On Aug 26, 2025, at 12:16 PM, Josh Luthman <[email protected]> > wrote: > > > No problems on any of my machines. > > What's the actual error? > > On Tue, Aug 26, 2025 at 2:09 PM <[email protected]> wrote: > > W11 BSOD is driving me crazy. I really don’t want to blame the hardware. > > Is this a thing with a recent W11 update or something? > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
