Solved Need Help / Blue Screen ntoskrln.exe & Stop: x000109

[Serious Gamer]

Hi Guys , i have problem with the blue screen , i have to Restart my computer every time , i am not gonna talk to mutch this is pics :

.

i had this problem before , and after i upload last drivers , BSOD Solved but , like u see i get it again with problem of ntoskrln.exe , like u know i have another PC that have the same system as this computer so i copied the file "ntoskrln.exe" paste it in this computer , but it didn't work , i tried everything "sfc /scannow" , "chkdsk /r" & system restore nothing , i really hope to give a solution , bcoz this problem is get me angry , and sorry for my bad language thanks in advance !!​

​

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Serious Gamer]

this is the SF Diagnostic Tool !

 

[Arc]

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_____________________________________________________________
BSOD ANALYSIS:

...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d898d69808, b3b7465eeb54d5ca, fffff80000b96bb0, 6}

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt_fffff80000b95000+1bb0 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d898d69808, Reserved
Arg2: b3b7465eeb54d5ca, Reserved
Arg3: fffff80000b96bb0, Failure type dependent information
Arg4: 0000000000000006, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:
------------------


FAULTING_IP: 
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03b78498 00000000`00000000 : 00000000`00000109 a3a039d8`98d69808 b3b7465e`eb54d5ca fffff800`00b96bb0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_NAME:  nt_fffff80000b95000+1bb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt_fffff80000b95000

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5149a99c

FAILURE_BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0

BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0

Followup: MachineOwner
---------

 

[Serious Gamer]

what do u mean by ; u didn't find any dump crash , is there anything i miss when doing the test ??
and i'll start testing my ram

 

[Arc]

You have done it right.

Now do the memtest. Depending on the result decide to go for Driver verifier. Let us know the results.

 

[Serious Gamer]

Boot error for usb ? , What's the problem . .??

 

[Arc]

May be you failed to make a bootable USB.

Try a bootable CD ... easier option.

 

[Serious Gamer]

CAN U give the direct link for the usb disk , maybe i didn't download the right one thanks !

 

[Serious Gamer]

i tested by : Control Panel -> System & Security -> Administrative tools -> Windows Memory Diagnostic ..
and i didn't find ant errors , plzz help !!

 

[Serious Gamer]

i burned it in cd and ,i started the scan , what now ??

 

[Arc]

Now let is run for at least 8 passes. After 8 passes is complete, take a camera snap of the computer's full screen .... upload the image here following http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html .

 

[Serious Gamer]

this me for my other machine , this is 9 passes almost 10 , i hope u give me a solution thanks !!

 

[Serious Gamer]

can i stop the scan ??

 

[Arc]

As I suggested, stop it after 8 passes.

Now enable Driver verifier as suggested. Make it sure that you are not selecting any driver provided by "microsoft" or "unknown". After a restart, DV is supposed to cause BSOD. Let it BSOD a couple of times. Then post it following th BSOD posting information.

 

[Serious Gamer]

ok , but is there any chance that i can't enter in my desktop after doing that , bcoz the Safe Mode also is not working Stop:0x000007B ??

 

[Serious Gamer]

Can u tell me is there anything to worry about it ,are my Hardware Fine ?? , i mean Rams and Processor or whatever shown in the picture 9 passes ??

 

[x BlueRobot]

Stop 0x7B:

Usual causes:  Hard drive, File system, Boot sequence errors, Device driver, Virus infection (in particular check the MBR)

Stop 0x7B is usually related to a failing hard drive, but can be due to drivers. Could you please upload the dump file?

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an 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.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[Serious Gamer]

Could you please upload the dump file?
Do u mean this files ?? C:\Windows\Minidump

 

[x BlueRobot]

Yes I do, thanks. The files inside that folder.