SOLVED BS0D 2057

Joined
Jun 12, 2012
Messages
19
Reaction score
0
Hello to all, I'm having a few issues with blue screens, which appear to be being caused by a errant driver, but I'm not sure which one, any assistance with this would be appreciated.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: 000000000000000B
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800432AE79
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\061312-26410-01.dmp
C:\Users\Kevin Johnson\AppData\Local\Temp\WER-42369-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
Joined
Jun 12, 2012
Messages
19
Reaction score
0
BSOD 2057 mini dump file

Thanks for the quick reply Shintaro.:) Sorry, I didn't have time this morning to attach the file, please let me know if there are any issues with the attachment, as I'm not sure this is correct.
 

Attachments

Last edited:
Joined
Jun 12, 2012
Messages
19
Reaction score
0
BSOD 2057 nusb3xhc.sys screen capture

Thanks Shintaro, here's the screencapture, I hope this is what you needed, I won't be able to deal with this until this evening, so any further feedback would be grately appreciated.
 

Attachments

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
Thanks mate, definately update those drivers.

Let us know how you go.
 
Joined
Jun 12, 2012
Messages
19
Reaction score
0
BSOD 2057 with mini dump file

Unfortunately this appears to have no effect, I have updated all my drivers and the chipset from the gigabyte webpage, it appears to no avail. Please see attached mini dump file, any suggestions on where to go from here?
 

Attachments

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
Just a couple of questions:

1/ What do you have plugged in to your USB ports?
2/ What kind of network / wireless card are you using?

The drivers below are quite old. Could you please update them.

secdrv.SYS Wed Sep 13 23:18:38 2006 (4508052E)
Can be updated via Windows Update.

scmndisp.sys Wed Jan 17 18:48:03 2007 (45ADD4B3)
Netgear Wireless. Please update the driver.

cmudaxp.sys Mon Jun 23 18:08:40 2008 (485F5A08)
http://support.asus.com/Download.aspx?SLanguage=en&m=Xonar+D1&p=21&ft=4&os=29

EDIT: Also in your BIOS set it to "Fail-Safe" defaults. It is on 2-9 of your motherboard's manual.

Let us know how you go.

Hope this helps.
 
Last edited:
Joined
Jun 12, 2012
Messages
19
Reaction score
0
Thanks Shintaro, the devices that I have plugged into the usb ports are, logitech C270 webcam, XBOX 360 Controller for PC, and Net Gear N300 Wireless Adapter (recent purchase). In your reply you provide a link to an ASUS page, my mobo is a Gigabyte, was that a typo?
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
That link is for your ASUS Xonar audio card. The driver cmudaxp.sys will be part of the driver update from ASUS.
Please look for updates for everything that plugged in to the USB ports.

Please let me know if you have anymore questions.
 
Joined
Jun 12, 2012
Messages
19
Reaction score
0
I believe Ihave managed to update all drivers you suggested, except secdrv.SYS Wed Sep 13 23:18:38 2006 (4508052E) which I can't locate via microsoft update, any suggestions on where to get this from? Also I have reset the BIOS to fail safe defaults, usually the BSOD happens from cold start up, so if this has fixed the problem I should be ok tomorrow morning. I'll post a new BSOD mini dump if not :)
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
secdrv.SYS is meant to part of Windows update.
Are you up to date with the MS updates? in particular the security updates?

If you have any questions please ask.
 
Joined
Jun 12, 2012
Messages
19
Reaction score
0
Thanks for the reply Shintaro. As far as I can tell, I'm up to date with all my windows updates, so am not sure why this hasn't been addressed before, any suggestions on how to rectify this?
 
Joined
Jun 12, 2012
Messages
19
Reaction score
0
Hi Shintaro, the general consensus that I have read trying to locate a download of the drvier secdrv.sys seems to be that it affected Windows XP, Server 2000 & Server 2003, also when I located the file in my C:\Windows\System32\Drivers file it shows the time/date stamp for the driver as modified 10/6/09 @ 21:37, it would appear that the patched update has already been applied if this is to be believed, any feedback on this theory would be appreciated :)
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
That's cool, the original date was 2006 for secdrv.sys. So a tick in the box for that one.

Now it is down to see if the crashes occur again. Lets hope those driver updates fix the problem.
If it doesn't, just let us know what was happening when it crashed and upload the .dmp files.

Let us know how you go.
 
Joined
Jun 12, 2012
Messages
19
Reaction score
0
BSOD 2057 mini dump file attached

Good Morning All, sadly the fix has not resolved the issue, first thing this morning fired up my PC & it bluescreened again

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA80037CEA20
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\061612-29983-01.dmp
C:\Users\Kevin Johnson\AppData\Local\Temp\WER-51402-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I've attached the mini dump file, any suggestions on where to go from here, I'm wondering if its a RAM issue, as the blue screen suggested Memory Management, but when I completed the start up repair, and Windows booted, it came up with the same BSOD code 2057
 

Attachments

Top