How can I check my memory dump?

[refmon]

My sister told me that the computer restarted and showed her an error but how I can check?

 

[P1nnacle]

I personally use WhoCrashed, easy to use program.

 

[refmon]

Thanks, it showed me what was wrong but can anybody tell me how I can fix it?


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 2013-11-08 3:12:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110813-20718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF803EDE8EB25, 0xFFFFFA8007CCBB00, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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.

 

[P1nnacle]

Sounds like you're missing a driver, I'd go into device manager and check out which drivers are missing. you can download and install them.

 

[refmon]

I checked all of my devices but an exclamation point didn't appear next to any of them, what else can I do?

 

[P1nnacle]

Make sure all of your drivers are updated, just because one is there, doesn't mean it isn't causing the problem.

 

[refmon]

Well I updated my videocard so now I just wait to see if the problem occurs again?

 

[P1nnacle]

Yeah, it may be have just been a one time error, but if it crashes again, let us know.

 

[refmon]

Alright so it crashed again, this time it was after a atuomatic windows update after I shut down my computer yesterday. This is what it told me: Error: CRITICAL_STRUCTURE_CORRUPTION

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 2013-11-16 6:18:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111613-30312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x109 (0xA3A039D8A180EC26, 0xB3B7465EF3FDEBFE, 0xFFFFF8029AC7F6DC, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[refmon]

It happened again

On Thu 2013-11-28 11:05:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112813-22812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x77 (0x1, 0xFFFFF8A0031422CE, 0x0, 0xFFFFF8800BE8C7C0)
Error: KERNEL_STACK_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
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 2013-11-28 11:05:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x77 (0x1, 0xFFFFF8A0031422CE, 0x0, 0xFFFFF8800BE8C7C0)
Error: KERNEL_STACK_INPAGE_ERROR
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.