New
#1
ntoskrnl.exe+71f00
the last 2,3 weeks i have multiple BSOD during the day...usually it happens when i play dod games , when i try to backup large files 4giga+ and sometimes but not to often when i see streaming movies....if i dont do anythng its possible to have a crash after 6,7 hours or not....firefox also crash a lot...
first i checked my 2 memory sticks seperatly (2048 MB DDR2-800 DDR2 SDRAM) with metest86+ and hcimemtest and found no errors...i replaced my gpu winth another system still crashes...i will also replace cpu and psu to see if something is wrong with them...i have nothing overclocked
then i run driver verifier to see if something is wrong with a driver....here are all the dump files i had the last week...
Attachment 373793
i unistall a couple of softwares than were incompatoble with win7 64 like acronis and partition magik8...i dont have anything installed from alcohol
#####################################################################
these are the results from BlueScreenView & WhoCrashedCrash List
Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time
101315-55785-01.dmp 13/10/2015 10:53:30 MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`270cd001 00000000`00018710 fffff700`01080000 ntoskrnl.exe ntoskrnl.exe+71f00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+71f00 C:\Windows\Minidump\101315-55785-01.dmp 4 15 7600 275.872 13/10/2015 10:55:56
101315-50700-01.dmp 13/10/2015 2:39:49 IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffff680`0001ba08 00000000`00000000 00000000`00000000 fffff800`02ae5ae2 ntoskrnl.exe ntoskrnl.exe+71f00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+71f00 C:\Windows\Minidump\101315-50700-01.dmp 4 15 7600 275.904 13/10/2015 2:42:19
101315-51729-01.dmp 13/10/2015 2:06:28 MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 fffff680`0000c2f0 1e700000`7ceb5867 fffff6fd`400245a8 ntoskrnl.exe ntoskrnl.exe+71f00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+71f00 C:\Windows\Minidump\101315-51729-01.dmp 4 15 7600 275.904 13/10/2015 2:09:52
#####################################################################
WhoCrashed
On Mon 12/10/2015 16:52:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101215-45614-01.dmp
uptime: 00:11:10
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41284, 0x278DC001, 0xA1F5, 0xFFFFF70001080000)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 12/10/2015 16:52:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:11:10
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41284, 0x278DC001, 0xA1F5, 0xFFFFF70001080000)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
Last edited by guilberto77; 17 Oct 2015 at 13:45.