BSOD Win7 x64 : Caused By Driver : ntoskrnl.exe

Faeken · 04 Jul 2012

Hi everybody,

Before all, i'm sorry for my bad english ! That's the french style

Well, I have a big problem with my PC that does not stop me from snapping BSOD !
After complete reinstallation of the OS, nothing to do, it inevitably comes back ...

Some information if you can help me ... Thank you very much to the community that will get me out!

Official Windows 7 X64
updated Antivirus Security Essential
BIOS updated ...

==================================================
Dump File : 070312-13681-01.dmp
Crash Time : 03/07/2012 08:28:54
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`1e864854
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`012a2a35
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70040
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17017 (win7_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+70040
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070312-13681-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 286 864
==================================================
==================================================
Dump File : 062312-9063-01.dmp
Crash Time : 23/06/2012 12:00:05
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`124752d1
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`02f19521
Parameter 4 : 00000000`00000002
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+5fbc
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062312-9063-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 284 432
==================================================
RAMMon v1.0 Build: 1005 built with SysInfo v1.0 Build: 1027
PassMark (R) Software
www.passmark.com
Memmory summary for MAISON-PC:
Number of Memory Devices: 2 Total Physical Memory: 8173 MB (8192 MB)
Total Available Physical Memory: 6825 MB
Memory Load: 16%
Item | Module #1 | Module #2 |
-------------------------------------------------------------------------------|-----------------------|-----------------------|-
Ram Type | DDR3 | DDR3 |
Standard Name | DDR3-1333 | DDR3-1333 |
Module Name | PC3-10600 | PC3-10600 |
Memory Capacity (MB) | 4096 | 4096 |
Bus Clockspeed (Mhz) | 666.67 | 666.67 |
Jedec Manufacture Name | G Skill Intl | G Skill Intl |
Search Amazon.com | Search! | Search! |
SPD Revision | 1.0 | 1.0 |
Registered | No | No |
ECC | No | No |
DIMM Slot # | 1 | 3 |
Manufactured | Year 0 | Year 0 |
Module Part # | F3-10666CL9-4GBRL | F3-10666CL9-4GBRL |
Module Revision | 0x0 | 0x0 |
Module Serial # | 0x0 | 0x0 |
Module Manufacturing Location | 0 | 0 |
# of Row Addressing Bits | 15 | 15 |
# of Column Addressing Bits | 10 | 10 |
# of Banks | 8 | 8 |
# of Ranks | 2 | 2 |
Device Width in Bits | 8 | 8 |
Bus Width in Bits | 64 | 64 |
Module Voltage | 1.5V | 1.5V |
CAS Latencies Supported | 6 7 8 9 | 6 7 8 9 |
Timings @ Max Frequency | 9-9-9-24 | 9-9-9-24 |
Minimum Clock Cycle Time, tCK (ns) | 1.500 | 1.500 |
Minimum CAS Latency Time, tAA (ns) | 13.125 | 13.125 |
Minimum RAS to CAS Delay, tRCD (ns) | 13.125 | 13.125 |
Minimum Row Precharge Time, tRP (ns) | 13.125 | 13.125 |
Minimum Active to Precharge Time, tRAS (ns) | 36.000 | 36.000 |
Minimum Row Active to Row Active Delay, tRRD (ns) | 6.000 | 6.000 |
Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns) | 49.125 | 49.125 |
Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns) | 160.000 | 160.000 |
| | |
DDR3 Specific SPD Attributes | | |
Write Recovery Time, tWR (ns) | 15.000 | 15.000 |
Internal Write to Read Command Delay, tWTR (ns) | 7.500 | 7.500 |
Internal Read to Precharge Command Delay, tRTP (ns) | 7.500 | 7.500 |
Minimum Four Activate Window Delay, tFAW (ns) | 30.000 | 30.000 |
RZQ / 6 Supported | Yes | Yes |
RZQ / 7 Supported | Yes | Yes |
DLL-Off Mode Supported | Yes | Yes |
Maximum Operating Temperature (C) | 95 | 95 |
Refresh Rate at Extended Operating Temperature Range | 1X | 1X |
Auto-self Refresh Supported | Yes | Yes |
On-die Thermal Sensor Readout Supported | No | No |
Partial Array Self Refresh Supported | No | No |
Thermal Sensor Present | No | No |
Non-standard SDRAM Type | Standard Monolithic | Standard Monolithic |
Module Type | UDIMM | UDIMM |
Module Height (mm) | 30 | 30 |
Module Thickness (front), (mm) | 2 | 2 |
Module Thickness (back), (mm) | 2 | 2 |
Module Width (mm) | 133.5 | 133.5 |
Reference Raw Card Used | Raw Card B Rev. 0 | Raw Card B Rev. 0 |
DRAM Manufacture ID | 1229 | 1229 |
# of DRAM Rows | 0 | 0 |
# of Registers | 0 | 0 |
Register Manufacturer | | |
Register Type | | |
Register Revision | 0 | 0 |
====================================================================================================
Et des screen de CPUz...

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`0328ae70
Debug session time: Tue Jul 3 08:28:08.863 2012 (UTC + 2:00)
System Uptime: 0 days 0:03:19.800
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a01e864854, 0, fffff880012a2a35, 2}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveScb+bd )
Followup: MachineOwner
---------
4: kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a01e864854, 0, fffff880012a2a35, 2}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveScb+bd )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a01e864854, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880012a2a35, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------

