New
#1
BSOD ntoskrnl.exe (nt+0x75C00)
Hello
My computer was fine untill today when all of a sudden I heard it restarting from the kitchen. I went in and I had no idea why it restarted so I just let it boot up again. Then I got an BSOD and I have gotten several since using WhoCrashed I have managed to get them all because I had log saving on.
It appears that all BSODs have had different causes.
If there is anything that you want me to do then please don't hesitate to ask. I found this link thread from this very same forum but it did not help me.Code:On Sat 2013-04-20 17:57:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\042013-8907-01.dmp uptime: 00:03:40 This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0xEE86, 0xEE842001DD0C) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. 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 which cannot be identified at this time. On Sat 2013-04-20 17:57:01 GMT your computer crashed crash dump file: C:\Windows\memory.dmp uptime: 00:03:40 This was probably caused by the following module: ntfs.sys (Ntfs+0x9AA6F) Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0xEE86, 0xEE842001DD0C) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that a severe memory management error occurred. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 2013-04-20 17:19:02 GMT your computer crashed crash dump file: C:\Windows\Minidump\042013-6068-01.dmp uptime: 00:00:35 This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800037B3CD0, 0x0, 0x20000000) 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 which cannot be identified at this time. On Sat 2013-04-20 07:50:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\042013-6692-01.dmp uptime: 00:00:08 This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1A (0x31, 0xFFFFFA800AFF0B50, 0xFFFFF88003E57000, 0xFFFFF8A001F6F98D) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. 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 which cannot be identified at this time. On Sat 2013-04-20 07:12:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\042013-9562-01.dmp uptime: 00:04:39 This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0xA (0xFFFFF6800000CD40, 0x0, 0x0, 0xFFFFF80003598545) Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 which cannot be identified at this time.
"ntoskrnl.exe" BSOD
I have tried checking for RAM errors in windows, that screen just rebooted my PC without telling me anything... I have tried resetting boot.ini
What to do? D:
I am reading the posting instructions now, I just wanted to get this thread up before a new BSOD shows up.