Solved BSOD 1033 9f when Win 7 Pro x 64 sleeps

[zLunch]

I've been experiencing BSODs when my computer is in Sleep mode. I really don't know what happens other than the computer is put to sleep and when I come back hours later it has suffered a BSOD and has restarted and is asking for the login.

Win 7 is up to date.
Drivers have been updated (Driver Finder).
All external drives have been disconnected.
memtestx86 version 3.5b was run 6 times (fell asleep) with no errors found.
sfc /scannow was run a number of times with no integrity violations found.
chkdsk /r reported nothing

According to the problem signature info it would seem the BSOD might have something to do with Dreamweaver because when I click on the file below, Dreamweaver opens. The software is up-to-date and I disabled any add-ons but the BSODs keep happening.

Files that help describe the problem:
C:\Users\John\AppData\Local\Temp\WER-3353506-0.sysdata.xml
​

I don't know what else to do.
Hope you can help. Thanks in advance




Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA80067D9A10
BCP3: FFFFF80000B9C518
BCP4: FFFFFA800B36C010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\090912-21465-01.dmp
C:\Users\John\AppData\Local\Temp\WER-3353506-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

 

[Arc]

Welcome aboard, zLunch. Nice to meet a creative person.

► Your issue is associated with nVidia nForce network driver (nvmf6264.sys)

0: kd> !irp fffffa800b36c010 1
Irp is active with 4 stacks 3 is current (= 0xfffffa800b36c170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800b36c030
ThreadListEntry.Blink = fffffa800b36c030
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800b36c088
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa800c1b0bb8
Tail.Overlay.ListEntry.Blink = fffff80003629b00
Tail.Overlay.CurrentStackLocation = fffffa800b36c170
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8008061050 00000000 fffff800036c6200-fffffa8006972220 Success Error Cancel pending
          [COLOR=Red][B]Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys,[/B][/COLOR] Win32 error 0n2
*** [COLOR=Red][B]WARNING: Unable to verify timestamp for nvmf6264.sys[/B][/COLOR]
*** [COLOR=Red][B]ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys[/B][/COLOR]
 \Driver\NVNET    nt!PopSystemIrpCompletion
            Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8006972220    

            Args: 00000000 00000000 00000000 00000000

► So let us check the age of the driver.

0: kd> lmvm nvmf6264
start             end                 module name
fffff880`04618000 fffff880`0466ba80   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
    [COLOR=Red][B]Image name: nvmf6264.sys
    Timestamp:        Fri Mar 05 06:34:39 2010 [/B][/COLOR](4B9058A7)
    CheckSum:         000565B2
    ImageSize:        00053A80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So, you should check for updates. Do it from nVidia's site : http://www.nvidia.com/Download/index.aspx

And, I would suggest you to uninstall McAfee, and use http://windows.microsoft.com/en-US/windows/products/security-essentials. McAfee causes a lot of troubles whereas MES is best designed for Windows 7, and its totally free.

 

[zLunch]

Nvidia gives me the option of of searching for graphics and/or motherboard drivers.

NVIDIA Driver Downloads:
GeForce 9100 301.42 Your PC currently has the latest driver installed for your GPU. No driver update is necessary at this time.

GeForce 8100 -- Your PC currently has the latest driver installed for your motherboard. No driver update is necessary at this time.

I updated to the graphics driver many BSODs ago. The motherboard driver (I guess) has not needed an update.

Nvidia doesn't even recognize "nvmf6264.sys" A search for "network driver" returns 986 results. How am I supposed to know what one to download?

 

[Arc]

For the first option, Product Type, do it:
View attachment 231156

Product Series, Product, Download Type, Operating System and Language .... do as your system and requirement.

It will lead you to what you need.

 

[zLunch]

Thanks for your patience and detailed response, Arc. Seriously, all the other options had me intimidated. I did not want to make things worse.

Thanks for your help!

 

[Arc]

You are welcome.
Let us know how the situation is, after the driver update.

 

[zLunch]

The recommended change to Microsoft Security Essentials wasn't made until this morning so maybe that was the problem. Or maybe something didn't take with my nForce drivers update. Anyhow, there was another BSOD yesterday. It came pretty much on schedule (every 7 +/- days) and had the same MO as all the others (computer sleeping). The memtest86 was again run 6 times and there's still no errors being reported.

Would you please take another look at my SF Diagnostic files and offer an opinion?

Thanks for all your help,

 

[Arc]

zLunch, sorry to hear it

Unfortunately, the cause is somehow similar.

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_nvmf6264_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_[COLOR=Red][B]nvmf6264[/B][/COLOR]_IMAGE_[COLOR=Blue][B]pci.sys[/B][/COLOR]

Followup: MachineOwner
---------

That we have already updated is mvmf6264.sys; but it reflects on pci.sys, which is NT Plug and Play PCI Enumerator. A driver component driven by a driver to match the card with motherboard. So wherefrom the fault comes?

Apparently, it is coming from the BIOS.

BIOS Version/Date    American Megatrends Inc. 5.11, [COLOR=Red][B]4/28/2009[/B][/COLOR]

A BIOS update may do the change.

Let us know if you can do it or not, otherwise we will take the help of our hardware experts.

 

[zLunch]

Okay, I now have:

BIOS Version/Date American Megatrends Inc. 5.22, 4/15/2010

Thanks for your input.

 

[Arc]

Let's hope