Windows 10 is getting on my nerves

[Kunal_5]

Hi guys.... Here is the thing... My pc was just updated to win 10 anniversary edition and it started lagging during general usee
... However for gaming ut was just fine... But still i decided to give the system a clean install... I had windows 10 ver 1607( anniversary edition) on my new pen drive so i installed it... Everything went fine but when i started to do windows updates everytime there came a blue screen error like memory_management and stopcode error but i still gave a blind eye to it... the updates never completed and got stuck after restart .... This caused me to reinstall windows about 5 times and yesterday again an error came but the update completed... I was happy... So i started downloading games and when they downloading on steam again tje blue screen errors came and the computer frequently restarted.. apart from that ,no game was downloaded fully as each game missed an important file or two and i had to redownload it but still the games never downloaded completely... I am sick of Windows 10 ... I was using it for the past 4 months but no such thing happened with windows... I dont know what to do... This thing has wasted my 3 complete days... Please guys tell me what to do... Show me the path

 

[Manish Tewari]

Option 1. SFC/SCANNOW is Microsoft’s tool for resolving various system problems, and even if it doesn’t sound like an actual solution, many ppl received this error message, even after multiple restarts, said that SFC/SCANNOW command resolved the issue.

@C:\ Windows\ system 32 enter this following line into Command Prompt and press Enter: sfc/scannow

- let it complete and check if it has fixed any errors - restart your system after that whether errors fixed or not.

Option 2. Run win diagnostic tool for memory:

Go to Search, type windows diagnostic tool and open Windows Memory Diagnostic Tool

"Choose Restart now and check for problems"

Let your computer restart, and on the next startup, the tool will report if something’s wrong with your RAM memory

i hope that works for you.

 

[Paul NZ]

Dont use the windows memory program, it's too short and it's useless. Use memtest

If you can get into it upload the small dmp files to onedrive. Then post the link

 

[Manish Tewari]

IMO memtest is not definitive if stopcode errors are popping with mem mgmt, also i do not think by the error description there is a leak happening

 

[Kunal_5]

Option 1. SFC/SCANNOW is Microsoft’s tool for resolving various system problems, and even if it doesn’t sound like an actual solution, many ppl received this error message, even after multiple restarts, said that SFC/SCANNOW command resolved the issue.

@C:\ Windows\ system 32 enter this following line into Command Prompt and press Enter: sfc/scannow

- let it complete and check if it has fixed any errors - restart your system after that whether errors fixed or not.

Option 2. Run win diagnostic tool for memory:

Go to Search, type windows diagnostic tool and open Windows Memory Diagnostic Tool

"Choose Restart now and check for problems"

Let your computer restart, and on the next startup, the tool will report if something’s wrong with your RAM memory

i hope that works for you.

Thanks bro for replying... Will tell what happens in about 5-6 hours since i am not currently at home... Will definiteky rply .. thanks bro for helping out

 

[Colif]

Perhaps we should look at the errors and see what they say?

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Kunal_5]

Option 1. SFC/SCANNOW is Microsoft’s tool for resolving various system problems, and even if it doesn’t sound like an actual solution, many ppl received this error message, even after multiple restarts, said that SFC/SCANNOW command resolved the issue.

@C:\ Windows\ system 32 enter this following line into Command Prompt and press Enter: sfc/scannow

- let it complete and check if it has fixed any errors - restart your system after that whether errors fixed or not.

Option 2. Run win diagnostic tool for memory:

Go to Search, type windows diagnostic tool and open Windows Memory Diagnostic Tool

"Choose Restart now and check for problems"

Let your computer restart, and on the next startup, the tool will report if something’s wrong with your RAM memory

i hope that works for you.

Guys i think my ram is faulty... I just think that because now i have windows 10 ver 1511 which i earlier also had. I just installed it and again a blue screen error came unfortunately i want able to read what error it was but it certainly hadn't occurred earlier.... What to do??.... What do u think

 

[Manish Tewari]

Option 1. SFC/SCANNOW is Microsoft’s tool for resolving various system problems, and even if it doesn’t sound like an actual solution, many ppl received this error message, even after multiple restarts, said that SFC/SCANNOW command resolved the issue.

@C:\ Windows\ system 32 enter this following line into Command Prompt and press Enter: sfc/scannow

