Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Ntoskrnl.exe BSOD after new Windows 7 install

01 Jan 2015   #11
carz95

Windows 7 Home Premium 64-Bit
 
 

Hello,

Today I got another BSOD. It happened when I left my computer on for a half hour.
I then came back to it, tried to log in, my computer froze and the Blue Screen occurred. I have
attached the dmp file in a .zip.

(Hopefully more info can clear things up)?

Thanks


My System SpecsSystem Spec
.
01 Jan 2015   #12
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Code:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800912e560, Terminating object
Arg3: fffffa800912e840, Process image file name
Arg4: fffff80002f8a270, Explanatory message (ascii)
Debugging Details:
------------------
----- ETW minidump data unavailable-----
PROCESS_OBJECT: fffffa800912e560
IMAGE_NAME:  wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000 
PROCESS_NAME:  wininit.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
An I/O error is a hard drive error. Almost every dump you have had indicates a hard drive error.

These are not what is blamed, I just wanted to show you what is going on during the crash.

Code:
fffff880`08adb2a8  fffff880`045ecb7d dump_msahci!ActivateQueue+0x1fd
fffff880`08adb2b0  00000000`0000000c
fffff880`08adb2b8  fffffa80`09188728
fffff880`08adb2c0  00000000`dd17e000
fffff880`08adb2c8  fffff880`045ecb7d dump_msahci!ActivateQueue+0x1fd
fffff880`08adb2d0  00000000`00000000
fffff880`08adb2d8  fffff880`045ef739 dump_msahci!AhciCompleteRequest+0x99
fffff880`08adb2e0  00000000`00000009
fffff880`08adb2e8  fffff880`045ec9e5 dump_msahci!ActivateQueue+0x65
fffff880`08adb2f0  fffffa80`091885a8
fffff880`08adb2f8  fffff880`045ec907 dump_msahci!AhciHwStartIo+0x59b
fffff880`08adb300  fffffa80`09188728
fffff880`08adb308  fffff800`03204280 hal!HalpTscStallExecutionProcessor+0x7c
fffff880`08adb310  00000000`00000001
fffff880`08adb318  00000000`00000000
fffff880`08adb320  fffffa80`09188278
fffff880`08adb328  fffff880`05ded401 dump_dumpata!IdeDumpFreeScatterGatherList+0x9d
fffff880`08adb330  fffff880`08adb598
fffff880`08adb338  fffff880`045ecbd7 dump_msahci!AhciHwInterrupt+0x3b
fffff880`08adb340  fffffa80`091881c0
fffff880`08adb348  fffff880`05dec82b dump_dumpata!DispatchCrb+0x163
fffff880`08adb350  ffff0087`ada261f2
fffff880`08adb358  00000000`00000000
fffff880`08adb360  fffffa80`091881c0
fffff880`08adb368  fffff800`03203a7b hal!KeStallExecutionProcessor+0x183
fffff880`08adb370  00000000`0000000a
fffff880`08adb378  00000000`000003de
fffff880`08adb380  fffff880`08adb470
fffff880`08adb388  fffffa80`091881c0
fffff880`08adb390  fffffa80`091881c0
fffff880`08adb398  fffff880`05ded49d dump_dumpata!IdeDumpWaitOnRequest+0x49
fffff880`08adb3a0  00000000`00000000
fffff880`08adb3a8  00000000`00000000
fffff880`08adb3b0  00000000`00000000
fffff880`08adb3b8  fffff880`05ddff7a crashdmp!FilterCallback+0xae
fffff880`08adb3c0  00000000`00000000
fffff880`08adb3c8  fffff880`05dec4e6 dump_dumpata!IdeDumpWritePending+0xee
That is just one small part of the dump file
My System SpecsSystem Spec
01 Jan 2015   #13
carz95

Windows 7 Home Premium 64-Bit
 
 

Ok, thanks!

So if it's safe to assume it is the hard drive, what would be the next step?

Also, when I ran the tests you recommended on it - nothing came up - was I doing something wrong?
My System SpecsSystem Spec
.

01 Jan 2015   #14
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Did you rub Seatools for DOS, the short and long tests? SeaTools for DOS and Windows - How to Use

