Jump to content

Computer keeps crashing, help please?

alperamop
 Share
Posted

If you can write down the error message, it would help in trying to resolve the issue.

CPU Cooler Tier List  || Motherboard VRMs Tier List || Motherboard Beep & POST Codes || Graphics Card Tier List || PSU Tier List 

 

Main System Specifications: 

 

CPU: AMD Ryzen 9 5950X ||  CPU Cooler: Noctua NH-D15 Air Cooler ||  RAM: Corsair Vengeance LPX 32GB(4x8GB) DDR4-3600 CL18  ||  Mobo: ASUS ROG Crosshair VIII Dark Hero X570  ||  SSD: Samsung 970 EVO 1TB M.2-2280 Boot Drive/Some Games)  ||  HDD: 2X Western Digital Caviar Blue 1TB(Game Drive)  ||  GPU: ASUS TUF Gaming RX 6900XT  ||  PSU: EVGA P2 1600W  ||  Case: Corsair 5000D Airflow  ||  Mouse: Logitech G502 Hero SE RGB  ||  Keyboard: Logitech G513 Carbon RGB with GX Blue Clicky Switches  ||  Mouse Pad: MAINGEAR ASSIST XL ||  Monitor: ASUS TUF Gaming VG34VQL1B 34" 

 

Link to post
Share on other sites
Posted

As it's been stated, If you could right down the error msg, it would be extremely helpful 

 Crust : Intel Core i5 4690K @ 4.4Ghz 1.45v  |  Motherboard : MSI Z97 MPower  |  Fruity Filling : MSI GTX 960 Armor 2Way-SLI |  Cooling : Noctua NH-D15  |  RAM : 16GB Corsair Vengeance 1600Mhz | Storage : 2xSamsung 840 EVO 500GB SSDs Raid-0  |  Power Supply : Seasonic X-Series 1250W 80+Gold  |  Monitor : Dell U2713HM 27" 60Hz 1440p  |                                                                                                                                           

Link to post
Share on other sites
Posted
  • Author
8 minutes ago, Mazeman03 said:
9 minutes ago, alperamop said:

Running Windows 10. It will show me the blue screen at the most random times. It's never the same error message. Is there anyone that can please help me?

 

8 minutes ago, CommanderAlex said:

If you can write down the error message, it would help in trying to resolve the issue.

 

5 minutes ago, LawrenceBarnes2013 said:

As it's been stated, If you could right down the error msg, it would be extremely helpful 

The latest was: Memory_management. Before that it was: PAGE_FAULT_IN_NONPAGED_AREA, REFERENCE_BY_POINTER, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (FLTMGRSYS), IRQL_NOT_LESS_OR_EQUAL. etc. what is the error bb

 

5 minutes ago, LawrenceBarnes2013 said:

As it's been stated, If you could right down the error msg, it would be extremely helpful 

 

7 minutes ago, CommanderAlex said:

If you can write down the error message, it would help in trying to resolve the issue.

 

The latest was: Memory_management. Before that it was: PAGE_FAULT_IN_NONPAGED_AREA, REFERENCE_BY_POINTER, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (FLTMGRSYS), IRQL_NOT_LESS_OR_EQUAL. etc.

Link to post
Share on other sites
Posted

Do you remember a specific driver stated in the error message? A lot of the Win 10 bugs are coming from drivers not optimized for the OS. To properly debug it were going to need the full error message. Otherwise your basically left with disabling and/or updating drivers for all hardware, and doing the same for non MS software, one at a time until the blue screens stop. Check Reliability Monitor for crash events.

Link to post
Share on other sites
Posted
  • Author
4 minutes ago, lowlyf said:

Do you remember a specific driver stated in the error message? A lot of the Win 10 bugs are coming from drivers not optimized for the OS. To properly debug it were going to need the full error message. Otherwise your basically left with disabling and/or updating drivers for all hardware, and doing the same for non MS software, one at a time until the blue screens stop. Check Reliability Monitor for crash events.

 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000041792, 0xfffff680000d36a8, 0x0000000040000000, 0x0000000000000000)

Link to post
Share on other sites
Posted
  • Author
4 minutes ago, lowlyf said:

That's a bad hardware driver but it's generic. I don't know which hardware is causing it. Start updating hardware drivers one by one. Also check event viewer for any other information as to which driver it is.

 

I think I already had updated everything. But is it possible it's my monitor? It all started happening 2 months ago since I bought it. It also won't show my monitor by its name in device manager. Just as Generic PnP Monitor.

Link to post
Share on other sites
Posted

Ntoskrnl is the windows kernel. It's what Windows is comprised of. Most likely Windows has provided a driver for a piece of hardware, and it is not compatible in certain hardware use cases. Jump into device manager and start looking driver updates or new drivers. If they are brand new and from around the time the bsods started, roll them back. If they are outdated, update them.

Link to post
Share on other sites
Posted
  • Author
2 minutes ago, lowlyf said:

The monitor is a passive output device, and shouldn't cause these issues. However I've seen new monitors cause video graphics devices to update because of increased functionality of the new monitor.

 

I've got g-sync on it, + it's a 144hz monitor combined with another monitor which is 60hz, both hooked up to my gtx 980ti. Could this be the problem?

Link to post
Share on other sites
Posted

And happy hunting. There are guys in forums that will give you a small piece of software that will grab your full bsod dump and be able to provide more info. They are much better than I am at reading them. From experience I'd say stay away from 3rd party utilities that claim to fix bsods. If you do use them back up files and registry before hand. Hopefully diligence and trial and error will solve your problem quickly. I understand how frustrating BSODs can be in regards to productivity and even gaming.

Link to post
Share on other sites
Posted
  • Author
2 minutes ago, lowlyf said:

Check device manager driver update dates and times and cross reference them with your bsod dates and times. Check for both the different dates/times for ntoskrnl and win32kfull.

That won't really tell me anything. These also weren't all the crashdumps, since I've reinstalled windows 10 twice..

Link to post
Share on other sites
Posted

Again it sounds to me like hardware or a hardware driver isn't playing nice with Windows. There are forums specifically for debugging BSODs. All I can provide is my experience with troubleshooting them, and the deductive reasoning I used to do so. Due to the wide range of Hardware, drivers, and Windows 10 being new (garbage BTW) it will take someone that can look at the BSOD dumps more thoroughly than I am able to do so to pinpoint your problem. Sorry I couldn't help more.

Link to post
Share on other sites
Posted

Also run memtest86. I just googled the bugchecks listed above. Seems it has to do with memory or your memory controller, (if software isn't causing the issue) If memtest86 succeeds, try running one stick of RAM at a time. Could also be your memory controller is too hot. If the memory controller is on your CPU, check CPU temps.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×