Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

LuckyCla

Member
  • Content Count

    52
  • Joined

  • Last visited

Awards


This user doesn't have any awards

About LuckyCla

  • Title
    Member

Contact Methods

  • Discord
    matthew <3#8208

Profile Information

  • Gender
    Not Telling
  • Location
    in bed with your mum
  • Interests
    death
  • Biography
    i fell on my head
  • Occupation
    drinking

System

  • CPU
    Intel Core i5 2400 3.1ghz
  • Motherboard
    crap
  • RAM
    DDR3 8GB
  • GPU
    GeForce GTX 1070
  • Case
    uhm i forgot
  • Storage
    wd blue hdd 500gb
  • PSU
    corsair something its 550w
  • Display(s)
    viewsonic and acer monitors
  • Cooling
    the fans that came with but i am getting some rgb ones soon.
  • Keyboard
    walmart mechanical
  • Mouse
    tesla bootleg from amazon
  • Sound
    logitech headset
  • Operating System
    Windows 7 Pro / Windows 10 Pro / Ubuntu (sometimes)
  • PCPartPicker URL

Recent Profile Visitors

286 profile views
  1. I tried that yesterday and I didn't notice any crashes, but I had to put it on the lowest settings to run so it wasn't exactly like getting a crash with my GTX 1070. I ran tests of what I thought might make it crash, including going in and out of matches (it crashes on the loading screen a lot), having people scream in my ear through voice chat (sounds stupid but I thought that might be why my PC crashes when I play with people more than without), and joining an entire full 16 player lobby and still no crash. I can't afford a new GPU if this is the problem but my GPU is only 5 months old it shouldn't be broken by now.
  2. UPDATE: I just downloaded that and it also says healthy. I am very lost now and I would really like to know what is wrong with my PC.
  3. Okay. Also I would like to add that I have done a memory test, a CPU test, and part of an SSD test, and all of it is a pass. I watched the resource monitor when my game crashed and the CPU shot WAY up when it crashed. I don't know if it was before or after the crash. I even contacted epic games, and they told me to do things that I already did. I am getting impatient now because it has crashed more than ever today. If anyone knows anything about how to fix it, please help.
  4. I used the program you told me to use but it only showed me the drive speeds and said nothing about drive health. Either I'm stupid (probably the problem), or the program doesn't have that feature.
  5. This thread is a repost, so go to the original thread where I said all my PC specs:
  6. I tried the memory thing and it worked for a minute, at least I thought. The next day it started crashing again. I had these problems a while ago and I reinstalled Windows and they were gone for a long while, until about a month ago when they came crawling back.
  7. It didn't work. I tried all of those methods and It still crashes just as much.
  8. Because people stopped answering and I desperately need an answer. I'm sorry if that is against the rules. I didn't know.
  9. I have been playing fortnite almost every day, and every day I encounter several game crashes with the error: unhandled exception, and I have been getting BSODs while in game or right after closing the game. My BSOD errors are: KMODE_EXCEPTION_NOT_HANDLED, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, KERNEL_SECURITY_CHECK_FAILURE, IRQL_NOT_LESS_OR_EQUAL, DRIVER VIOLATION DETECTED (while i was using driver verifier), and MEMORY_MANAGEMENT. Please help me because no one has an answer to this problem yet and it is just luck if I can make it to the top 3 without a crash. The crashes also increase when I play with people. If I play with a whole squad or even just 2 other people, the game will give me the unhandled exception error almost every time I get to the match loading screen. I have some of the crash dumps from the crashes today: On Sun 5/19/2019 16:54:52 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\051919-5265-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0) Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF83, 0x2, 0xFFFFF805759F973F, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that invalid system memory has been referenced. 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. On Sun 5/19/2019 16:54:52 your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x90D3B) Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF83, 0x2, 0xFFFFF805759F973F, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA Bug check description: This indicates that invalid system memory has been referenced. 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. On Sun 5/19/2019 13:55:14 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\051919-5796-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0) Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  10. I think you should try to use a different power supply. Sometimes power supplies burn out and stop producing power. It could also be that the power supply was being hurt by the mobo and your mobo could also be dying.
  11. Idk because I reinstalled windows and fortnite to try to fix it before and no luck, but before that it crashed in other apps and websites too. Also, I read online that Windows 10 compresses drivers in the memory or something, so if I use Windows 7, will the issue stop?
  12. Asus P8Z77 board GIGABYTE Geforce GTX 1070 OC 8gb DDR3 PC3 RAM Intel Core i5 3770 WD Blue Caviar HDD 500gb Samsung SSD 500gb Corsair CX550M psu
  13. I have been playing fortnite almost every day, and every day I encounter several game crashes with the error: unhandled exception, and I have been getting BSODs while in game or right after closing the game. My BSOD errors are: KMODE_EXCEPTION_NOT_HANDLED, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, KERNEL_SECURITY_CHECK_FAILURE, IRQL_NOT_LESS_OR_EQUAL, DRIVER VIOLATION DETECTED (while i was using driver verifier), and MEMORY_MANAGEMENT. Please help me because no one has an answer to this problem yet and it is just luck if I can make it to the top 3 without a crash. The crashes also increase when I play with people. If I play with a whole squad or even just 2 other people, the game will give me the unhandled exception error almost every time I get to the match loading screen. I didn't save the crash logs so if you needed it I'm very sorry.
  14. I thought about it and this seems right. I think this is the issue because I stumbled upon a forum that said: " For windows 7, I keep getting messages saying that appdata local temp folder is corrupt. dskchk will not repair and system restore fails dskchk on reboot hangs. Everything else seems normal other than programs that depend on the temp folder. Can't restore prior version of temp folder. Thanks to anyone with suggestions. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. Answer I found a solution. Go to All Programs from start menu and go to Maintenance. Select create a system repair disc (you will create a DVD). Boot off the DVD and you will have several recovery options. Select fix on start up and an attempt to repair disc will begin. It may take a while (an hour or two), but it will tell you when it is finished. The rest is obvious and the problem goes away. I suggest cleaning up the temp file once you can access it. I think you will want to create an OS image recovery disc after this. I wish I had done that to start with. Windows 7 is solid."
×