Yet another Win 7 x64 blue screen

[Sahandrian]

Hi there,

For a month or so I am experiencing a blue screen issue,

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1026

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 0000000000033174
BCP3: 0000000000000001
BCP4: 0000000005860014
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060110-12979-01.dmp
C:\Users\Mystic\AppData\Local\Temp\WER-22042-0.sysdata.xml


Any help would be appreciated - I tried to discover the problem but I am really not the one to read minidumps...
I have attached several last minidumps I got.

Thanks in advance for any help provided!

 

[Jonathan_King]

The dmp looks like bad RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Also, remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 06:05:52.411 2010 (GMT-4)
System Uptime: 0 days 0:35:21.019
BugCheck 4E, {99, 33174, 1, 5860014}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  GSvr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 05:29:47.421 2010 (GMT-4)
System Uptime: 0 days 0:47:40.044
BugCheck 50, {fffff8d00b088350, 1, fffff88004591421, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+31 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 20:41:18.211 2010 (GMT-4)
System Uptime: 0 days 2:16:13.555
BugCheck A, {fffff840009ebb00, 2, 0, fffff80002acc05b}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  everest_bench.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 14:57:18.477 2010 (GMT-4)
System Uptime: 0 days 0:12:22.100
BugCheck 24, {1904fb, fffff88002faec28, fffff88002fae490, fffff80002ab4000}
Probably caused by : Ntfs.sys ( Ntfs!LfsFlushLfcb+644 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 13:16:14.493 2010 (GMT-4)
System Uptime: 0 days 0:11:06.976
BugCheck 50, {ffffdd03c0221d60, 0, fffff96000152f00, 7}
Probably caused by : win32k.sys ( win32k!HmgSetOwner+80 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Skype.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 11:39:43.396 2010 (GMT-4)
System Uptime: 0 days 0:02:10.190
BugCheck 3B, {c0000005, fffff96000112ad3, fffff88002612090, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+73 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 11:36:43.941 2010 (GMT-4)
System Uptime: 0 days 0:17:29.611
BugCheck 3B, {c0000005, fffff960000d2ad3, fffff88002612090, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+73 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
[/font]

Update these old drivers:

WMP54Gv41x64.sys Mon Dec 11 09:37:57 2006
gdrv.sys     Sat Oct 13 03:22:00 2007

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[Sahandrian]

Thanks for the fast replay, did everything you stated and the memtest showed alot of errors during the tests. Does that mean it's time for new RAM? Tried with one RAM plate then with the other and with both - it was the same during tests. Thanks very much for your help!

Best regards!

 

[Jonathan_King]

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

If you determine it's the RAM, and not the board, buy new RAM.

 

[Ageeb]

Assuming it's the board in your profile info:
Another perspective is that your board was designed with overclocking features also... Have you made any changes to the BIOS? Was there another owner to this computer before you?

I guess I'd make sure BIOS settings are near default settings for your hardware before you decide they're in a fail state. just my $.02...

-Ageeb