Windows 7 crashes frequently for no apparent reason

kenneth...@gmail.com

unread,

Jan 23, 2013, 7:31:59 PM1/23/13

to

I am using Windows 7 64-bit on a fairly new HP laptop. Initially things seemed okay but lately Windows gives me the blue screen of death daily, including every single time I lock the screen. I can have our tech support people re-install Windows 7 but I don't want to do that because as a software developer working with PeopleSoft among other things, the last time I had a new OS, it took me about four days to get everything re-installed again and working. Short of that, is there any way I can determine why I keep having Windows crashing because it "encountered an unexpected error"? Thanks.

Ken

Robert Carnegie

unread,

Jan 23, 2013, 9:13:25 PM1/23/13

to

On Thursday, 24 January 2013 00:31:59 UTC, kenneth...@gmail.com wrote:
> I am using Windows 7 64-bit on a fairly new HP laptop. Initially things seemed okay but lately Windows gives me the blue screen of death daily, including every single time I lock the screen. I can have our tech support people re-install Windows 7 but I don't want to do that because as a software developer working with PeopleSoft among other things, the last time I had a new OS, it took me about four days to get everything re-installed again and working. Short of that, is there any way I can determine why I keep having Windows crashing because it "encountered an unexpected error"? Thanks.

When I had random crashes with a previously healthy HP TouchSmart TM2-1010EA,
it turned out to be a fault in memory that I see I described here before as
not detected by the bare BIOS test, but revealed by downloading and booting
from the Linux SystemRescueCD and selecting to run the MemTest86+ utility.
I seem to have not tried the EFI diagnostic because I'd deleted the EFI
partition from the MFT-partitioned disk, and put a downloaded copy on an
SD card instead. That allowed the utilities to run but then I misplaced
the card.

How are your tech support people if it's a matter of replacing a RAM module?

Steve Foster

unread,

Jan 24, 2013, 2:21:26 PM1/24/13

to

Yes, the STOP Code. About 2/3 down the screen during BSOD, W7 reports
the details of the primary reason for the BSOD.

Then you can use an internet search for possible causes: eg "Stop 0x3f".

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net

Jeff Layman

unread,

Jan 25, 2013, 8:25:01 AM1/25/13

to

Anything useful in the Event log?

--

Jeff

Tony Toews

unread,

Feb 11, 2013, 3:38:51 PM2/11/13

to

On Wed, 23 Jan 2013 18:13:25 -0800 (PST), Robert Carnegie
<rja.ca...@excite.com> wrote:

>When I had random crashes with a previously healthy HP TouchSmart TM2-1010EA,
>it turned out to be a fault in memory that I see I described here before as
>not detected by the bare BIOS test, but revealed by downloading and booting
>from the Linux SystemRescueCD and selecting to run the MemTest86+ utility.

There is an option to test memory from within Windows 7. I don't
recall the details of how to get there but basically it restarts your
computer into memory testing mode and chugs away for a while, restarts
back in normal Windows and reports the results.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/