BSOD every weekend

FBBMitch · 06 Jun 2011

Apparently my computer doesn't like to work weekends, but I need to keep it running because of scheduled work-related downloads. Oddly, the problem only happens when my computer is inactive for more than one day; no problems at all during the week when it gets daily use.

Zip file with info attached.

Specs:
Win7 Professional 64-bit
Original installed OS
OEM version
Computer is about 2 months old
OS install should be the same, I'd hope.

Help would be appreciated!

FBBMitch · 07 Jun 2011

Let me know if I need to provide additional info!

:)

mgorman87 · 07 Jun 2011

Never seen this bug check before

STOP 0x000000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE

Usual causes: Device driver

Lets enable driver verifier and see what it catches - Driver Verifier - Enable and Disable

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun  5 13:51:19.623 2011 (UTC - 4:00)
System Uptime: 4 days 4:55:59.547
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4621f )
BUGCHECK_STR:  0xCF
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xCF_nt!_??_::FNODOBFM::_string_+4621f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 21:16:34.770 2011 (UTC - 4:00)
System Uptime: 4 days 4:04:07.849
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4621f )
BUGCHECK_STR:  0xCF
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xCF_nt!_??_::FNODOBFM::_string_+4621f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 22 16:15:55.801 2011 (UTC - 4:00)
System Uptime: 4 days 2:41:05.627
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4621f )
BUGCHECK_STR:  0xCF
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xCF_nt!_??_::FNODOBFM::_string_+4621f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

FBBMitch · 07 Jun 2011

Thanks for the reply. I've got the Driver Verifier running as per the instructions. There was a memory check when I rebooted, and I assume this is just running in the background now, correct? Should I see a log report somewhere?

FBBMitch · 07 Jun 2011

Ooops, duh, just read this which answered my question:
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

No BSOD's yet. Okay to leave this running for a while until something comes up?

mgorman87 · 09 Jun 2011

You only need to run it for 48 hours. If no crashes happen within that time period then you can turn it off.

FBBMitch · 14 Jun 2011

I was out Friday and Monday; back to work today and my computer was locked up. Had to do a hard reboot. How do I know if Verifier caught anything? (It was still running, as far as I know.)

mgorman87 · 14 Jun 2011

If DV caught something it would blue screen your comptuer