- let it complete and check if it has fixed any errors - restart your system after that whether errors fixed or not.

Option 2. Run win diagnostic tool for memory:

Go to Search, type windows diagnostic tool and open Windows Memory Diagnostic Tool

"Choose Restart now and check for problems"

Let your computer restart, and on the next startup, the tool will report if something’s wrong with your RAM memory

i hope that works for you.

Guys i think my ram is faulty... I just think that because now i have windows 10 ver 1511 which i earlier also had. I just installed it and again a blue screen error came unfortunately i want able to read what error it was but it certainly hadn't occurred earlier.... What to do??.... What do u think

Mem gone bad was what i was suspecting from the beginning, borrow working ram stick from someone see how that works out for you.

If your mem sticks are under warranty go for RMA route.

 

[Kunal_5]

Option 1. SFC/SCANNOW is Microsoft’s tool for resolving various system problems, and even if it doesn’t sound like an actual solution, many ppl received this error message, even after multiple restarts, said that SFC/SCANNOW command resolved the issue.

@C:\ Windows\ system 32 enter this following line into Command Prompt and press Enter: sfc/scannow

- let it complete and check if it has fixed any errors - restart your system after that whether errors fixed or not.

Option 2. Run win diagnostic tool for memory:

Go to Search, type windows diagnostic tool and open Windows Memory Diagnostic Tool

"Choose Restart now and check for problems"

Let your computer restart, and on the next startup, the tool will report if something’s wrong with your RAM memory

i hope that works for you.

Guys i think my ram is faulty... I just think that because now i have windows 10 ver 1511 which i earlier also had. I just installed it and again a blue screen error came unfortunately i want able to read what error it was but it certainly hadn't occurred earlier.... What to do??.... What do u think

Mem gone bad was what i was suspecting from the beginning, borrow working ram stick from someone see how that works out for you.

If your mem sticks are under warranty go for RMA route.

Can the issue be due to hdd... I am not sure of anything and i can't borrow anything so i will have to buy the hardware and be sure of it... But i have a spare hard disk lying around...i will test that and message back in 2-3 hours

 

[Kunal_5]

Option 1. SFC/SCANNOW is Microsoft’s tool for resolving various system problems, and even if it doesn’t sound like an actual solution, many ppl received this error message, even after multiple restarts, said that SFC/SCANNOW command resolved the issue.

@C:\ Windows\ system 32 enter this following line into Command Prompt and press Enter: sfc/scannow

- let it complete and check if it has fixed any errors - restart your system after that whether errors fixed or not.

Option 2. Run win diagnostic tool for memory:

Go to Search, type windows diagnostic tool and open Windows Memory Diagnostic Tool

"Choose Restart now and check for problems"

Let your computer restart, and on the next startup, the tool will report if something’s wrong with your RAM memory

i hope that works for you.

Guys i think my ram is faulty... I just think that because now i have windows 10 ver 1511 which i earlier also had. I just installed it and again a blue screen error came unfortunately i want able to read what error it was but it certainly hadn't occurred earlier.... What to do??.... What do u think

Mem gone bad was what i was suspecting from the beginning, borrow working ram stick from someone see how that works out for you.

If your mem sticks are under warranty go for RMA route.

I also thought of another thing.... Before 1511 version when i installed anniversary update a blue screen error came named MEMORY_MANAGEMEMT can it mean that ram is faulty

 

[Colif]

Bug Check 0x1A: MEMORY_MANAGEMENT
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

MS Error description

They can be caused by ram, drivers or perhaps even hdd

Are you still getting the bsod or was this from a previous install and its not happening now? If its still happening, can you download and run who crashed: http://www.resplendence.com/whocrashed
it will give us a summary of the error and perhaps from the codes it supplies, we can work out what cause is.

copy/paste here.

the minidumps I suggested before would also do same thing.

 

[Kunal_5]

Bug Check 0x1A: MEMORY_MANAGEMENT
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

MS Error description

They can be caused by ram, drivers or perhaps even hdd

Are you still getting the bsod or was this from a previous install and its not happening now? If its still happening, can you download and run who crashed: http://www.resplendence.com/whocrashed
it will give us a summary of the error and perhaps from the codes it supplies, we can work out what cause is.

copy/paste here.

the minidumps I suggested before would also do same thing.

