Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 6.1.7601.2.1.0.768.3 locale id 2057

17 Mar 2015   #1
DJohnE

Windows 7 Home Premium 64bit
 
 
BSOD 6.1.7601.2.1.0.768.3 locale id 2057

After years of stable operation, I've had several BSODs in the space of a few days. The code is:-

6.1.7601.2.1.0.768.3 locale id 2057

There does not seem to be a pattern - the first one occurred when I wasn't even touching the computer and (I think) the only application running at the time was IE11. Subsequent crashes have occurred while I was using it, but I wasn't doing the same thing each time.

The only warning of trouble was that for a week or two - with increasing frequency - IE kept telling me it had to close and reopen (though it seemed to give the message without actually doing so).

I've not installed any hardware or new drivers recently (other than to uninstall/reinstall my printer driver because there seemed to be a problem with it AFTER the first crash).

I believe I'm current in regard to updates.

I've run a full scan (McAfee) and it came up clean.

I've discovered that several of (but not all) the JPG files in one particular folder have become corrupted. I have run CHKDSK on all my drives (and run it again with the "Scan for and attempt recovery.." option ticked on the drive containing the JPG files) and it reported nothing unusual.

After some Google research I found a thread suggesting this BSOD code can be caused by overclocking (not the case here, and I haven't touched the BIOS in years) or by failed/clogged fans causing overheating. They looked pretty clean, but I have brushed them out and watched them spinning with the side off the case so I don't think that is the problem.

Ideas? Thank you.


My System SpecsSystem Spec
.
17 Mar 2015   #2
Chris2005

Windows 10 Home x64
 
 

The most recent dump file: 031615-29016-01.dmp. Returns the following:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 15b6b4, 2, 6f1d9}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------
The PFN_LIST_CORRUPT bug check has a value of 0x0000004E. This indicates that the page frame number (PFN) list is corrupted.

This error is typically caused by a driver passing a bad memory descriptor list.

----

031615-14617-01.dmp. Returns the following:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800038c58ec}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+17c )

Followup: MachineOwner
---------
That is IRQL_NOT_LESS_OR_EQUAL. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

The following process was listed, which is Windows Media Player.

Code:
PROCESS_NAME:  wmplayer.exe
-----

031515-16738-01.dmp. Returns the following:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80017e8420, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

With the 41790 as parameter 1, that means a page table page has been corrupted.

-----

031315-14742-01.dmp. Returned the same as the previous dump file.

-----

Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+

Note   Note


Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.


Report back with the MemTest86+ results.
My System SpecsSystem Spec
18 Mar 2015   #3
DJohnE

Windows 7 Home Premium 64bit
 
 
Thank you

Thanks Chris2005.

I'll do that - hopefully tonight - and post results.

I can confirm that I increased the amount of RAM in the PC maybe two years ago (possibly more, I really can't remember now but it wasn't recently) and it hasn't been touched since, so if that is the problem then it is either due to the memory failing or could it be an issue with the contacts needing cleaning?

Anyway, let's do the test first and see what it finds.

Thanks again.
My System SpecsSystem Spec
.

18 Mar 2015   #4
DJohnE

Windows 7 Home Premium 64bit
 
 

Hi again Chris 2005,

It looks like you hit the jackpot first try - I waited until now that I'd finished for the day on the advice that the test software should run all night to try to find an error. No criticism of the advice, but I didn't need to, it racked up thousands of errors in the first minute!!!

I've not moved onto the next stage (removing banks of memory to try to home in on the defective one) but it looks like some of my RAM is thoroughly kaput.

Based on your experience, is it 'buy new' time or could it be dirty contacts do you think?
My System SpecsSystem Spec
18 Mar 2015   #5
Chris2005

Windows 10 Home x64
 
 

It could be dirty contacts, you could try killing two birds with one stone and proceed with the narrowing down approach, take all the RAM out give a good blow on the DIMM slots on the motherboard or even a can of compressed air to remove any and all particulates as possible.

