Windows 7: bsod, after long period of powered on

marosell · 17 Aug 2010

Never noticed a problem until recently (last five days or so), when I've been keeping my pc booted for a longer period of time (more than 24 hours). Every time I come back, I have some kind of BSOD, either Page_fault_in_nonpaged_area, or memory_management.

The only thing I've done to it in the past two weeks is run Windows Update (which I had been putting off for a little while, seemed like mostly security updates though).

- x86 (32-bit) or x64 ?
- OEM
- Asus motherboard
- hardware is 2-3 years old
- install is since release

Thanks!

Jonathan_King · 17 Aug 2010

Welcome to SF!

First thing you need to do is memorize your unique Customer Identification Number (CIN), and Thread Identification Number (TIN)

CIN: 101255
TIN: 105037

Just kidding.

First thing, install the latest ATK0110 Utility for XP/Vista/7 from here: ASUSTeK Computer Inc.-Support-

Search for your motherboard model, M2N32. The full model of your mobo is M2N32 SLI Deluxe.

Also, install these latest nForce drivers: NVIDIA DRIVERS 15.53 WHQL

I'm hoping that works, because I'm having trouble finding drivers for your Silicon Image hard drive controller!

If that doesn't work, enable driver verifier: Driver Verifier - Enable and Disable

Then upload the new dumps files. We no longer need the full jcgriff2 report, only the dumps, from now on in this thread.

http://www.sevenforums.com/tutorials...en-forums.html

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 00:23:46.069 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:06.864
BugCheck C0000221, {fffff8a0001d78a0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
BUGCHECK_STR:  0xc0000221
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 15 09:23:52.128 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.923
BugCheck C0000221, {fffff8a000240530, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
BUGCHECK_STR:  0xc0000221
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 14:17:42.510 2009 (UTC - 4:00)
System Uptime: 0 days 0:02:48.305
BugCheck 24, {1904fb, fffff88006e1e628, fffff88006e1de80, fffff88001321562}
Probably caused by : Ntfs.sys ( Ntfs!AddToIndex+e2 )
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 14:13:50.557 2009 (UTC - 4:00)
System Uptime: 8 days 3:58:55.758
BugCheck 1E, {ffffffffc0000005, fffff80002bd825c, 0, 13}
Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+118 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

marosell · 18 Aug 2010

So I did those things last night. Seemed to install them just fine.

Today I had another BSOD, Memory_Management. But when I restarted, I had the option to go into "recovery mode" or something like that. Windows wanted to try to fix the problem itself, so I said sure.

It pulled an old restore point, and I don't know what else it did while I was gone (I had to leave) but when I came back it was ready for me to login.

When I logged in, my wireless network adapter was having issues connecting to my router. So I rebooted, and now I seem to be connected.

Don't know how long until the next BSOD, but I can keep it running over night and see what happens in the morning. What can I upload for you take another look, another dump?

Thanks, and any ideas you may have are appreciated.

marosell · 19 Aug 2010

Had a blue screen this morning. Computer won't boot now, it just keeps going into "Startup Repair mode" and tries to fix itself, with the dialog box coming up saying it was unable to fix anything.

But it gives a list of tests it did. It came up with a "Registry Corrupt" message. How do I try to fix this?

Thanks.

Tews · 19 Aug 2010

Insert your Windows 7 DVD and choose the repair option... if this doesn't resolve your problem, you may have to do a clean install...

marosell · 22 Aug 2010

I couldn't fix the problem, so I just reinstalled Windows 7. It's been fine for two days (or at least I thought) but today I had another BSOD. Attached is my dmp.

Jonathan_King · 22 Aug 2010

Install these drivers again: NVIDIA DRIVERS 15.53 WHQL

Test hard drive: HD Diagnostic

What is your computer model/OEM?

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 19 03:55:58.318 2010 (GMT-4)
System Uptime: 0 days 0:00:07.113
BugCheck C0000221, {fffff8a00013c340, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
BUGCHECK_STR:  0xc0000221
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 16:25:02.621 2010 (GMT-4)
System Uptime: 1 days 16:28:51.000
BugCheck 50, {fffffaf45200001b, 0, fffff800028df53b, 5}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

marosell · 22 Aug 2010

Home-built pc, ASUS m2n32-sli deluxe mobo.

I'm running memtest86 right now; if no errors come up, ill install those on the next reboot.

I had issues with sticks of memory about a year ago and sent them all back to crucial for new ones. They're ballistix, (4) 1gb sticks. I may have to send them back again, maybe their stuff is only good for a year? Sigh.

marosell · 23 Aug 2010

I installed those NVIDIA 15.53 drivers last night. When I get home, if I don't have a BSOD yet, that may have been the problem.

I installed Seatools for my Maxtor HDD. I assume it's supposed to detect my HDD when the program launches, as the first view of the program shows detected hdds. Mine isn't detected/shown, so I can't run the diagnostic.

Leads me to believe I may have an issue with the HDD driver? Never installed one before, always thought the OS was supposed to handle that. The asus website doesn't have any listed for Windows 7-64 bit, but I can try to install the one they have listed for vista-64bit when I get back home and see what happens.

Thoughts?

Jonathan_King · 23 Aug 2010

It could be SeaTools, designed for Seagate drives, is not liking your Maxtor drive.

Try this Maxtor diagnostic: http://www.tacktech.com/download.cfm...or/PwrMxEn.exe

Windows 7: bsod, after long period of powered on

bsod, after long period of powered on problems?