[dantium]

I was having regular blue screen crashes with Windows 7 so decided to install Windows 8. After several attempts it eventually worked, but I am still getting lots of crashes. Can anyone help? I have pasted below some reports from WhoCrashed as I understand that they can help diagnose the problem.

System Information (local)
--------------------------------------------------------------------------------

computer name: DANTIUMTASTIC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Core™ i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8555474944 total
VM: 2147352576, free: 1918701568




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 18/11/2012 03:17:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111812-9296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0xA (0x7FE54397FE8, 0x2, 0x0, 0xFFFFF803CA390322)
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 that cannot be identified at this time.



On Sun 18/11/2012 00:51:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111812-10578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68029C00400, 0xA2000000000000, 0x0)
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 that cannot be identified at this time.



On Sat 17/11/2012 21:45:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111712-9406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A00DDC3220, 0xA01000, 0x462)
Error: REGISTRY_ERROR
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 registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17/11/2012 17:42:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111712-9203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x41793, 0xFFFFF6800000F000, 0x1, 0x0)
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 that cannot be identified at this time.



On Sat 17/11/2012 14:16:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111712-13218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x41284, 0x46AD001, 0x19B9, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Sat 17/11/2012 12:48:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111712-8937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8004B6C013D, 0x0, 0xFFFFFFFFFFFFFFFF)
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.



On Sat 17/11/2012 09:48:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111712-8515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68054782C50, 0x1, 0x0)
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 that cannot be identified at this time.



On Sat 17/11/2012 03:05:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111712-10546-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800D274DC8, 0xFFFFF8800D274600, 0xFFFFF80348CE247A)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 16/11/2012 16:39:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111612-21171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x5200, 0xFFFFFA8011437000, 0xD40C6ACCDFB62863, 0xD4CD6ACCDFB62863)
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 that cannot be identified at this time.



On Fri 16/11/2012 16:22:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111612-9125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x5200, 0xFFFFFA8011437000, 0xE20C552EBDF7BD57, 0xE2C5552EBDF7BD57)
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 that cannot be identified at this time.



On Fri 16/11/2012 15:56:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111612-11656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0xA (0x7FCCCAEFFE8, 0x2, 0x0, 0xFFFFF8018D78A322)
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 that cannot be identified at this time.



On Fri 16/11/2012 15:05:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111612-11296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x41284, 0x7FC95076001, 0x2B1, 0xFFFFF70001080000)
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 that cannot be identified at this time.



On Thu 15/11/2012 23:12:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111512-8671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x5200, 0xFFFFFA8011437000, 0x9C1A1225A973B649, 0x9CBA1225A973B649)
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 that cannot be identified at this time.



On Thu 15/11/2012 22:49:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111512-9109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x1A (0x5200, 0xFFFFFA8011437000, 0x621AFD613DDBCFA0, 0x6206FD613DDBCFA0)
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 that cannot be identified at this time.



On Thu 15/11/2012 22:25:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111512-9921-01.dmp
This was probably caused by the following module: unknown_module_fffff803c4687000 (nt+0x7A740)
Bugcheck code: 0x1A (0x5200, 0xFFFFFA8011437000, 0x331A2EF9B9B474D0, 0x33562EF9B9B474D0)
Error: MEMORY_MANAGEMENT
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_fffff803c4687000 .
Google query: unknown_module_fffff803c4687000 MEMORY_MANAGEMENT




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

17 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown_module_fffff803c4687000

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Advertisements]

Hello! I have to say that I am in the same exact boat as you. I don't know whether to start a new thread or just use the solutions posted on this one. I was having frequent crashes on windows 7 and so I upgraded to windows 8 two weeks ago. The random blue screens were stopped until last night. Now I cannot load windows for a minute without getting a crash. Safe mode is the only way I can boot my machine as of now.

I'm getting the same driver error as you are, ntoskrnl.exe (nt+0x7A740.

Also I receive the server memory management errors too. I've tried swapping hardware out but nothing has solved the problem yet. Any help would be much appreciated!

[chester129]

Hello! I have to say that I am in the same exact boat as you. I don't know whether to start a new thread or just use the solutions posted on this one. I was having frequent crashes on windows 7 and so I upgraded to windows 8 two weeks ago. The random blue screens were stopped until last night. Now I cannot load windows for a minute without getting a crash. Safe mode is the only way I can boot my machine as of now.

I'm getting the same driver error as you are, ntoskrnl.exe (nt+0x7A740.

Also I receive the server memory management errors too. I've tried swapping hardware out but nothing has solved the problem yet. Any help would be much appreciated!

[njscorreia]

Have you guys done a clean install or just an upgrade keeping the settings and files???

[chester129]

I did a clean install at first, and then just upgraded windows 7 to windows 8.

However, I found out what was giving me the frequent blue screens. I had a linksys usb wireless internet hub that was crashing me. I removed it from my pc and haven't crashed since!

[rshaffer61]

Your crash dumps indicate a possible bad memory issue so I would suggest starting there.

A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[Macboatmaster]

dantium

I appreciate that telling you this now is a little too late but

I was having regular blue screen crashes with Windows 7 so decided to install Windows 8

that was not the best way forward.

Your first approach should have been, at the very least - a reinstall of Windows 7, after other attempts to asscertain the reason for the crashes.

DO OF COURSE please continue with the recommendations of my good colleague rshaffer61 in respect of the memtest.

If you wish to attach your minidump or memory dump files whichever you have as a compressed ZIP file or files and not please as a compressed RAR file I will analyse them for you with a utlity that may give us a better clue than Who Crashed.

[rshaffer61]

Are you still having problems with your issue?
It has been 15 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.