Ok..i will try to post the results in an hour and about the error u said, that was exactly the one which u said... Thanks for the support u guys are giving.. Thanks a lot
Edit: i forgot one thing... This error is coming since the previous installs and is still persisting

 

[Kunal_5]

Guys how to post an image here

 

[Manish Tewari]

Hi Kunal, Just read your concerns regarding HDD - i do not think that there is any issue with you your hdd

Update: to post image: use this guide http://www.tomshardware.com/answers/id-2173703/post-images-tomshardware-guide.html

 

[Kunal_5]

Hi Kunal, Just read your concerns regarding HDD - i do not think that there is any issue with you your hdd

Update: to post image: use this guide http://www.tomshardware.com/answers/id-2173703/post-images-tomshardware-guide.html

See guys this is the error that came. http://m.imgur.com/YqxrbD5

 

[Colif]

the minidump or who crashed report may show the driver responsible for that error

Bug Check 0x133 DPC_WATCHDOG_VIOLATION
The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above. DPCs should not run longer than 100 microseconds and ISRs should not run longer than 25 microseconds, however the actual timeout values on the system are set much higher.

MS Bug description

 

[Kunal_5]

the minidump or who crashed report may show the driver responsible for that error

Bug Check 0x133 DPC_WATCHDOG_VIOLATION
The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above. DPCs should not run longer than 100 microseconds and ISRs should not run longer than 25 microseconds, however the actual timeout values on the system are set much higher.

MS Bug description

I still haven't run the bug report side the windows update is still going on... Will upload it asap
And what to do about this http://m.imgur.com/wdWFQfH

 

[Colif]

what error is it showing, click on the blue error links...

what motherboard do you have? Did you update drivers after installing windows?

 

[Kunal_5]

what error is it showing, click on the blue error links...

It is showing nothing.. Just shows info about the update

 

[Colif]

did any of them finish?

what motherboard do you have? Did you update drivers after installing windows? If you installed drivers for motherboard, its possible windows update just tried to grab drivers you already had. Win 10 tries to get software that matches your hardware but its not always the most up to date.

 

[Kunal_5]

did any of them finish?

what motherboard do you have? Did you update drivers after installing windows? If you installed drivers for motherboard, its possible windows update just tried to grab drivers you already had. Win 10 tries to get software that matches your hardware but its not always the most up to date.

I have a h110m and i didn't Intel any drivers for mobo... And about the windows updates they always get stuck so i stopped the update and ran Whocrashed... Nope what days do i have to send u

 

[Kunal_5]

Should i do crash dump test and it yes then at what parameters?

 

[Kunal_5]

And here are shocrash reprt after i pressed analyze. http://m.imgur.com/8cs1Cjg,bbnztNF

 

[Colif]

Faulty Hardware Corrupted Page - name is misleading

Causes of FAULTY_HARDWARE_CORRUPTED_PAGE Blue Screen Errors
Incorrectly configured, old, or corrupted device drivers. (very common)
Corruption in Windows registry from a recent software change (install or uninstall).
Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
Driver conflict after installing new hardware.
Damaged or removed system files after you’ve installed software or drivers related to Windows Operating System.
Error 0x12B blue screen caused by a damaged hard disk.
FAULTY_HARDWARE_CORRUPTED_PAGE STOP error due to memory (RAM) corruption.

Go Here and download AI Suite 3 from the utility tab, then run it and look on the Ezy Update tab as it should check your motherboard and grab all the drivers you need.

 

[Kunal_5]

Faulty Hardware Corrupted Page - name is misleading

Causes of FAULTY_HARDWARE_CORRUPTED_PAGE Blue Screen Errors
Incorrectly configured, old, or corrupted device drivers. (very common)
Corruption in Windows registry from a recent software change (install or uninstall).
Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
Driver conflict after installing new hardware.
Damaged or removed system files after you’ve installed software or drivers related to Windows Operating System.
Error 0x12B blue screen caused by a damaged hard disk.
FAULTY_HARDWARE_CORRUPTED_PAGE STOP error due to memory (RAM) corruption.

Go Here and download AI Suite 3 from the utility tab, then run it and look on the Ezy Update tab as it should check your motherboard and grab all the drivers you need.

Sorry forgot to tell u that mine is a gigabyte board... What to do for it?