Virtual Memory

jcgriff2 · 17 Jan 2010

Hi -

Glad to hear that you were able to easily solve your BSOD.

Windows 7 & Vista systems by default set the crash dump settings to "Kernel Memory Dump" - which will produce a full kernel memory dump as well as a mini kernel dump.

Full Kernel Dump --> \windows\memory.dmp (overwritten by each BSOD)
Mini kernel Dumps --> \windows\minidump (new one created each BSOD)

Per kb254649 -

Kernel memory dump
A kernel memory dump records only the kernel memory... Depending on the RAM in your computer, you must have between 150MB and up to 2GB of pagefile space ... on the boot volume.

Small memory dump
... This option requires a paging file of at least 2 MB on the boot volume. . .

Full Kernel can be 250MB - 2GB or more; avg ~ 600MB
Mini Kernel = avg ~ 275kb Vista; Windows 7 ~ 325kb (I've seen some recently ~ 900kb)

The "allocated base size" (ABS) of the page file on the OS drive is another reason that no dump may be produced by a BSOD. The ABS = the size of the initial page file size allocation which usually occurs during OS installation. The ABS must be > installed physical RAM. If one were to upgrade RAM from 2 to 4 GB, the page file would increase in size for mapping physical and virtual memory addresses, but the initial allocation size would remain at the original size - just over 2GB if system managed. So, if upgrading RAM, it is important to delete the page file and allow the system to re-allocate it. It is very simple to do -

- turn the page file OFF; re-boot into SAFEMODE
- change file attributes for c:\pagefile.sys
- change file permission settings for c:\pagefile.sys (via takeown & icacls commands)
- delete c:\pagefile.sys - via "hard delete" - hold SHIFT key down when clicking "Delete" (it's too big for recycle bin) or use line command del
- re-boot
- turn page file ON - system managed
- re-boot

Check ABS and page file status/ location with the WMI script from my previous post.

"Recoveros/ page file" script --> WMIC_Recoveros_Pagefile_01-2010_jcgriff2_html_.bat.zip

I hope you continue to have a BSOD-free day !

Regards. . .

jcgriff2

.

Night Hawk · 17 Jan 2010

The only problem of not seeing a BSOD or forcing one by disabling the automatic restart when a program or something else causes a system crash is the error information that will be displayed. Generally that will pinpoint the actual problem once looked up.

In the 64bit Windows more data is placed in the active ram there with less swapping out to the paging file on the drive. That's why you only see the recommened in the screenshot earlier for only 1 1/2 times while the 32bit Windows on the other hand relies more heavily on the paging file to suppliment the physical with the virtual memory there.

As for addon devices like tv tuner cards, devices like those can be notorious for blue screens depending on type.

One tip is if the software requires that software version's tuner driver be installed as part of the process and you have the latest or last here for the model don't check off the latest in the optional updates since that will knock things out. For Media Center where only the driver is used that shouldn't become a problem since only the driver is being downloaded and installed.

Now for upgrading 4gb to 8gb that will be seen on a new build being planned to start off with 8gb there. The "automatically manage paging file size for all drives..." option there helps as well as having the paging file on the same drive when you have more then one OS drive to consider. BSODs are actually rather rare here even when working with a few older programs that simply love crashing!

jcgriff2 · 27 Jan 2010

You are right - TV tuners do tend to wreak havoc. Good point on memory utilization - SuperFetch at its finest.

BSODs are a rare event? Well, if you are someday bored or find yourself in need of additional kernel dumps for a late night party, you can crash your system - Blue Screen and all - with a registry change and pressing a few keys -

Windows feature lets you generate a memory dump file by using the keyboard

Forcing a System Crash from the Keyboard

However, the result is always the same - bugcheck 0xe2 - self inflicted crash, i8042prt.sys

Regards. . .

jcgriff2

.

Night Hawk · 27 Jan 2010

I here quite a few people running into problems with Haugpauge tuner cards with the previous versions of Windows. Pinnacle was XP only seeing not even Vista support for their line.

That's another item for people to contend with as far as that addon type.

When people are afraid they can't run the 64bit Windows on a machine seeing 2gb of ram or why less is seen available in the perfomance monitor they often don't realize why. The utilization of the active ram is simply a more effectient data management process seen with the 64bit kernel there.

Intentional system crash? Gee I'll just load up some old outdated stuff here and watch those crash!

In fact I ran into just today looking a Flip3D tweak for someone running a Vista laptop.

This runs on both Vista and 7 but has one annoying problem. If you check off the mouse option it takes full control of the mouse meaning you can't even close a window out! Best leaving that to one corner of the screen! The Windows Vista Flip 3D Activator

The real working solution? Switch Between Windows - Flip 3D Shortcut[2]=Shortcuts

Actually when compared to that example of what works consider where BSODs are most often seen? Surprizingly the 32bit Windows! With less swapping out to the drive there's less chance of data corruption seen with the 64bit Windows.

At least 7 has seen some improvements in both flavors with fewer even reporting any then seen with previous versions even after this amount of time. I guess I may need to use one of those links there just to see one here!