Windows 7 Windows 7 constantly Blue Screen'd/Not Genuine?

[DeferredGalaxy3]

Ok, so I've constantly been getting Blue Screens of Deaths, ever since last Sunday. I was browsing through DeviantArt, consistantly getting these "Windows is not Genuine" messages out of nowhere, which is weird, since I've had a valid copy of Windows since 2010. Anyway, not too long later, the computer crashed. It got a blue screen and restarted. This has been constantly happening to me since then. I've taken out my graphics card, and running off the mother board, which doesn't seem to cause a problem JUST YET, but I'll post when it does. I noticed while running Blue Screen View, that one file highlighted almost throughout the list of Blue Screen is ntoskrnl.exe. Two reoccuring Causes by Address seems to be ntoskrnl.exe+7010 and ntoskrnl.exe+7040. I wonder what it is. I'm usually pretty good with computers, but I've never really gotten into anything deep-system wise.

I have uploaded the MiniDump files here: https://www.dropbox.com/s/pf1djicjenk55e4/MiniDump Files.zip. A lot of threads post these, so I guess these are important.

One thing to note, under System Properties, where it would usually say what my Processor and RAM is, it just says "Not Available", under both. So, that might be one thing to note.

 

[kemical]

Glad to hear your up and running..

 

[DeferredGalaxy3]

I hate how my computer trolls me like this. So, you know how before nothing worked except the blue screens were gone? Now, everything works except I'm getting blue screens. The first time this occured was when I closed out of a game and unplugged a video game controller. The second time was just after playing a game, and all I did was select on the desktop, and it crashed. The third time, I wasn't watching, but it was after playing a game. All three games were different. Only one game, was I using the controller. But, the second time was when I had the controller plugged in. Also, my CPU or GPU fan (Can't tell at the moment) is making a really loud noise, like it's going to take off any minute now. Could the Blue Screens occur because it's overheating, maybe? If so, why are my fans being like this, after constantly being cleaned because of this issue?

Here are the dump files. Hopefully, this will be easier to solve, now that we have all the other issues out of the way. https://www.dropbox.com/s/3y81wr00e0nnxz1/New dump 1.zip

EDIT: So, I launched this program I have called "Who Crashed." It gives a full description of what the crashing could be caused by.

Here are the three descriptions it gives:

On Thu 5/22/2014 3:47:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052114-23618-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2213A3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002613A3, 0xFFFFF88005108F20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 5/23/2014 2:20:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052214-53165-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x7AC3C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000FAC3C, 0xFFFFF8800612B3B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 5/23/2014 3:32:06 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002D5FFCD, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I noticed two things it says on all three bug checks.

"This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. " and " Possibly this problem is caused by another driver that cannot be identified at this time."

Uh, huh. I seem really suspicious of my XBox controller, as before this whole problem occurred, there was a one in a hundred chance my computer would blue screen. I am also suspicious of it being caused by over heating, if that's an issue. Either way, I have no idea what's going on, but I thought this was all worth a mention.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000fac3c, fffff8800612b3b0, 0}

Probably caused by : win32k.sys ( win32k!RFONTOBJ::bMatchRealization+c )

Followup: MachineOwner

Hi,
your right to be suspicious of your Xbox controller as the driver is a 2009 version well known for causing bsod in win 7:
xusb21.sys Wed Apr 08 15:28:44 2009: XBox USB wireless controller BSOD issues in Win7 with 2009 driver please update:
Link Removed


BiosVersion = 0704
BiosReleaseDate = 06/11/2010
You have bios updates relating to improved stability:
http://www.asus.com/Motherboards/M4A78LTM_LE/HelpDesk_Download/

atikmdag.sys Fri Dec 06 21:19:43 2013: AMD GPU driver please update after uninstalling using this tool:
Link Removed
Install latest 14.4 driver:
Link Removed

Whilst the above dump files are most likely driver related sometimes Bugcheck 3B accompanied by win32k.sys can be a indicator of a hardware fault. Try the above changes and see how you go. Post any new dump files.

 

[DeferredGalaxy3]

Thanks, I'm kind of mad and happy knowing at least A cause. Well, I'll update everything you have here, and check back if I've gone a few days without blue screens.

 

[DeferredGalaxy3]

Not much to say, except I'm still getting blue screens. It seems my controller is ignoring the driver, for one thing. Unplugging it doesn't really help, either. Here are the dumps. At least we're only dealing with Blue Screens, here. https://www.dropbox.com/s/6iwi40p5hkgxbfp/new mini dumps 2.zip

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff880031856e8, fffff88003184f40, fffff880010b6560}

Probably caused by : hardware ( fltmgr!FltpPassThrough+510 )

Followup: MachineOwner

You have dump files ranging from bugcheck 124, USB.SYS, GPU driver and NTFS issues. Having many different types of dump file is usually indicative of a hardware issue.
Your graphic drivers are still out of date as is the bios but I feel the point is moot as something is clearly not right with a component or process on your system. It would be really handy if you could find a colleague to help test each component in their machine. Once you're sure that everything runs ok that leaves just the motherboard which at that point I would be highly suspicious of.
It could be that with all the issues you've had recently that windows has become so corrupt it keeps blue screening but usually a system file check (which you've done) would reveal any corruption.
The bios update may help. I'd give that a try.

 

[DeferredGalaxy3]

Yeah, I was just about to ask how to do that, but then I found my old mother board driver installer CD which has a program I seemed to have overlooked before, which was an updater. I updated the bios, as well as any other driver update (Including one for my graphics card), and updated them all after installing, and now everything should be up to date. The blue screens don't seem as apparent, could be the recent System File Check I actually just finished doing or the BIOS update, but if I still get any, I'll let you know.

Also, my EPSON printer driver can't even update, haven't tried after the BIOS update, because it was ALWAYS interrupted with a blue screen. I'll give it another try, but even thought it's stretching, I think that may be at least A factor of what's causing the blue screen.

 

[DeferredGalaxy3]

More crashes more dumps. Oh, what? Only one? Um.... okay. https://www.dropbox.com/s/2ejvgvhli2fz3i0/052614-59639-01.dmp

And when I said I did a System File Check in the post above, I meant I did a Memory Diagnostic. Sorry, I got those two mixed up.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80080a2748, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner

Your CBS log shows corruption:

  CSI    00000318 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-05-27 01:51:13, Info                  CSI    00000319 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-05-27 01:51:13, Info                  CSI    0000031a [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-05-27 01:51:13, Info                  CSI    0000031b [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2014-05-27 01:51:13, Info                  CSI    0000031c Hashes for file member \??\C:\Windows\SysWOW64\en-US\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-05-27 01:51:13, Info                  CSI    0000031d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-05-27 01:51:13, Info                  CSI    0000031e [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
2014-05-27 01:51:13, Info                  CSI    0000031f Repair results created:

Try booting off the windows disk but instead of installing run repair instead. Failing that I'd try re-installing windows.