READ_ADDRESS: fffff8a01e864854 Paged pool
FAULTING_IP:
Ntfs!NtfsRemoveScb+bd
fffff880`012a2a35 f7400400010200 test dword ptr [rax+4],20100h
MM_INTERNAL_CODE: 2
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d79996d
MODULE_NAME: Ntfs
FAULTING_MODULE: fffff88001210000 Ntfs
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88006e6e890 -- (.trap 0xfffff88006e6e890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a01e864850 rbx=0000000000000000 rcx=fffffa8009025780
rdx=fffff8a00e864980 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012a2a35 rsp=fffff88006e6ea20 rbp=fffffa80073dec00
r8=0000000000000000 r9=0000000000000000 r10=fffffa8009025780
r11=fffff88006e6eaf0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
Ntfs!NtfsRemoveScb+0xbd:
fffff880`012a2a35 f7400400010200 test dword ptr [rax+4],20100h ds:008c:4854=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000313c452 to fffff800030be040
STACK_TEXT:
fffff880`06e6e728 fffff800`0313c452 : 00000000`00000050 fffff8a0`1e864854 00000000`00000000 fffff880`06e6e890 : nt!KeBugCheckEx
fffff880`06e6e730 fffff800`030bc12e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`01220e8b : nt! ?? ::FNODOBFM::`string'+0x40940
fffff880`06e6e890 fffff880`012a2a35 : fffff8a0`0e864850 00000000`00000000 00000000`00000001 fffff880`012baf56 : nt!KiPageFault+0x16e
fffff880`06e6ea20 fffff880`01218a50 : fffff8a0`0e864880 fffff8a0`0e864980 fffffa80`073dec00 fffff880`012af4cf : Ntfs!NtfsRemoveScb+0xbd
fffff880`06e6ea60 fffff880`012a03ec : fffff8a0`0e864850 fffffa80`073dec60 fffff880`06e6eb98 fffffa80`09025780 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`06e6ea90 fffff880`012b7196 : fffffa80`09025780 fffff880`06745470 fffffa80`09025780 fffffa80`09025700 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`06e6eb10 fffff880`0122198d : fffffa80`09025780 fffffa80`073dec60 fffff880`06745470 fffffa80`08d43000 : Ntfs!NtfsCommonCreate+0x21ff
fffff880`06e6ecf0 fffff800`030b5ec7 : fffff880`067453e0 00700075`003c003e 00650074`00610064 0070006d`006f0043 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`06e6ed20 fffff800`030b5e81 : 00000000`00000000 fffffa80`08d43060 fffff880`06e6f000 fffff800`030cd88a : nt!KxSwitchKernelStackCallout+0x27
fffff880`067452b0 fffff800`030cd88a : fffffa80`073dec00 fffffa80`08d43060 00000000`00000000 fffff880`012af08d : nt!KiSwitchKernelStackContinue
fffff880`067452d0 fffff880`012218af : fffff880`01221970 fffff880`067453e0 fffff880`06745400 fffff880`012c040d : nt!KeExpandKernelStackAndCalloutEx+0x29a
fffff880`067453b0 fffff880`012bbaa0 : 00000000`00000000 00000000`00000000 fffff880`06745600 fffffa80`073dec60 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
fffff880`06745410 fffff880`0103d23f : fffffa80`07791030 fffffa80`073dec60 fffffa80`09a21100 fffffa80`076a3b60 : Ntfs!NtfsFsdCreate+0x1b0
fffff880`067455c0 fffff880`0105c2b9 : fffffa80`073dec60 fffffa80`06719800 fffffa80`073dec00 fffffa80`076a3b60 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`06745650 fffff800`033bb947 : 00000000`00000005 fffff800`033bb3a0 fffffa80`09c7e010 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`06745700 fffff800`033b2294 : fffffa80`07673940 00000000`00000000 fffffa80`09ca3740 00000000`00000701 : nt!IopParseDevice+0x5a7
fffff880`06745890 fffff800`033b6f8d : fffffa80`09ca3740 fffff880`067459f0 00000000`00000040 fffffa80`067039f0 : nt!ObpLookupObjectName+0x585
fffff880`06745990 fffff800`033bda57 : fffff880`030f9180 00000000`00000001 fffffa80`0a134301 fffff880`06745a58 : nt!ObOpenObjectByName+0x1cd
fffff880`06745a40 fffff800`033d6204 : 00000000`00baf7b0 fffff8a0`00000080 00000000`02b62290 00000000`00baf810 : nt!IopCreateFile+0x2b7
fffff880`06745ae0 fffff800`030bd293 : ffffffff`ffffffff fffffa80`089df280 00000000`00baf758 fffff880`00000004 : nt!NtOpenFile+0x58
fffff880`06745b70 00000000`7782f9ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00baf778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7782f9ea

STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsRemoveScb+bd
fffff880`012a2a35 f7400400010200 test dword ptr [rax+4],20100h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Ntfs!NtfsRemoveScb+bd
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x50_Ntfs!NtfsRemoveScb+bd
BUCKET_ID: X64_0x50_Ntfs!NtfsRemoveScb+bd
Followup: MachineOwner
---------

