Blue Screens of Death

Nemean · 2008/06/27

Hey guys,

I went on google for information about BSoD, my computer is giving BSoD's everytime.

When I am using Firefox I get a BSoD, When I use Outlook etc etc..

I had the following BSoD's:

IRQL_Not_Less_Or_Equal

Driver_IRQL_Not_Less_Or_Equal

'Cause I had the driver error I updated every driver but that didn't worked out, I also did Memtest with out any result. I also removed my new Network Card from Linksys but the BSoD's still come back.

I also had these:

PFN_List_Corrupt

Bad_Pool_Header

Non_Paged_Area

My last BSoD was about 5 hours ago with the following message:

Volsnap.sys

Page_Fault_In_nonpaged_Area

Stop: 0x00000050 (0x8B433C46, 0x00000001, 0xF761EA95, 0x00000000)

Volsnap.sys - Adress F761EA95 Base at 7617000, Datestamp 480253bc

So what can this problem be?

Hopefully somebody can help me.

PeteC · 2008/06/27

Nemean - Welcome to the Board

My initial reaction is that you have a memory problem ....

From my 'standard' reference ....

http://aumha.org/a/stop.htm

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).
Click to expand...

0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues, but I haven’t been able to confirm this as a cause.)
Click to expand...

0x0000004E: PFN_LIST_CORRUPT
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.
Click to expand...

I also did Memtest with out any result
Click to expand...

Unfortunately not conclusive ....

Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
Click to expand...

The only way of checking memory successfully is to run with one stick only - switch between slots, testing in each position. Then repeat with sticks in pairs swapping them around the slots and testing. Tedious, but the only surefire way of determining if you have a flakey memory module or slot.

You might like to debug the dump files using our Dump Data Collection Tool and posting the logs here, noting ....

Unfortunately these logs require expert knowledge to analyze and there are only 2 members (who occasionally visit WindowsBBS.com) that have the depth of knowledge necessary. Other members can make observations and suggestions as to how you might proceed toward finding the cause ....
Click to expand...

Log in or Sign up

Blue Screens of Death

Nemean Inactive Thread Starter

PeteC SuperGeek Staff

Share This Page

Log in or Sign up

Blue Screens of Death

Nemean Inactive Thread Starter

PeteC SuperGeek Staff

Share This Page

Useful Searches