Next Generation Emulation banner
1 - 13 of 13 Posts

·
Premium Member
Joined
·
5,934 Posts
Discussion Starter · #1 ·
I am having a weird issue where my install of Windows 7 will blue screen at random. I can reproduce the problem every time by doing the following:

1. Boot up PC

2. Let Windows load to the log in screen

3. Let Windows idle on the log in screen for a few minutes.

4. Attempt to log in.

5. Upon attempting to log in after letting Windows idle on the login screen for a few minutes I am presented with a BSOD.

The error is related to NTFS.sys an is something along the lines of PAGED_TO_NON_PAGED_AREA.

It only happens if I let Windows idle on the log in screen for a few minutes, I don't get a BSOD if I log in right away.

Also Windows will blue screen at random when my PC is idle, never when I am actively using it.

Here is a minidump, hopefully it will be of use to pinpoint where the problem is:
 

·
Banned
Joined
·
23,263 Posts
Faulty Memory.

There is no other cause for NTFS crashes.
 

·
Banned
Joined
·
23,263 Posts
It might simply require a +.01v increase,
 

·
Premium Member
Joined
·
5,934 Posts
Discussion Starter · #5 ·
Can anyone analyze the dump file to see if any programs or drivers may be at fault? Did one of the drivers or programs crash in the event of the blue screen?

It says that drivers or applications could also be the fault of the blue screen, or if the requested data is not in memory. I never had this problem with Vista and suspect it could be a faulty application or driver causing my troubles.
 

·
Banned
Joined
·
23,263 Posts
NTFS.sys IS the driver :p and when core drivers crash (on an os this stable) it can only be hardware, or a tampered disk. (you verified the disk before installing right?)
 

·
Premium Member
Joined
·
5,934 Posts
Discussion Starter · #7 ·
Squall I reinstalled Windows 7 and am no longer having this problem, the ram or HDD definitely wasn't the problem. If it was I would be having the same problem on even a fresh install.

It had to be a bad driver, rogue/bad application that was causing it or something corrupted in my Windows installation. This is why I needed that minidump file analyzed, now I have to fight with reinstalling tens or hundreds of applications and games.
 

·
Registered
Joined
·
1,620 Posts
it still can be the ram because all the reinstall did made the os use another area of your ram and hence its not recieveing the error yet... if it were me id run memtest, just in case, to see if it can be a bad area in your ram
 

·
Banned
Joined
·
23,263 Posts
Yeah. you have to consider, why the previous install was corrupted.
 

·
Rpcs3 user :D
Joined
·
780 Posts
It's easy, just make a test of your RAM using W7 or Memtest and you'll figure out if your RAM is corrupted or something like that :)
 

·
Premium Member
Joined
·
5,934 Posts
Discussion Starter · #11 ·
Well the reason why I say my previous install was corrupted is because I used CCleaner to delete registry entries.

I also compressed my main drive Windows is installed on, compression messed up because I terminated the process early. I then had to uncheck the box in drive options to decompress what files were compressed and run the compression process over again.

I also deleted some files/directories I thought were not needed, but probably were. I also had over a hundred games and applications installed. I modified the environment variables for Tortoise SVN and VS2008. I also used a guide to get Windows 7 to boot a bit faster which I found useless in the end because it made no difference in boot time and my Windows 7 install already booted quite fast.
 

·
Premium Member
Joined
·
5,934 Posts
Discussion Starter · #12 · (Edited)
I think I had a stick of ram in incorrectly..

I noticed my system was a quite sluggish, slower, unusually unstable, and the display driver was crashing constantly. I opened the case, took the video card out, cleaned the dust, readjusted and checked the ram sticks.

Also checked the cords for my SATA drives, which might of been loose. I checked other connections and adjusted them. I hooked up my PC speaker to the motherboard so it makes a beep upon bootup and I can tell what problem there is if any.

I also switched one of my fans around to blow air out of the case, I had one of my fans blowing air inside the case which was also bringing in dust..

After cleaning out the dust and putting everything together, I sealed off one of the card slots to prevent as much dust getting inside the case as I could.

I also reset the bios back to the defaults and adjusted only the necessary options.

My PC then posted without a problem, has been running stable, smoothly, and fast ever since then.
 

·
From Love and Limerence
Joined
·
6,574 Posts
In case it helps, if you were by any chance overclocking (or even tweaking voltages at stock frequency) and using a BIOS feature akin to Loadline Calibration of any sorts to do so, this can happen. The PC will be fine under any sort of load, but when idle, it can be more prone to crashes and BSODs. It confuses people since they assume this couldn't be one of many possible causes since they'll see it's fine under load, so it must be during anything less too.
 
1 - 13 of 13 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top