Requesting BSOD .dmp analysis

Hello and welcome drejk there is one dump file that has me thinkin this might be due to malware

Code:

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Some malware can be masked as this system

The other thing is there is some reference to the NVidia driver so how did you update it ?? the Windows feature (which I never use) ? NVidia site??

Code:

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xfffff88003385070 ; kb

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

Another thing you could try is a Furmark run too FurMark

EDit I also meant to say run these
SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Malwarebytes | Malwarebytes Anti-Malware Premium
AdwCleaner Download
ADW download from bleeping computer delete any rubbish found with the malware scans

ICIT2LOL said:

Hello and welcome drejk there is one dump file that has me thinkin this might be due to malware

Code:

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Some malware can be masked as this system

Nope, that is just your symbol problems again, not malware or something.


Hi drejk,

Welcome to the 7forums :)

Lets try to clean reinstall the drivers from Nvidia, if another BSOD occurs please follow the BSOD Posting Instructions

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
Attachment 384897

Code:

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8801127ee71, fffff88003385818, fffff88003385070}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1c5e71 )

Followup:     MachineOwner

7: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff880`110b9000 fffff880`11cfd000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Mar 22 02:49:01 2016 (56F0A48D)
    CheckSum:         00BFF073
    ImageSize:        00C44000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hmm axe I just Googled that mssmbios and it had a few refs to malware still working on the symbols mate

All Windows drivers could have a reference to malware, but it doesn't mean there is malware.
The mssmbios.sys is used to display data of the CPU, BIOS, motherboard, etc. via the command !sysinfo, for example !sysinfo cpuinfo which displays some information about the CPU.
The mssmbios.sys wasn't loaded in the dump what makes that we then can't use the !sysinfo commands when analysing dumps, more doesn't it mean.

No worries:)