Sign in with
Sign up | Sign in
Your question

BSOD help, running out of ideas.

Last response: in Windows 7
Share
January 12, 2012 12:10:02 AM

So, I've recently built a new computer oriented towards gaming. Putting it together went well, on start-up it worked amazing. After updating my drivers and getting the software all running I started using it for games. For almost a month straight I had no errors what-so-ever. Then one day I ran Skyrim for a total of six hours, still no errors. After coming home that night I turn on the computer, run skyrim, play for twenty or so minutes, and I get greeted with a BSOD.

I restart the computer and instantly start tracking down the error message, but after about two minutes or so of browsing the internet it would blue screen. This happened multiple times, and eventually I got tired and went to bed. The next day i swapped the RAM around and started trouble shooting again. No blue screens while searching the web made me scratch my head. So to test I started Skyrim again and played for another twenty minutes until I blue screened. This happened multiple times while playing, and happened pretty spontaneously.

Recently I tried doing a clean driver install of my graphic drivers, hoping that would fix it. Playing League of Legends for almost three hours with no blue screen. However, I haven't tried testing League before to see if it would cause a BSOD. My initial thought was that maybe because Skyrim is more graphically intensive that it was causing the BSOD. So today was my testing day. I played Skyrim for a little bit, with no BSOD. Played League for a couple hours, and still no BSOD.

Then I played one last match and the BSOD happened. This one looked a tad different and unfortunately I couldn't fully read it before it was dumped. But it said something about the System32 file, I believe, but BlueScreenViewer says nothing about that.

So before I post the info I wanted to throw out that I have tried FileVerifier and it turned up nothing. I've done the clean driver install, and I've changed the RAM around. I have not tried MemTest yet, and would be willing to try it, but I just wanted some feedback just in case I'm missing a glaring problem.

I'm using a P8P67 Pro ASUS motherboard, i5 2500, Nvidia 560 GTX, and 2 sticks of Corsair 4 gig 1600Mhz RAM.

If you need more info, or the actual dump filed, let me know. This is the BlueScreenView info though:

011112-17425-01.dmp 1/11/2012 5:39:41 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff901`c01feb40 00000000`00000000 fffff960`0015b06e 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\011112-17425-01.dmp 4 15 7601 333,768


010812-15927-01.dmp 1/8/2012 6:43:51 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff683`ff7e29f0 3e700000`c952f025 fffffa80`06abb8b0 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\010812-15927-01.dmp 4 15 7601 293,152


010612-21777-01.dmp 1/6/2012 2:52:10 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff680`0202a1e0 00000000`00000000 fffff800`030bd27b 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\010612-21777-01.dmp 4 15 7601 293,136


010612-16504-01.dmp 1/6/2012 12:24:41 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`0dbfa03b 00000000`00000000 fffff800`030b24cf 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\010612-16504-01.dmp 4 15 7601 293,168


010412-19827-01.dmp 1/4/2012 11:04:22 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff680`00027638 bf500005`77ea8867 fffffa80`0c08b310 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\010412-19827-01.dmp 4 15 7601 286,400


010412-19390-01.dmp 1/4/2012 10:57:44 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`fffffffc 00000000`00000000 fffff800`032de282 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\010412-19390-01.dmp 4 15 7601 285,712


010412-15818-01.dmp 1/4/2012 10:53:28 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff820`0210b518 00000000`00000001 fffff880`0f401986 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\010412-15818-01.dmp 4 15 7601 293,168


121611-20170-01.dmp 12/16/2011 12:49:25 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`19808a7b 00000000`00000000 fffff800`030b15d5 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\121611-20170-01.dmp 4 15 7601 293,152

Thanks to anyone in advance for reading this long winded post and having the patience to help. I do appreciate it.

More about : bsod running ideas

a b $ Windows 7
January 12, 2012 3:26:16 AM

This topic has been moved from the section Opinions and Experiences to section Windows 7 by Pyree
a b $ Windows 7
January 12, 2012 3:33:24 AM

