• Hey Guest!
    British Car Forum has been supporting enthusiasts for over 25 years by providing a great place to share our love for British cars. You can support our efforts by upgrading your membership for less than the dues of most car clubs. There are some perks with a member upgrade!
    **Upgrade Now**
    (PS: Upgraded members don't see this banner, nor will you see the Google ads that appear on the site.)
Tips
Tips

Bsod!

Share this page

NutmegCT

NutmegCT

Great Pumpkin
Bronze
Offline
OK you Windows gurus ... neighbor's Vista machine was running fine for two years until two months ago. Browsing (latest Chrome), all updates, runs 24/7 (not using sleep or hibernate).

Mouse will freeze on screen, hard drive stops spinning, BSOD appears within 30 seconds. Have to do a hard power off (hold in power button). Here's the first BSOD; note the "Kernel Data Inpage Error", and the codes.

View attachment 36323

Now here's the latest BSOD - same "Kernel Data Inpage Error", same base code, but different subsequent codes:

View attachment 36324

System has "frozen" about ten times in the last two months, but only these two instances of the BSOD. No new hardware added; I reinstalled Chrome two weeks ago. No other changes.

Any thoughts?

Thanks.
Tom
 
Tom, Last week my wifes Dell did the same thing. A deep scan found a lot of junk files, over 4000 and two of them were Trojans!! Cleaned the entire system and all is well now. Seems malware started the whole mess. On one of my old computers, which fortunately had a back up, I had to format the HD and reinsert windows to get rid of the virus. Now, I have three anti virus programs running. No more blue screen. PJ
 
Thanks gentlemen - I'll continue checking through those MS links.

I've run three different malware checks in safe mode, with no positives. Also ran a system overnight memory check, and a Windows memory check, with no results. I've also tried the fixes suggested here, with no improvement.

https://answers.microsoft.com/en-us...ror-code/03276fa2-6dcb-44d0-a778-499d5d00b65d

On this page - https://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx - you see

"The four parameters that are listed in the message can have three possible meanings. If the first parameter is 1 or 2, or 3 and the third parameter is 0, the parameters have the following definitions."

What the heck are "the four parameters"?. I don't see any "1 2 3 or 0 first parameters" on the two BSOD pages - just multi-character hex codes. And of course that page doesn't give an example of a parameter - just what the first digit might indicate.

I'm wondering if any BCF member has ever dealth with a BSOD with the STOP code "0x0000007a".

grumble grumble
PS - if you read the following MS q&a regarding this problem, you see why us end users tear their hair out (if they have any ...)

https://answers.microsoft.com/en-us...4-errors/13754b59-79a8-4e3b-a6ec-3874e9ae646b
 
I will say this, my desktop with Linux in it never seems to give me any of these problems. Seems like a lot of this stuff always comes down to a Microsoft thing. :rolleyes2: PJ
 
The error code of x'C0..0E' implies a hardware (probably disk) problem, or a driver problem. In my experience it has usually been a disk problem, intermittent at first and graduating to a situation where you can't boot the system. Once or twice it was caused by a driver update that I knew was risky and backed out.

One decent source of info is here. The specific text for your code (I think) is below. I can send you the Vista variant of the file they reference but I assure you it's useless to non Windowsmegageeks.


  • 0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration.
These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
A virus infection can also cause this bug check.
 
PAUL161 said:
I will say this, my desktop with Linux in it never seems to give me any of these problems. Seems like a lot of this stuff always comes down to a Microsoft thing. :rolleyes2: PJ
Click to expand...

Sorry to hijack the thread, but I moved from PC (Windows) to iMAC, with its UNIX-based OS, a few years ago. Best computer-related move in my life! Such crashes are a thing of the past, although I have run into an occasional instance of a program hanging, thus requiring a re-boot, but even those are rare. For the most part, this thing just works - and is much easier (to me anyway) to navigate and use. It took a while to get used to the differences, but once I did, there was no going back!
 
We have 3 laptops and a desktop. The laptops all have windows in them. I would change them over, but the wife uses them on occasion and she hates change! She won't even turn my desktop on because it's a Linux machine. Linux is twice as fast as windows and no worries about going haywire. I like it, but I try to keep a happy home. :highly_amused:
 
John - thanks for the tip on the 0xC000000E.

As that's just one of the several codes that show up, how does it relate to the actual STOP code shown?

In other words, why should I emphasize the meaning of that 0xC000000E as opposed to the STOP code and all the other codes?

Thanks.
Tom

 
If the first value (of the 4 in parens) is not a single digit, then the only "code" in the array is the second. The others are memory addresses. The 7A error indicates that Windows needed a page of memory that has been "paged out", or temporarily stored on disk. (This is memory that in the old days would be permanently stored in RAM - with virtual storage part of the hard drive is used to extend RAM). The info it needs is part of the Windows "kernel" - i.e. Windows itself. For some reason, it can't read the info it needs from disk into memory. Since it (the page) contains a piece of the kernel itself, Windows can't be sure of its own integrity and hits the panic button (aka bsod) rather than risk causing more damage.

My first step in your case would be a quick chkdsk and then (if errors are shown) a chkdsk with repair (/F/R, I think) - use chkdsk /? for the parms. To run chkdsk, use Start-Run, enter 'cmd' for a DOS window, and enter chkdsk. Vista will probably demand admin privileges.

This could also be some nasty rootkitish virus but I think more likely it's a fading disk.

I feel like I'm in work....
 
Thanks John. I had no idea about that "If the first value (of the 4 in parens) is not a single digit, then the only "code" in the array is the second. " Amazing to me that MS never explains that on the BSOD pages!

I've run the chkdsk with repair several times already - no errors found. Actually ran at reboot, before Windows even loaded.

Think I'll now check BIOS to see if there's something I've missed. Then do a System Restore and keep fingers crossed.

Frustrating!


 
dt150301.jpg
 
coldplugs said:
I feel like I'm in work....
Click to expand...

Got enuff coffee? :smirk:
 
Doc! Got any suggestions for my BSOD troubleshooting?

Thanks.
Tom
 
None that haven't been offered already. Is there some compelling reason you cannot replace the drive and do a reinstall (or use a backup/restore) of the O/S?

UBCD has some useful utilities, BTW. Clonezilla among them.

...and... Vista? It's headed for the M$ ashbin of history. Soon.
 
" Is there some compelling reason you cannot replace the drive and do a reinstall (or use a backup/restore) of the O/S? "

My ancient philosophy is to try to find the problem first, before using the BFH approach. As there's no evidence so far that the HD or O/S is the problem, I'd rather try to find specifics.

The "Restore to a Backup Point" idea sounds good. Will give that a try today. And I hear you on the Vista being outdated issue!

Thanks.
Tom
(To be honest, I've run into repair pro's who tell me they replace a HD and O/S pretty fast, as it saves them time - whether the drive had a problem or not! User's data and installed apps be dam*d. Relatively easy to save user files; not so easy to save the hundreds of new apps, updates, and drivers that had been installed.)



 
I thought I'd posted this earlier - if it's duplicated then my apologies.

A restore might do it but I'd be pleasantly surprised. It might revert to an earlier driver & update mix which could do it.

You could try messing with the paging area. Right-click "My Computer" and trundle to the Advanced Performance tabs. Making it a bit larger never hurt, and it may shift some pages around to different disk areas.
 
Thanks John. Never even thought of changing the paging file setup.

Might start with actually *removing* the paging file, then doing another chkdsk. Then restarting and creating a paging file of a larger size than before.

Sure wish the BSOD "diagnostic" codes were more clearly explained by MS, which I assume would allow me to do a better diagnosis.

Onward through the fog!
Tom
 
Back
Top