Windows 10: Bsod Windows 10 Multiple Bsods Please Help

You don't sound stupid at all.
Try running this in an admin command prompt* and post the result
Code: Get-ScheduledTask | Get-ScheduledTaskInfo | Sort-Object LastRunTime, TaskName | ft TaskName,LastRunTime -auto[/quote] *Search "command prompt" (without quotes), right click the command prompt and choose to run as administrator.

 

i think im doing it wrong because i keep getting is not reconizged by internal or external or batch file im supoosed to do the whole thing right sorry

 

Search taskscheduler and open the app.
In taskscheduler, click on Task Scheduler Libraby.
You should see in the middle of the screen tasks schedules like below
Attachment 43955

 

Attachment 43958

ok now what i took a pic like you

 

Please take screenshots of the tasks Advanced and KMS8 and post them.

 

here is driver updator and im afriad to say what kms8 is but its not legalAttachment 43960

 

Very odd that I missed Advanced Driver Updater

That is enough to say that you need to remove it, any kind of cracking is not allowed and I cannot give further support until every kind of cracking is removed.

Forum rules

 

so if i remove advanced driver updater i should be fine

 

Remove ADU and its installed drivers.
No garantee you should be fine, there is no prove that ADU causes it.

The supports stops here, until the illegal stuff is removed from your system!

 

Attachment 43962ok so i just removed it and got another bsod with memory managment as i was unistalling it PLEASE HELP

 

i removed it i promise its not im my system anymore PLEASE HELP

 

Please run the BSOD tool again and upload the zip file.
The 0x1A(MEMORY_MANAGEMENT) is mainly caused by memory problems, but could also be caused by drivers.
I would need to check to make sure which of the 2 it is, but you could start with running MemTest86+ to test your memory.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Check the frequency your RAM can handle and the supported RAM frequency by the motherboard.
Go into the BIOS and make sure the frequency of the RAM is supported by the motherboard.
Same with the voltage.
Also, run MemTest86+ as previous instructed.

Code: BugCheck 1A, {41792, fffff68000338178, 400000000, 0} Probably caused by : memory_corruption ( ONE_BIT ) Followup: MachineOwner --------- 5: kd> !analyze -v; ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. Arg2: fffff68000338178 Arg3: 0000000400000000 Arg4: 0000000000000000 Debugging Details: ------------------ MEMORY_CORRUPTOR: ONE_BIT BUGCHECK_STR: 0x1a_41792 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: dragon.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre STACK_TEXT: ffffd000`e71c83b8 fffff803`9177e7ee : 00000000`0000001a 00000000`00041792 fffff680`00338178 00000004`00000000 : nt!KeBugCheckEx ffffd000`e71c83c0 fffff803`9162ddf0 : ffffe001`55ba3860 ffffd000`e71c8689 ffffe001`5a70c578 ffffe001`5b5fd010 : nt! ?? ::FNODOBFM::`string'+0x209ee ffffd000`e71c85c0 fffff803`91ac2cb7 : ffffe001`5b5fd010 ffffe001`5b5fd010 ffffe001`5a44e840 ffffe001`5a70c080 : nt!MiDeleteVad+0x4b0 ffffd000`e71c86f0 fffff803`91ac2a13 : 00000000`00040000 ffffd000`e71c8988 00000000`00000000 ffffe001`5a70c080 : nt!MmCleanProcessAddressSpace+0xef ffffd000`e71c8750 fffff803`91abb61b : ffffe001`5a70c080 ffffc000`50310060 ffffd000`e71c8988 00000000`00000000 : nt!PspRundownSingleProcess+0x12b ffffd000`e71c87e0 fffff803`91b1f318 : 00000000`00000000 ffffe001`5a44e801 00000000`fe7e4000 ffffe001`5a70c080 : nt!PspExitThread+0x5fb ffffd000`e71c88e0 fffff803`91b1f2ff : ffffe001`54707080 00000000`00000100 00000000`00000000 fffff803`9164611d : nt!PsExitCurrentUserThread+0x18 ffffd000`e71c8910 fffff803`91642712 : fffff803`916ae1d8 00000000`00000000 ffffd000`e71c8a48 ffffd000`e71c89d0 : nt!KiSchedulerApcTerminate+0x1f ffffd000`e71c8940 fffff803`91752570 : 00000000`00000000 ffffd000`e71c89c0 fffff803`916ae1d8 00000000`00000000 : nt!KiDeliverApc+0x2f2 ffffd000`e71c89c0 fffff803`9175990a : ffffe001`5a44e840 00000000`00000000 00000000`00000000 ffffe001`5be3a2b0 : nt!KiInitiateUserApc+0x70 ffffd000`e71c8b00 00000000`692a1e52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f 00000000`038df0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x692a1e52 STACK_COMMAND: kb SYMBOL_NAME: ONE_BIT FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7} Followup: MachineOwner[/quote]

 

yea i set it to auto and everything about a month ago after i was having the same problems also set the profile too i cant test memtest now but i will get it

 

could i also be that my ram its a 8gb kit and another 16gb kit of the same brand just diffrent timings one is 1600 and the other is 1866