Computer Error

[justinb138 0]

  Quote

Just waiting for the "Install Linux" response. So I'll throw it out there.

Install Linux Mint version 8. Visualize Windows for those critical windows programs or run those using wine!

You mean "Virtualize"?

[regulator 0]

Interesting. Do you know what was causing the issue? Perhaps a driver conflict or an incorrect registry key perhaps? If you still remember what caused the BSOD I'd like to hear the cause.

Thanks

Paul

[GogglesnTeeth 6]

  Quote

  Quote

Just waiting for the "Install Linux" response. So I'll throw it out there.

Install Linux Mint version 8. Visualize Windows for those critical windows programs or run those using wine!

You mean "Virtualize"?

Yeah, that's the word I was looking for....

Goggles and Teeth

"You fall like a greased safe!!!"

[pilotdave 0]

  Quote

The is no BSOD in Win 7. Any application that fails you will get a prompt stating what happened and the rest of your apps should be fine.

HA! Tell my windows 7 computer that. It's the least stable machine I have ever used. Not the fault of win7... I have some kind of hardware issue. Maybe bad memory but it passes every test. I get blue screens nearly daily. Apps crash allllllll the time. It's the most awful computer I have ever used even though it's the fastest and most powerful. That's what I get for building it myself.

I get MEMORY_MANAGEMENT and PFN_LIST_CORRUPT blue screens most of the time. Any ideas other than trying new memory? It's an intel i7-920 with 6 gigs of ram.

Dave

[shropshire 0]

  Quote

Interesting. Do you know what was causing the issue? Perhaps a driver conflict or an incorrect registry key perhaps? If you still remember what caused the BSOD I'd like to hear the cause.

Thanks

Paul

Most likely clue is the logo on the packaging

(.)Y(.)
Chivalry is not dead; it only sleeps for want of work to do. - Jerome K Jerome

[regulator 0]

Are you using a 64 bit Processor or 32 bit?

----------------------------------------------------------

You are running a quad core Intel processor. Got it.

[regulator 0]

Windows tracks physical pages of memory using a table called the Page Frame Database. This database (which actually is just a big one-dimensional array) is indexed by physical page number. As a result, the page frame database is typically referred to as the Page Frame Number list or PFN.

Every page of physical memory has an associated PFN entry. Each PFN entry contains information about the state of its corresponding physical page in the system. This state includes information about whether the corresponding physical page is in use, how it’s being used, a count of active users of the page, and a count of pending I/O operations on the page.

Depending on the pages state, a PFN entry may be on one of several lists that the Memory Manager maintains. The listheads for these lists are simple global variables that are used for quick access to PFN entries of certain types. For example, one such list would be the list that contains all the modified pages that need to be written to disk.

Because all the PFN lists and entries are present in the high half of kernel virtual address space, they are subject to corruption through stray pointer accesses (such as by errant drivers or other similar kernel-mode modules). Also, the count in the PFN that tracks the number of I/O related accesses to a given physical page can be corrupted by improper MDL handling.

Whenever Windows detects that any of the PFN lists or any of the PFN entries themselves have become invalid, the system halts with a PFN_LIST_CORRUPT bugcheck

-------------------------------------------------------------
How this is fixed varies depending on the reason of the bugcheck. Using Driver Verifier and the checked build of the O/S should allow you to pinpoint the driver that is either corrupting memory or mishandling MDLs. If the offending driver is not a driver that you have any control over, the only available option is disabling the driver until a fixed version is available.

[riddler 0]

  Quote

If you still remember what caused the BSOD I'd like to hear the cause.

I turned on the machine, it booted to Windows 7. I installed Windows Security Essentials (anti-virus). Then I installed Microsoft Office 2007 basic. No rocket science here.

In the middle of the Office install, it powered off, rebooted itself twice in a row, then recommended I fix the OS loader, which I did, and it said it couldn't fix it. Then I rebooted, and Office was clearly not installed (although there may have been existing registry files from the aborted attempt). So I made a second attempt to install Office, and BSOD!

The Microsoft marketing division may claim no more BSOD, but a kernel fault is a kernel fault, no matter the OS.

Trapped on the surface of a sphere. XKCD

[regulator 0]

Well that makes sense. Usually the times I've seen 7 crash and create the log report, it was a particular app crashing not an actual windows file that probably resided in the system folders. Basically anytime you encounter kernel, page and memory faults its a BSOD of some type. Were you able to resolve the issue. And if not, could you give me some details about the type of machine you were installing it on? It sounded like you were running a quad core so that is probably a desktop setup right?

[champu 1]

  Quote

The Microsoft marketing division may claim no more BSOD, but a kernel fault is a kernel fault, no matter the OS.

At least in windows they do you the courtesy giving you a clean crisp BSOD, as if despite the failure the programmer actually had some semblance of control over the situation.

A kernel that just throws up all over whatever you were doing comes with a tragic fall from blissful innocence, "You... you mean it doesn't just work?"