writhziden · 04 Jul 2012

We really need the full crash reports. Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with them so we may help you.

Also, for the CPU-Z screenshots, please include both SPD slots and not just one. It would also be nice if you included those screenshots in your crash report .zip file. :)

Night Hawk · 05 Jul 2012

The "ntoskmi.exe" problem is from errors on the main drive itself. For that alone scheduling a run of the Check Disk for the next startup will help clean up any disk errors. You can schedule that by right clicking on the drive's icon in Windows Explorer to bring up the properties screen>Tool tab and click on the Check Now button under error checking or open up a command prompt and type "chkdsk /r" and press enter.

When prompted for a yes or no press the Y key to see it scheduled to run before Windows starts loading on the next startup. The tool won't run while you are still booted in Windows since it works without Windows loaded and runs immediately following the post tests either when you restart the system or the next time you turn it on.

Faeken · 05 Jul 2012

I'm sorry I posted too fast and forgot some intructions.
I am far from this PC until this weekend but I'll send the missing items as soon as possible.
I told my father on site to conduct tests with the RAM until my return. He can do that

Night Hawk, you speak of "ntoskmi.exe" but it does not seem to have seen this information in my PC?

Some additional items: I have 3 HDD with a SDD for the system.
After several BSOD, some DLLs are found corrupt and planted some applications (Office or Magix video editing ...)
I crainds for my disk. I think the SSD, although new, has a problem?

writhziden · 05 Jul 2012

SSD Steps:

For the SSD:

Make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.
The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

System Information and Analysis:

We really have no idea if you are actually having issues with your hard disk, SSD, or just a Windows issue. We know very little about your system at the moment. If you need help, please fill in your system specs in your profile and not in a post in this thread: System Info - See Your System Specs.

Also, follow the https://www.sevenforums.com/crashes-d...tructions.html to help us help you.

Night Hawk · 05 Jul 2012

In addition to following the steps writhzedin has posted another thing that can be a help is editing your profile system specs to fill in some genera. system information. That is often needed for troubleshooting various problems.

Hopefully the references along with the steps to take will get you situated. :)

Faeken · 07 Jul 2012

Hi all,
I was able to generate the zip file as requested.
I hope it contains relevant information ...

For the SSD, I flash the firmware just before reinstalling Win 7
The BIOS of my motherboard was also updated and I was in AHCI
If you really think this is the SDS which is a problem, I also think a bit, I will install Win 7 again but on a hard drive.
I would just like to be certain that the problem comes right away

Thank you very much everyone for your valuable aid.

writhziden · 07 Jul 2012

Installing on a platter drive is a good troubleshooting step.

Have you tried the SSD power cycle first, though?

Faeken · 07 Jul 2012

Yes but nothing better, another BSOD appeared
I put the file. ZIP in my first post by editing

Night Hawk · 08 Jul 2012

Apparently SSDs can still be a little buggy at times! The dump file should however help isolate the main problem you are
running into the blue screen nightmare.