Constant Random BSOD (0x41790, 0xFFFFFA80051D6EC0, 0xFFFF, 0x0)

Toggle sidebar Toggle sidebar
C

Critical Mass

Honorable
Aug 22, 2012
10
0
10,510
Before I begin, let me mention that I will be away from home until Friday, so failure to respond on my part before then is NOT ignorance!

I have a custom built computer. The components were sold as a bundle from a popular computer website back in Feb '14, and I really have had no problems until a few months ago.

The most pressing problem (and possibly related to, and may solve the other problem) is seemingly random crashing with a BSOD. If there is anything in common between the occurrences, I can't figure it out. I think maybe it occurs more often when I have Microsoft Outlook open for my email.

I've downloaded WhoCrashed? and get this very vague message:

On Sun 8/30/2015 2:48:54 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 01:38:01
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80051D6EC0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I updated my video driver a few weeks ago, but had no improvement.

The other (but not primary) problem is a "Buzzing" coming from my tower. When I researched it months ago, it was suggested something could be overheating. I was told to download a utility called "Speedfan" which shows me temps and speeds of various spots inside my computer. The buzzing (and overheating) comes and goes at random as well, and sometimes happens even when my computer is idle. The BSOD problem happens independently of the buzzing.

My computer specs (according to WhoCrashed) are as follows

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: GA-78LMT-USB3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8570593280 total

Thank you in advance for your help.
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the sub error code was 0x41790 = page table page has been corrupted.

page tables are used to map virtual memory(pagefile.sys) to actual physical memory.

this can be a memory corruption caused by drivers, or by hardware problems.

since you have windows 7, your options are kind of limited.
run cmd.exe as an admin, run
sfc.exe /scannow
and confirm any corruptions are fixed.

I would also, go to control panel and turn off virtual memory and delete the pagefile.sys or rename it to pagefile.old and then create a new one by rebooting and turning the virtual memory back on.
http://windows.microsoft.com/en-us/windows/change-virtual-memory-size#1TC=windows-7

if you turn off virutal memory, windows will set aside some ram to page swap, then you can delete the file and reboot.

Since this problem can be caused by errors returned by the harddrive, or your sata hardware, or firmware in you drive. You should:
run crystaldiskinfo.exe and read the smart data from the drive to get an idea if your drive is failing,
update your motherboard SATA drivers, CPU chipset driver and BIOS.

confirm you memory system is ok, by running memtest86 after you update the BIOS or reset it to defaults.
-make sure you don't have overclocking drivers installed and running,

if every hardware test looks ok, then start cmd.exe as an admin
then run
verifier.exe /standard /all
and reboot
the system will bugcheck and name a bad driver in the memory dump file (if it finds a bad driver)
Note: use
verifier.exe /reset
to turn off verifier functions after you are done testing or your machine will run slowly until you do.

if you get a memory dump you can put the memory dump on a server and post a link.
or you might run whocrashed.exe or bluescreenview.exe and it might name the device driver for you.
(or it will name a windows component, which will not be very useful)





 
Upvote 0 Downvote
C

Critical Mass

Honorable
Aug 22, 2012
10
0
10,510
When I run sfc.exe/scannow, I get told that Windows Resource Protection found corrupt files but was unable to fix them, and I can find details in CBS.log but I have to figure out how to upload it to you. It's way too long to cut & paste.

I turned off virtual memory (all drives are 0MB) but if I try to delete or rename pagefile.sys it tells me the file is open in another program and I need to close it first. I rebooted, and while VM is still off, I get the same message. However, when I tried again last night, I was able to create a new one.

 
Upvote 0 Downvote
C

Critical Mass

Honorable
Aug 22, 2012
10
0
10,510
I left my computer running Saturday, Sunday, Monday with no problems.

Started this morning with a clean slate and it ran about a half hour before it crashed.

Isn't anyone able to help?

Of course, now I'll be leaving for a while again, and won't be back until next week. Hopefully by then I'll have a clue.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
The error code can happen when a driver frees up virtual memory, then frees up the same handle again. This causes the counter to under flow,(becomes ffff) This prevents the memory from being released. Turn on verifier and produce a kernel memory dump and send me a message and I will try to take another look in the debugger. Maybe I can a tag to find out which driver caused the problem.




 
Upvote 0 Downvote
C

Critical Mass

Honorable
Aug 22, 2012
10
0
10,510
The error code can happen when a driver frees up virtual memory, then frees up the same handle again. This causes the counter to under flow,(becomes ffff) This prevents the memory from being released. Turn on verifier and produce a kernel memory dump and send me a message and I will try to take another look in the debugger. Maybe I can a tag to find out which driver caused the problem.
Click to expand...

Thank you for the offer to help, but that's a little over my head. I have no idea how to do that.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom