Windows 8.1 (64 Bit) Keeps Crashing

I have been using Nvidia Geforce to update the GPU. I didn't before, but now I have allowed for beta updates.

So should I use the beta drivers or should I not use the beta drivers?

All right, I'll try that. Just received another crash, and here is the error message. I guess I should also mention this happened right after I installed some driver software for a Xbox 360 Wireless controller receiver, though since I was receiving crashes these past couple of days, I am not sure if the two are related.

Log Name: Application
Source: Application Error
Date: 4/15/2015 9:18:14 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Serge
Description:
Faulting application name: LogonUI.exe, version: 6.3.9600.17415, time stamp: 0x5450541b
Faulting module name: USBKeyCredentialProvider.dll_unloaded, version: 0.0.0.0, time stamp: 0x53d9fa55
Exception code: 0xc0000005
Fault offset: 0x000000000002b4a8
Faulting process id: 0x548
Faulting application start time: 0x01d077e32e98d8f9
Faulting application path: C:\WINDOWS\system32\LogonUI.exe
Faulting module path: USBKeyCredentialProvider.dll
Report Id: 73d879d9-e3d6-11e4-82ab-d050994d56ae
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-16T01:18:14.000000000Z" />
<EventRecordID>14158</EventRecordID>
<Channel>Application</Channel>
<Computer>Serge</Computer>
<Security />
</System>
<EventData>
<Data>LogonUI.exe</Data>
<Data>6.3.9600.17415</Data>
<Data>5450541b</Data>
<Data>USBKeyCredentialProvider.dll_unloaded</Data>
<Data>0.0.0.0</Data>
<Data>53d9fa55</Data>
<Data>c0000005</Data>
<Data>000000000002b4a8</Data>
<Data>548</Data>
<Data>01d077e32e98d8f9</Data>
<Data>C:\WINDOWS\system32\LogonUI.exe</Data>
<Data>USBKeyCredentialProvider.dll</Data>
<Data>73d879d9-e3d6-11e4-82ab-d050994d56ae</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Besides installing the controller, no. I was watching a YouTube or a Netflix video, but that is about it. I was able to format and re-install windows. Going to try doing what I was doing before and see if another crash occurs.

Update
Well I received another crash. Thought the problem was finally fixed. I was simply downloading some items, listening to some music on iTunes, and chatting with a friend. Before, I was just posting any warnings/errors I saw on the applications, but now I will post stuff from the administrative events.
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 4/16/2015 9:29:34 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Serge-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a00f58b22db546, 0xb3b71bdf04aaf7d9, 0xfffff800d5459c88, 0x0000000000000001). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 041615-13015-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-17T01:29:34.000000000Z" />
<EventRecordID>1533</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Serge-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000109 (0xa3a00f58b22db546, 0xb3b71bdf04aaf7d9, 0xfffff800d5459c88, 0x0000000000000001)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">041615-13015-01</Data>
</EventData>
</Event>

Also


Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 4/16/2015 9:29:28 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Serge-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2015-04-17T01:29:28.506464200Z" />
<EventRecordID>1515</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Serge-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">265</Data>
<Data Name="BugcheckParameter1">0xa3a00f58b22db546</Data>
<Data Name="BugcheckParameter2">0xb3b71bdf04aaf7d9</Data>
<Data Name="BugcheckParameter3">0xfffff800d5459c88</Data>
<Data Name="BugcheckParameter4">0x1</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

And another crash. The blue screen of death mentioned this was an irql_not_less_or_equal error.

Log Name: Application
Source: Application Error
Date: 4/16/2015 11:27:56 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Serge-PC
Description:
Faulting application name: LogonUI.exe, version: 6.3.9600.17415, time stamp: 0x5450541b
Faulting module name: USBKeyCredentialProvider.dll_unloaded, version: 0.0.0.0, time stamp: 0x53d9fa55
Exception code: 0xc0000005
Fault offset: 0x000000000002b4a8
Faulting process id: 0x55c
Faulting application start time: 0x01d078be72f78a02
Faulting application path: C:\WINDOWS\system32\LogonUI.exe
Faulting module path: USBKeyCredentialProvider.dll
Report Id: bc9e40c4-e4b1-11e4-825f-d050994d56ae
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-17T03:27:56.000000000Z" />
<EventRecordID>1459</EventRecordID>
<Channel>Application</Channel>
<Computer>Serge-PC</Computer>
<Security />
</System>
<EventData>
<Data>LogonUI.exe</Data>
<Data>6.3.9600.17415</Data>
<Data>5450541b</Data>
<Data>USBKeyCredentialProvider.dll_unloaded</Data>
<Data>0.0.0.0</Data>
<Data>53d9fa55</Data>
<Data>c0000005</Data>
<Data>000000000002b4a8</Data>
<Data>55c</Data>
<Data>01d078be72f78a02</Data>
<Data>C:\WINDOWS\system32\LogonUI.exe</Data>
<Data>USBKeyCredentialProvider.dll</Data>
<Data>bc9e40c4-e4b1-11e4-825f-d050994d56ae</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Well this is a desktop, so no fingerprint reader. While I have purchased Sins of a Solar Empire from Steam, I haven't installed it on this computer. Looking at the program list, I don't see anything developed from DigitalPersona or Stardock.

