New
#1
Bsod
I keep getting this annoying BSOD at random Times.
Windows 7 64BIT.
8GB RAM
AMD X6 1090T @ 4.02Ghz
I keep getting this annoying BSOD at random Times.
Windows 7 64BIT.
8GB RAM
AMD X6 1090T @ 4.02Ghz
Hello D3LL!
BSOD Summary
As you see, it's unknown, this means it's likely Malware. Try doing a full scan with MalwarebytesCode:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.987\071811-11856-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03099650 Debug session time: Mon Jul 18 20:08:45.994 2011 (UTC + 2:00) System Uptime: 0 days 1:42:09.134 Loading Kernel Symbols ...............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list .....Missing image name, possible paged-out or corrupt data. .....Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. .....Missing image name, possible paged-out or corrupt data. .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff88008ffe498, fffff88008ffdcf0, fffff80002e98780} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner ---------
Either, I'd wait for more assistance, because I'm not sure at this one when I think about it.
Best Regards,
FredeGail
Try running Driver Verifier under these instructions:
Using Driver Verifier to identify issues with Drivers
.. and upload the .dmp file from the BSOD if any.
Best Regards,
FredeGail
Done this, Restarted windows and it froze on "Starting Windows", Rebooted and then after starting windows I got another BSOD...
Got it. Certainly great news for you!
Uninstall your Nvidia driver!
BSOD Summary
nvlddmkm.sys is your Nvidia Graphic Driver. Again, uninstall it, and reinstall the newest version from their website.Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI02.454\071811-16707-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063650 Debug session time: Mon Jul 18 22:29:48.122 2011 (UTC + 2:00) System Uptime: 0 days 0:00:13.277 Loading Kernel Symbols ............................................................... .................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002e948b4, fffff88003183828, fffff88003183080} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+aa1e4 ) Followup: MachineOwner ---------
Best Regards,
FredeGail