Blue screen --> minidump and not user.dmp Your debug report report is the user dump and not the minidump. You can find the minidump at the folder...
Faulty RAM ?? All of your minidumps showed that the crashes are caused by faulty memory. Reseat your memory module to another memory slot. If it...
Memory error Your first minidump has 12 memory errors and the 2nd minidump is crashed with bugcheck code 1A. They are crashed by memory error....
Hardware problem The 1st minidump is crashed at TCPIP and it usually caused by faulty ram. The 2nd minidump is crashed with bugcheck code 9C...
Faulty memory Your debug report shows that there have two memory error and this is the symptom of faulty ram. Reseat the memory module to another...
This is not compatibility issue between the ram and m/b. If you have spare ram from another PC, swap the ram.
From the stack trace, it is memory problem. Some faulty ram can pass memtest. Make sure that the ram is compatible to the motherboard. For...
?? Mixed RAM This is hardware problem due to bus connection time out, It maybe related to TV cards, mixed ram, hyperthreading, IDE hard disk is...
Faulty ram Your nVidia Motherboard device driver are on year 2005. I doubt they are the latest. >> f6cac000 f6cbc480 nvarm nvarm.sys Wed May 26...
Faulty ram usbuchi.sys is USB miniport device driver. Only HP USB printer has known software problem at usbuchi.sys. If you are not using HP USB...
At my first post I mentioned that one minidump is insufficient to find out the root cause. Attach the latest debug report (ie the minidump after...
Maybe faulty ram One minidump is insufficient to find out the root cause of the problem. Attach more debug reports here if you have. Your windows...
Hardware error The latest minidump is a partial dump and it is symptom of hardware error (ie RAM or PSU). Bugcheck code FE is also related to...
Usually bugcheck code C5 is related to faulty ram. Run memtest to stress test the ram. However a minidump is insufficient to confirm the culprit....
win32k is windows GDI FYI Your debug report shows that your windows is crashed at win32k.sys which is GDI (Graphical Display Interface). GDI...
Bad paging space maybe related to hard disk error. CHKDSK can only fix software error and it cannot fix hardware problem.
Hardware error Hi, Your windows is crashed at IRQL x'1c' which is the timer IRQL and this is the symptom of hardware error (ie RAM, CPU or...
Hi, One minidump is insufficient to find out the root cause of the problem. If you have 4 to 5 minidumps with exactly the same symptom, this is...
More minidumps to find out the culprit In general 1 minidump is insufficient to find out the culprit. We need at lease 4 to 5 minidumps. If all...
Of course, it is hardware error. Bugcheck code 124 is related to WHEA (Windows Hardware Error Aritcheture).
Separate names with a comma.