Run Memtest86+ on each individual stick.
My System SpecsSystem Spec
21 Mar 2015   #6
DJohnE

Windows 7 Home Premium 64bit
 
 

I finally got the chance to get back at the computer his morning. I took out the four RAM boards, cleaned the contacts and put each back one at a time. I ran Memtest for a couple of minutes on each board. The first three found nothing, the fourth showed errors immediately.

I already guessed that it would - that board had caught my eye while I was cleaning it. It has a 'shadow' (maybe 1/2" wide) across it on a diagonal near the middle. That looked suspicious. That slot is very close to the CPU cooling fins and I'm guessing its been affected by temperature over time.

I put the other three RAM boards back in and ran Memtest again and it didn't find errors (I let it run for a little over one full pass) so I'm currently running on 4GB (comprising 2 x 1GB and 1 x 2GB). I'll buy a new 2GB board, put that in and then run Memtest for the recommended 8 passes to be sure, but I think the mystery is solved. After that I'll mark this thread as 'solved'.

One thing I haven't tried is putting just one RAM board in, using the slot that had contained the defective board and checking that it behaves OK (I left that one empty when I put the three in).

According to Memtest my CPU is running at about 60 degrees. A quick look on Google suggests that isn't excessive.

Once again, a huge thank you for pointing me in the right direction!
My System SpecsSystem Spec
21 Mar 2015   #7
Chris2005

Windows 10 Home x64
 
 

60 C or F?

60 C is rather hot. The TCASE (Case Temperature is the maximum temperature allowed at the processor Integrated Heat Spreader (IHS)) is 72.7 C.
My System SpecsSystem Spec
22 Mar 2015   #8
DJohnE

Windows 7 Home Premium 64bit
 
 
Temperature

Degrees C.

That temperature was as displayed by the Memtest utility, so I'm guessing that the chip was under load at the time?
My System SpecsSystem Spec
24 Mar 2015   #9
DJohnE

Windows 7 Home Premium 64bit
 
 
New RAM board installed

The new 2GB RAM board arrived this morning. The computer has recognised it and is showing 6GB again. I'll run Memtest for the recommended 8 passes to prove everything is now OK, but I'm optimistic - there's been no sign of instability since I took out the defective board.
My System SpecsSystem Spec
Reply

 BSOD 6.1.7601.2.1.0.768.3 locale id 2057




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD 6.1.7601.2.1.0.768.3 Locale ID 2057
Hi, I am getting the same error every time, I thought it was my external back up drive, but have disconnected it, problem is still there. Attached are my files, if anyone could point me in the right direction that would be great. Kind Regards Neill
BSOD Help and Support
BSOD Locale ID:2057
Hi, I would really be grateful if anyone could help me solve this. It's a pretty new computer, about a month old. Had BSOD twice now, only a few apps running: Abode Reader, Chrome, Skype, Outlook Word. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1...
BSOD Help and Support
BSOD Locale: 2057
Hi, I am having recurring problems with my pc, particularly BSOD Locale 2057. I tried using the diagnostics utility and perfmon to determine the problem, but neither can finish their processes before the system crashes again. I've saved a couple of the crash reports, though, and hope someone can...
BSOD Help and Support
BSOD Locale ID: 2057
I am having problems with BSOD, every time I leave my laptop, and come back to find it off, with a recovery notice when I log back into Windows. I think it may have something to do with the laptop going into sleep or hibernation mode, as I have never seen it happen when I'm at the computer. ...
BSOD Help and Support
BSOD's - Locale ID 2057
Hi BSOD's from this morning anywhere between 30 secs to 5 mins using the computer. Win 7 Ultimate Home i5 520 @ 2.40ghz 8gb ram Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3
BSOD Help and Support
BSOD Locale ID: 2057
Hello, recently I have been getting the BSOD practically everytime I start up my Laptop (Acer Extensa 5620). I was therefore wondering whether anyone could provide any guidance, I have attached two of the .dmp files in zip format and the problem reports are here: Problem signature: Problem...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:36.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App