New Laptop BSODs

[Redbl]

Hi everyone. I recently purchased a new laptop, and I've been getting BSODs. I thought it was a RAM issue and ran memtest86. All seemed good. So I ran Prime95, got errors the first time, but upon testing the RAM individually and then in opposite slots, I got no Prime95 errors anymore. The BSODs have returned, and no tests I'm running are giving me negative results. I'm very grateful for any help you can offer!

 

[reventon]

What Anti-Viruses have you had on the laptop since you got it? (incl. ones that you have uninstalled)

3 BSODs - all Microsoft Drivers; meaning that it is most likely a hardware error.

One suspicious 3rd party driver that was loaded at the time of all 3 BSODs

[font=lucida console][B]smserial.sys[/B] Mon Dec 01 22:45:22 [COLOR=Red]2008[/COLOR][/font]

smserial.sys - Dial up modem driver. Update from your laptop manufacturers website.

Also, given you got errors on at least one memtest try running it again for an extended period this time (at least 7 passes per stick)

Regards,
Reventon

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 05:25:09.488 2010 (GMT+12)
System Uptime: 0 days 19:05:21.002
BugCheck 34, {50830, fffff8800b5ce4f8, fffff8800b5cdd60, fffff80002b02642}
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+d2 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 09:28:36.032 2010 (GMT+12)
System Uptime: 0 days 0:14:45.546
BugCheck BE, {fffff88001732fa8, 3d4c121, fffff88007c76c20, b}
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+8e52 )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 09:12:54.306 2010 (GMT+12)
System Uptime: 0 days 2:50:01.820
BugCheck BE, {fffff880013595a8, 8c000000392d121, fffff8800a673370, b}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+423be )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ 
[/font]

 

[Redbl]

What Anti-Viruses have you had on the laptop since you got it? (incl. ones that you have uninstalled)

3 BSODs - all Microsoft Drivers; meaning that it is most likely a hardware error.

One suspicious 3rd party driver that was loaded at the time of all 3 BSODs

[FONT=lucida console][B]smserial.sys[/B] Mon Dec 01 22:45:22 [COLOR=Red]2008[/COLOR][/FONT]

smserial.sys - Dial up modem driver. Update from your laptop manufacturers website.

Also, given you got errors on at least one memtest try running it again for an extended period this time (at least 7 passes per stick)

Regards,
Reventon

BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 05:25:09.488 2010 (GMT+12)
System Uptime: 0 days 19:05:21.002
BugCheck 34, {50830, fffff8800b5ce4f8, fffff8800b5cdd60, fffff80002b02642}
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+d2 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 09:28:36.032 2010 (GMT+12)
System Uptime: 0 days 0:14:45.546
BugCheck BE, {fffff88001732fa8, 3d4c121, fffff88007c76c20, b}
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+8e52 )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 09:12:54.306 2010 (GMT+12)
System Uptime: 0 days 2:50:01.820
BugCheck BE, {fffff880013595a8, 8c000000392d121, fffff8800a673370, b}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+423be )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ 
[/FONT]

I've only installed MS Security Essentials.

Those are the latest Modem drivers, but I'm not exactly using it- can I just disable the device or should I fully uninstall it?

I'll try running an extended memtest again. :/

Thanks so much for your response.

 

[Davidxtux]

If you are not using it then I suggest just removing/uninstalling from the device manager. Not essential dlls and drivers can cause problems if left alone.

 

[reventon]

Ok, the reason I asked about the Anti-Viruses was because in one of the dumps MpFilter.sys was mentioned:

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 09:28:36.032 2010 (GMT+12)
System Uptime: 0 days 0:14:45.546
BugCheck BE, {fffff88001732fa8, 3d4c121, fffff88007c76c20, b}
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : [COLOR=Blue][B]MpFilter.sys[/B][/COLOR] ( MpFilter+8e52 )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
[/FONT]

This driver is part of Microsoft Security Essentials, and while we do see 3rd party Anti-Viruses as the cause of BSODs all the time it is unusual for a Microsoft Driver to be the true cause.

One of the possibilities in the above case is that remnants from a previous AV install could be interfering with MSE, but obviously that is not the case. The other possibility is hardware error.

After you finish the memtest run Prime 95 again following these instructions:

Prime95 Setup:
Download from: Free Software - GIMPS
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Regards,
Reventon

 

[Redbl]

Well, after 10 passes, the first stick finally got 2 errors. "There's the culprit!" I thought. I ran the second stick and by the time 7 passes were over it had over 4000 errors. I'm going to RMA both sticks. Should I still run Prime95?

Thanks so much for your help!

 

[Davidxtux]

4000 errors? If you motherboard has 4 dimm slots.. I would suggest trying them in different slots and run memtest again.

 

[reventon]

Agreed, if a memtest fails it does not necessarily mean that the RAM is faulty - it could be the motherboard. No need to run Prime95 now.

 

[Redbl]

There are two DIMM slots on my motherboard. At the recommendation of my manufacturer I'm going to RMA the whole unit and let them give it their workup.

 

[Davidxtux]

I believe that should be the best course of action. 4000 errors definitely can mean a bad dimm slot.