Stressful crash, please help, havent gotten any support on this for weeks

p0rtal

Distinguished
Jan 28, 2012
116
0
18,680
900x900px-LL-c46be778_P1050530.jpeg


Situation - Had a rig that showcased a memory dump, mini dump error blue screen crash that was I wasnt able to find a fix for. Bought new ram, new SSD and upgraded to windows 8 just to make sure. That didn't work and the same error appeared On an unrelated note, my psu blew AND TOOK OUT EVERYTHING BUT MY SSD ALONG WITH IT, TOTALLY FRIED EVERYTHING so I decided screw it, I bought an entirely new pc rig.

New rig has the same ssd with all new ram and all new components. Everything was new and nothing was recycled except the os and ssd. I am getting the same error again. I used Whocrashed to capture it, here is what it listed. PLEASE FOR THE LOVE OF GOD SOMEONE TELL ME HOW TO FIX THIS. iS THIS A RAM ISSUE, OR A HARD DRIVE ISSUE, OR AN OS ISSUE? CAN I REALLY BE THAT UNLUCKY TO HAVE THIS ISSUE APPEAR ON MY FIRST SAMSUNG SSD WITH WINDOWS 7, THEN BUY A NEW SSD COMPLETELY FROM ANOTHER BRAND AND INSTALL WINDOWS 8 AND IT STILL HAPPENS, THEN BUY ALL NEW COMPONENTS AND IT CONTINUES? any help is appreciated smile.gif

On Fri 2/14/2014 6:22:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021414-3494-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800406D950, 0xFFFFFA800406DC30, 0xFFFFF800033807B0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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.



On Thu 2/13/2014 6:49:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-3697-01.dmp
This was probably caused by the following module: cdfs.sys (cdfs+0x16554)
Bugcheck code: 0x7A (0xFFFFF6FC40021958, 0xFFFFFFFFC000000E, 0x37620860, 0xFFFFF8800432B554)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\cdfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: CD-ROM File System Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 1/24/2014 2:47:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012614-3104-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80051C96C0, 0xFFFFFA80051C99A0, 0xFFFFF80002F867B0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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.
 

p0rtal

Distinguished
Jan 28, 2012
116
0
18,680
i set the ram from auto to 1066. I have kingston 4gb 1333 ram. Highest rated ram I could find, prior to that on my older rig I had three 4gb sticks from another brand and still had this issue. ill post again here if the crash happens after setting the ram to 1066 from auto
 

khicharkumar

Distinguished
May 18, 2010
283
0
18,860


Well i guess than only some guy with software knowledge ie. of that crash hexadecimal codes can solve your problem.
 

p0rtal

Distinguished
Jan 28, 2012
116
0
18,680
its absolutely looney tunes crazy that two different rigs with totally different components can share the same rare crash and nobody is able to help fix it lol...unreal. Talk about bad luck.
 

p0rtal

Distinguished
Jan 28, 2012
116
0
18,680
as mentioned, i had an ssd on the origin...bah here just read this timeline its easier to explain

-had nice i7 rig with samsung ssd and win8 installed. this error happened
-unable to get support for why it happened
-bought windows 7 and wiped the ssd, still had this error
-this rig blew up from unrelated faulty psu issue
-new rig purchased, new ocz ssd, fresh install of win7, all new componts, new ram

rare error still flashing and crashing my pc. I find this extremely unusual. I've gone into the bios and the ram was set to auto. I set it to 1066. Its a 1333 4gb kingston stick, so maybe that was the issue. So far, no crash but its only been an hour. lol. Sometimes the crash happens soon after a hard reboot, sometimes it can go 12 hours without happening. We will see and ill report back if it happens again.
 

p0rtal

Distinguished
Jan 28, 2012
116
0
18,680
I have a few programs right now but not many. Foobar2000, photoshop, chrome,thunderbird, malware bytes, steam, vlc media player and medieval cue splitter along with the os itself are really all i have going on. The virtual memory says its set to automatically managed, but its saying 6mb is recommended and that 4mb is allocated.

cdrie is system managed
edrive ( my ssd ) is none