[SELF-SOLVED] PC freezes then restarts, No BSOD Windows 7 *CRASH DUMP FILES INCLUDED*

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1
Hello People of the Tom's Hardware,

I need help with my PC, it just restarts for like 5 times within 5 minutes of each other when I turn it on, then it would just calm down and not restart at all. I recently reinstalled Windows 7 back from Windows 10 because I thought that was the problem but it is still going. This has been happening since I got the PC which was back in 2014 and I had to put up with it, it would be highly appreciated if you guys knew a solution, sometimes it would just freeze and not restart at all and I have to manually press the button.
I am really desperate to get this fixed because it is a real pain in the backside when I am gaming and out of nowhere it freezes then restarts :)

Here is what it says in Windows 7:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80087B4708
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070616-20732-01.dmp
C:\Users\AndrewX\AppData\Local\Temp\WER-25038-0.sysdata.xml

1st File: https://drive.google.com/open?id=0B4aHa9FJFm6CSWp5dGlvLUxRUHc
2nd File: I could not find

This is everything else in the 'Minidump' folder:
https://drive.google.com/open?id=0B4aHa9FJFm6CdUUyMXNUdEF5aVk
https://drive.google.com/open?id=0B4aHa9FJFm6CWXJjUFJraFlhRTQ
https://drive.google.com/open?id=0B4aHa9FJFm6CZHdwMkhSYk1yVTg

Thanks in advance!

*EDIT*

I checked my dump files on WhoCrashed and they all said the same thing which was:

On Wed 7/6/2016 3:48:23 PM GMT your computer crashed
On Wed 7/6/2016 4:46:06 PM GMT your computer crashed
On Wed 7/6/2016 4:49:56 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\070616-20732-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80087B4708, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Anyone have any idea what these are?

 
seems like u r too late...one of ur hardwares might be messing up from the beggining...why didnt u get it checked when u started getting this issue???
bccode 124 is usually heat related than driver related...but driver cud be problem as well...
wat r ur specs, and wat temp are ur parts running???
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


Currently, I'm getting this bootup error (fwpkclnt.sys) and so I can't get that infomation
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


CPU: AMD FX-6300 6 Core Black Edition Processor
Motherboard: Gigabyte GA-78LMT-USB3
RAM: DDR3 1333 *I can provide more detail if you want*
HDD: 1TB *I can provide more detail if you want*
Graphics Card: Palit Nvidia Geforce 640
PSU: *I don't think the PSU matters, but tell me if you need this infomation*

I am not sure how much my system draws on a 12v rail.
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


I only have 1 RAM stick, but I will still try reseating them, doing the MemTest86 test and seeing if the problem still occurs.
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


I only have 1 RAM stick, but I will still try reseating them, doing the MemTest86 test and seeing if the problem still occurs.
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


Alright, I ran the MemTest with the RAM on different slots and these are the results, I have the standard 4 RAM slots:

Slot 1= Passed, No Errors (Still Restarts)
Slot 2= Passed, No Errors (Still Restarts)
Slot 3= Passed, No Errors (Still Restarts)
Slot 4= RAM slot is broken, so I couldn't test it.
 
well...if wat u have posted above is accurate, then ur slots may be the issue...
if its not restarting on slot 1, but restating on every other, except 4 ofcourse, then the slots are faulty...
which slot was it in all this while since 2014???
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


It restarted when it was in slot one, I got excited there when it didn't restart :/
Also I changed the RAM to different slots during the years and it showed the same result and still crashed
 
do u have any other ram that u can put ur hands on???
we are running out of options here...and unless u can grab substitute ram/psu to test with, it will be pretty difficult to figure out...
reset the motherboard cmos and jumper pins...see if that makes a difference...
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


Unfortunately I do not have any other RAMs or PSUs to work with.
How do I reset the motherboard cmos and jumper pins?
 
drain ur cmos battery completely for 20-30mins atleast...
for jumper reset....
Remove the side panel, locate and remove the CMOS battery. Locate the BIOS configuration jumper for your motherboard (often very close to the battery, refer to your manual for additional information) and move the jumper from pins 1 & 2 to pins 2 & 3. After ~5-10 seconds, move the jumper back to the original pins.
 

AndrewDafuqq

Reputable
Feb 9, 2015
114
0
4,690
1


I removed the CMOS battery but I can't seem to find the BIOS configuration jumper.

http://imgur.com/a/yaqIf
http://imgur.com/a/n2NmF

Sorry about the image quality.
 
have any frnd tht u can borrow spares from???
else the only other alternative will be...to go to a professional store...and let them figure out...
thy wont charge too much to figure the issue...but they will charge to fix the issue...
but, if u dont fix, atleast u ll have an idea whr to look at...
 

Similar threads


ASK THE COMMUNITY