Just got another crash. They seem to be occurring more frequently now. This time it was a Critical Structure Corruption. I just took a quick look at Google and found some info about it being a hard-drive issue. I guess I should have mentioned it before, but I have three hard drives. An SSD with the OS, a basic HDD, and another HDD from an old computer. I reformatted that drive and added it to this computer. Later tonight I am going to disable that drive (wasn't using it much anyway), and see if that solves anything.

Log Name: Application
Source: Application Error
Date: 4/17/2015 9:01:43 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Serge-PC
Description:
Faulting application name: LogonUI.exe, version: 6.3.9600.17415, time stamp: 0x5450541b
Faulting module name: USBKeyCredentialProvider.dll_unloaded, version: 0.0.0.0, time stamp: 0x53d9fa55
Exception code: 0xc0000005
Fault offset: 0x000000000002b4a8
Faulting process id: 0x53c
Faulting application start time: 0x01d0790ea0566c16
Faulting application path: C:\WINDOWS\system32\LogonUI.exe
Faulting module path: USBKeyCredentialProvider.dll
Report Id: e4970eef-e501-11e4-8260-d050994d56ae
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-17T13:01:43.000000000Z" />
<EventRecordID>1600</EventRecordID>
<Channel>Application</Channel>
<Computer>Serge-PC</Computer>
<Security />
</System>
<EventData>
<Data>LogonUI.exe</Data>
<Data>6.3.9600.17415</Data>
<Data>5450541b</Data>
<Data>USBKeyCredentialProvider.dll_unloaded</Data>
<Data>0.0.0.0</Data>
<Data>53d9fa55</Data>
<Data>c0000005</Data>
<Data>000000000002b4a8</Data>
<Data>53c</Data>
<Data>01d0790ea0566c16</Data>
<Data>C:\WINDOWS\system32\LogonUI.exe</Data>
<Data>USBKeyCredentialProvider.dll</Data>
<Data>e4970eef-e501-11e4-8260-d050994d56ae</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

There may be something to that, because I just took a look at some of the warnings and found several of these the past two days. Going to investigate.

Log Name: Application
Source: NvStreamSvc
Date: 4/17/2015 8:55:28 PM
Event ID: 2002
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Serge-PC
Description:
The description for Event ID 2002 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

NvStreamSvc
SSAU process ID 6120 did not exit, Terminating. [0]

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NvStreamSvc" />
<EventID Qualifiers="32770">2002</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-18T00:55:28.000000000Z" />
<EventRecordID>1666</EventRecordID>
<Channel>Application</Channel>
<Computer>Serge-PC</Computer>
<Security />
</System>
<EventData>
<Data>NvStreamSvc</Data>
<Data>SSAU process ID 6120 did not exit, Terminating. [0]</Data>
</EventData>
</Event>

Hey so a couple of things happened. First I received another general crash, so I decided to perform the Driver Verifier test once more. In the instructions, it mentions that DDI compliance checking and randomized low resource simulation, should be unchecked, but I noticed there was also this setting called DDI compliance checking (additional), so this time I unchecked that as well. Then I restarted my computer, and instead of instantly crashing, I was able to use it. After a while, it finally crashed, with the error PFN_List_Corrupt. Here is the mini dump file, and the event log.

https://www.dropbox.com/s/4npgvsy0r283feu/041615-9609-01.zip?dl=0

https://www.dropbox.com/s/5481pr8x0cwpwgn/Errors2.zip?dl=0

From another site I received the suggestion to disable the nVidia Streaming service, and was trying that. Received a few less errors in the log, but then the computer started to crash once more. Going to try uninstalling the Asrock Ram Driver, but not AVG since the computer was crashing before I used it.

Also here are the logs for after I disabled the nVidia Streaming service.
https://www.dropbox.com/s/d5rj1vta4pu7ihf/042115-9765-01.zip?dl=0

https://www.dropbox.com/s/j5nfx7pi1vzruh4/Errors4.zip?dl=0

Hey guys, sorry for replying to this for a while. Well the case is closed. Apparently I shorted the motherboard when I was installing the computer (first build, what can I say). That was why the computer was crashing for little to no reason. Well a new motherboard later, and more proper installation care, and the computer is A OK. Thanks for everyone for the help and again, sorry for the late reply.

So yeah as posted before, problem solved. now I am just trying to mark this as solved.