thomja Posted April 21, 2013 Share Posted April 21, 2013 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. 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. Alright so after hours and hours of memtesting with the two main blue slots on my motherboard I have tried each memory individually on each of the two blue slots (I have 4 total slots but I only use the 2 blue ones). When I tested the memorys by themselves on the two slots separately I got 0 errors (after 1 pass). But when I try them both together I have got different results, the test I did yesterday gave me 44 errors. I tried them both again today and only got 2 errors. And they were in the same slots as yesterday. I have yet to try to change the slots of them tho. My memory: 2x4 GB CMX8GX3M2A1333C9 That's what I purchased. Uses it with an intel core i7 3770 and a P8Z77-V LX What does this mean? how can I get different errors? Link to comment Share on other sites More sharing options...
peanutz94 Posted April 21, 2013 Share Posted April 21, 2013 Those are all generic errors and could point towards just about anything. Have you installed any new software or hardware recently? 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. It could also be a bad slot on the MB. Try using the other two slots and see if you still get the same sort of issues. But from the crash report it looks like a software /driver issue. Link to comment Share on other sites More sharing options...
thomja Posted April 22, 2013 Author Share Posted April 22, 2013 What is the difference between using the RAM modules in different slows than the two blue ones(except for that in my case it might solve the problem)? Link to comment Share on other sites More sharing options...
peanutz94 Posted April 22, 2013 Share Posted April 22, 2013 What is the difference between using the RAM modules in different slows than the two blue ones To rule out a bad memory slot on the MB. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.