You also need to run it on all your hard drives. Sometimes the errors are from a secondary drive. All I know is all the dumps seem to be pointing to a hard drive or file system structure.
My System SpecsSystem Spec
11 Jan 2015   #15
carz95

Windows 7 Home Premium 64-Bit
 
 

Hello, just a quick update.

For a week no bsods have occurred, and I am still in the progress of testing my hdd.

However, I have had 3 recently. I have uploaded a dmp file. Hopefully these can shed
some light on the situation.

Thank you
My System SpecsSystem Spec
11 Jan 2015   #16
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Have you changed your virtual memory size? This is Vista Forums but is the same for Windows 7. See what yours is. Virtual Memory Paging File - Change
My System SpecsSystem Spec
11 Jan 2015   #17
carz95

Windows 7 Home Premium 64-Bit
 
 

I don't think I changed it..here is what came up in Virtual Memory
My System SpecsSystem Spec
11 Jan 2015   #18
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

OK, just curious.
My System SpecsSystem Spec
17 Jan 2015   #19
carz95

Windows 7 Home Premium 64-Bit
 
 

Hello

I ran SeaTools for DOS on my HDD (I only have one)
Short test and long test - both passed.

However, I have had two more BSODs recently. One while starting up my PC, and one just out of
the blue after I had logged in (different days of course)

Anything in these that still points to the hard drive? Or could it be my disk drive (where I put
CDs, etc)?

Thank You
My System SpecsSystem Spec
17 Jan 2015   #20
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

One of the dump files was pretty much exactly the same as all the others I have seen. stop code F4 all with references to NTFS and I/O

The other one was a standard 116 which is a typical graphics driver/card error

Code:
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800a0234e0, fffff8800508623c, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7a223c )
Followup: MachineOwner

Which is your Nvidia Graphics driver
Code:
nvlddmkm
start             end                 module name
fffff880`048e4000 fffff880`05304000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 13 00:53:17 2014 (548BE25D)
    CheckSum:         009E7B4F
    ImageSize:        00A20000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
Reply

 Ntoskrnl.exe BSOD after new Windows 7 install




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD, Windows 7 New Install - WinDbg says ntoskrnl.exe
Hi, I have had a BSOD twice now over the last 2 days. Both times analysis of minidump file says that probable cause is ntoskrnl.exe. I have run your diagnostic tool and have attached the output. Any help here would be much appreciated. I am sure the attached files give you the...
BSOD Help and Support
UNEXPECTED_KERNAL_MODE_TRAP BSOD (ntoskrnl.exe) (New Install)
So yeah, I was getting BSOD's with Windows 8 (Which only started in the last 2 months) so It thought it might just be a compatibility error but apparently not. I freshly installed windows 7, 2 days ago and it's still going for it. I can't even boot normally anymore it just instantly BSODS when I...
BSOD Help and Support
BSOD ntoskrnl.exe fresh windows 7 install
Hey guys, I have been having a problem with blue screens on this computer for a few weeks now. I finally got frustrated with it yesterday and reinstalled windows 7. The issues would happen any time I ran windows update. To fix it, I would have to restore to the oldest possible point, run the...
BSOD Help and Support
BSOD: ntoskrnl.exe; clean install corruption?
So I received a solid state drive for Christmas last year and haven't had any luck with installing it. I'm doing everything I can to rule out that it was DOA considering that at this point it's probably past warranty and I don't really wanna drop the money on a new one. Following a clean install...
BSOD Help and Support
BSOD after fresh install, ntoskrnl.exe
I really need help here guys, im out of ideas. About a week ago my computer started getting BSOD randomly while gaming or browsing the web. I thought it was a failing HDD so I re installed windows onto a new one after running stress tests on it to make sure it was good. I have run stress tests...
BSOD Help and Support
BSOD - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install
I got BSOD while I was watching a movie on Netflix and playing World of Warcraft. I was setting up my settings for Media Monkey and got this blue screen of death. I recently did a fresh install on my computer no more than a week ago. I am running Windows 7 Enterprise 64 Bit with Service Pack 1. I...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:55.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App