Hmmm interesting, I can't quite remember what the "PAGE_FAULT_IN_NONPAGED_AREA" But going off my fuzzy memory i think it has something to do with the ram, Are your timings set correctly and have you tried running memtest or windows memory diagnostic, also what are your temps like under 100% load

Using Furmark for the GPU and, prime95 for the cpu, or intel burn test...

run these for atleast 15 minutes, also run memory diagnostics or memtest for atleast 3 passes.
Related resources
a b $ Windows 7
January 12, 2012 3:45:13 AM

Check the BIOS as well... Does it report the correct settings for the RAM as well as the other installed hardware?

It could be incorrect and then you'll get errors when stressed, ie Skyrim...

Look at the spec's for the RAM on the mfg's website
a b $ Windows 7
January 12, 2012 11:07:42 AM

PAGE_FAULT_IN_NONPAGED_AREA: Memory related BSOD
MEMORY_MANAGEMENT: Memory realted BSOD

Run memtest86 for a few runs and report back; looks like you have a bad stick of RAM.
January 12, 2012 11:20:47 AM

Are you using beta drivers for graphics? that might cause prob.....alsodid you install custom mouse drivers? .....maybe bump up cpu volts a tad
January 12, 2012 11:30:29 AM

mouse24 said:
Hmmm interesting, I can't quite remember what the "PAGE_FAULT_IN_NONPAGED_AREA" But going off my fuzzy memory i think it has something to do with the ram, Are your timings set correctly and have you tried running memtest or windows memory diagnostic, also what are your temps like under 100% load

Using Furmark for the GPU and, prime95 for the cpu, or intel burn test...

run these for atleast 15 minutes, also run memory diagnostics or memtest for atleast 3 passes.



Explanation:

This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.

http://technet.microsoft.com/en-us/library/cc957625.asp...

There is user action in the link =D
a b $ Windows 7
January 12, 2012 5:48:19 PM

^^ Essentially, the pointer to the location on the HD where the data is located is defective, which by itself leads me to suspect RAM. Combine that with a MEMORY_MANAGMENT BSOD, and you very likely have a defective stick of RAM.
January 13, 2012 2:46:29 AM

Wow, one day and already a ton of responses! Thanks a ton for everyone's ideas. Running a couple of suggested test tonight and will report back tomorrow when finished. Multiple things I wanted to add that could be totally irrelevant but couple potentially help as well:

FireFox randomly crashes sometimes, and gives me an error box (asking me to send problem etc.). When trying to reopen firefox I keep getting the same error box with no other result from fire fox. Which is pretty annoying in itself. I think it could be a problem with Adobe because sometimes League will get a Adobe Air Debug Launcher message and will not let me start as well. Restarting the computer solves this issue's, and they happen pretty infrequently that I haven't put much thought into them.

Additionally, another spontaneous occurrence is that my monitor will temporarily lose detection of the graphics card, and act like its not plugged in. Nothing I can do fixes it, but it will come back to life within 30 seconds of doing that. When it comes back I get a small error message from windows saying that there was a problem with my visual display.

Now I haven't noticed if any of these happen in a specific order before a BSOD, or if they have any relevance at all to this problem, but I figured I'd add them to the mix, to see if that triggers anyone's brain.

Anyway, I'll definitely run the tests now and post what I come up with. Thanks again!

EDIT: another quick clarification, I'm definitely not running any Beta drivers.

EDIT #2: Ran Prime65 twice to be sure, and was welcomed with an error twice.

[Thu Jan 12 21:06:11 2012]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Reading up on it points to RAM some more, and I did indeed check on my timings and voltage. Both are set to a recommended 9-9-9-24 and 1.5v. I've done no overclocking on this machine. I'll run MemTest over night and return with results.
a b $ Windows 7
January 13, 2012 11:28:06 AM

^^ yeah, if normal applications are randomly crashing, that VERY much points to RAM. Even if memtest passes, I'd take out a stick and see if you become stable. If not, swap sticks. I'm almost postive you have a RAM problem based on your description of the problem.
a b $ Windows 7
January 13, 2012 3:13:12 PM

Yeah you get more accurate results from testing the sticks individually in memtest, or so I've heard... I personally haven't tried it :3
!