Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Multiple BSODs, help analyzing DMP files

22 May 2010   #1
Norron

Win 7
 
 
Multiple BSODs, help analyzing DMP files

Hello, I was hoping someone here could help me out. I recently upgraded from XP 32 to Win7 64 and am now experiencing frequent blue screen crashes. There is no new hardware except for 4 GB of memory that was already slotted into place that is now accessible in 64 bit Win 7. Also since it was a clean OS installation I've installed a large amount of programs and drivers.

The error I keep getting is PAGE FAULT IN NONPAGED AREA. I've managed to figure out enough to install the Microsoft debugging tools and read through some of the minidumps but I know nothing about analyzing them properly. The best I can see is that different processes are crashing but all causing the same error.

Dump files are attached. I'd greatly appreciate any help I can get as this is driving me crazy.


My System SpecsSystem Spec
.
22 May 2010   #2
Lomai

Win7 HP (x64)/Win7 Ultimate (x64)
 
 

Hi Norron

Welcome to SevenForums

Some of the other experts on site here will provide the specifics in relation to your minidump.
I did notice however that you had upgraded to 7 from XP.
Were you having any issues with XP prior to the upgrade?
The best recommendation when upgrading is to perform a clean installation as that ensures that any systemic faults/issues that were present in XP would not carry over to the new OS.
Recommend in the meantime that you do the following:

  1. Search for and upgrade to the latest hardware drivers - graphics card, mobo, sound-card (if add-on card) etc. Be sure to search specifically for the Win7-compatible drivers if they are available.
  2. Download memtest (Google is your friend) and run it to check whether it isn't your RAM that's causing the issue
  3. Download the latest DirectX (Feb2010) from Microsoft website and install that (Total file size around 106MB)
  4. Update your OS via windows update (optional but could come in handy in case there are new Microsoft drivers for your hardware)
Hope this helps and keep us posted on your progress

Regards
My System SpecsSystem Spec
22 May 2010   #3
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Norron View Post
Hello, I was hoping someone here could help me out. I recently upgraded from XP 32 to Win7 64 and am now experiencing frequent blue screen crashes. There is no new hardware except for 4 GB of memory that was already slotted into place that is now accessible in 64 bit Win 7. Also since it was a clean OS installation I've installed a large amount of programs and drivers.

The error I keep getting is PAGE FAULT IN NONPAGED AREA. I've managed to figure out enough to install the Microsoft debugging tools and read through some of the minidumps but I know nothing about analyzing them properly. The best I can see is that different processes are crashing but all causing the same error.

Dump files are attached. I'd greatly appreciate any help I can get as this is driving me crazy.
I am assuming you mean you did a clean install with format for you cant upgrade in place from 32 bit to 64.

these all had the same bugcheck (50) and all were related to memory and had a game running at the time.


That being said I would download a program called memtestx86, burn it to a cd, and run it for at least 5 passes to test the ram.

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS


Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 00:43:20.169 2010 (GMT-4)
System Uptime: 0 days 0:28:19.683
BugCheck 50, {fffff80007ffed60, 0, fffff80002e7285b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  LGDCore.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 00:13:55.068 2010 (GMT-4)
System Uptime: 0 days 0:16:50.941
BugCheck 50, {fffff8000a3cbd60, 0, fffff80002e8685b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  hl2.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 23:56:19.108 2010 (GMT-4)
System Uptime: 0 days 0:31:40.981
BugCheck 50, {fffff820088ea610, 0, fffff8000316de20, 5}
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+1e5 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SteamService.e
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 23:23:35.554 2010 (GMT-4)
System Uptime: 0 days 0:09:55.427
BugCheck 50, {fffff8000a620d60, 0, fffff80002ebd85b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  hl2.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 23:12:19.435 2010 (GMT-4)
System Uptime: 0 days 0:01:00.918
BugCheck 50, {fffffa0008f0ce90, 1, fffff80002eda7c4, 7}
Probably caused by : win32k.sys ( win32k!UserGlobalAtomTableCallout+38 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 23:10:23.519 2010 (GMT-4)
System Uptime: 0 days 0:37:01.017
BugCheck 50, {fffff8000852cd60, 0, fffff80002e8185b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 22:32:39.143 2010 (GMT-4)
System Uptime: 0 days 0:12:16.015
BugCheck 50, {fffff8000a59ed60, 0, fffff80002ed485b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  hl2.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 22:19:31.852 2010 (GMT-4)
System Uptime: 0 days 6:00:20.741
BugCheck 50, {fffff800072eed60, 0, fffff80002ebc85b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  hl2.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 16:18:19.768 2010 (GMT-4)
System Uptime: 0 days 0:01:01.656
BugCheck 50, {fffff80009f52d60, 0, fffff80002e8985b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  wmplayer.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 16:16:05.653 2010 (GMT-4)
System Uptime: 0 days 0:37:40.542
BugCheck 50, {fffffa000a45e224, 1, fffff800031699f7, 7}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+1b7 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  BFBC2Game.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 15:37:23.554 2010 (GMT-4)
System Uptime: 0 days 0:33:31.427
BugCheck 50, {fffffa0008c9ac90, 1, fffff80002ee07c4, 7}
Probably caused by : win32k.sys ( win32k!UserGlobalAtomTableCallout+38 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  firefox.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 03:21:01.586 2010 (GMT-4)
System Uptime: 0 days 1:09:08.084
BugCheck 50, {fffff8000a3aad60, 0, fffff80002e7585b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  WMPSideShowGad
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 02:10:29.349 2010 (GMT-4)
System Uptime: 0 days 1:26:18.221
BugCheck 50, {fffff8000a118d60, 0, fffff80002e7d85b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  wmplayer.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 20 22:42:56.070 2010 (GMT-4)
System Uptime: 0 days 8:55:15.958
BugCheck 50, {fffffa0008152624, 1, fffff800031b39f7, 7}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+1b7 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  BFBC2Game.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 19 21:58:28.524 2010 (GMT-4)
System Uptime: 0 days 0:02:29.022
BugCheck 50, {ffffe8a0030bf2f0, 0, fffff80003167062, 7}
Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+56 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  TeaTimer.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 19 21:54:48.734 2010 (GMT-4)
System Uptime: 0 days 0:38:27.232
BugCheck 50, {fffff8000a512d60, 0, fffff80002ecf85b, 2}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  hl2.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 19 21:15:36.343 2010 (GMT-4)
System Uptime: 0 days 7:32:51.872
BugCheck 50, {fffff8000a304730, 1, fffff960001432a5, 2}
Probably caused by : win32k.sys ( win32k!xxxDCEWindowHitTest2+209 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  hl2.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 18 13:12:27.107 2010 (GMT-4)
System Uptime: 0 days 0:30:24.995
BugCheck 50, {fffff8000a0a19a0, 0, fffff9600007ac56, 2}
Probably caused by : win32k.sys ( win32k!vExpandAndCopyText+46e )
BUGCHECK_STR:  0x50
PROCESS_NAME:  firefox.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 16 03:43:46.146 2010 (GMT-4)
System Uptime: 0 days 20:59:34.889
BugCheck 50, {fffff80006df5b28, 0, fffff960001b432c, 2}
Probably caused by : win32k.sys ( win32k!RGNOBJ::vSet+0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  firefox.exe
My System SpecsSystem Spec
.

22 May 2010   #4
Norron

Win 7
 
 

Thanks for the quick replies. And I did mean that it was a clean install from XP to Win 7. I forgot that Microsoft uses the word "upgrade" in that way.

I'll run a test on the RAM and report back.
My System SpecsSystem Spec
22 May 2010   #5
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Norron View Post
Thanks for the quick replies. And I did mean that it was a clean install from XP to Win 7. I forgot that Microsoft uses the word "upgrade" in that way.

I'll run a test on the RAM and report back.
Anytime thats what we are here for. Good Luck
My System SpecsSystem Spec
22 May 2010   #6
Lomai

Win7 HP (x64)/Win7 Ultimate (x64)
 
 

Thanks Norron.
Re-read your post and what zigzag stated xp>7 64

Better take a break

Regards
My System SpecsSystem Spec
22 May 2010   #7
Norron

Win 7
 
 

Well I'm back and after 5 passes memtest found no errors with my ram. I'm not sure if there is a way to generate a report from the program so I didn't bother. The only thing I can think of now that is a common link is that steam is always running when it blue screens. The most frequent crashes happen when I'm attempting to play games through the steam desktop client but it's also crashed a couple of times from the desktop while steam was running in the background. But I don't really know and am just guessing. You guys are the experts here.
My System SpecsSystem Spec
22 May 2010   #8
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Norron View Post
Well I'm back and after 5 passes memtest found no errors with my ram. I'm not sure if there is a way to generate a report from the program so I didn't bother. The only thing I can think of now that is a common link is that steam is always running when it blue screens. The most frequent crashes happen when I'm attempting to play games through the steam desktop client but it's also crashed a couple of times from the desktop while steam was running in the background. But I don't really know and am just guessing. You guys are the experts here.

Not a gamer, so expert on steeam, not. It may be that steam is the common link. Can it be re-installed?
My System SpecsSystem Spec
22 May 2010   #9
Norron

Win 7
 
 

It can indeed. I'll give that a try.
My System SpecsSystem Spec
23 May 2010   #10
Norron

Win 7
 
 

Alright, I tried uninstalling and then reinstalling Steam and no dice. I got 3 more BSODs today within minutes of each other. The dump files are attached. At this point I'm beginning to think it might be better to just format and reinstall again, even if it means spending a whole day to do it. Any opinions? Would just formatting from the win 7 install disk be the best option or is there another route you'd recommend?
My System SpecsSystem Spec
Reply

 Multiple BSODs, help analyzing DMP files




Thread Tools




Similar help and support threads
Thread Forum
Multiple BSODs daily, generally .sys files blamed in WinDbg
I have been fighting multiple daily BSODs since mid June. I am a novice, so the debugging process is confusing. I have managed to run it several times and it has pointed to different .sys files. I have run memtest86 for several passes and the built-in Windows Memory Check, with no errors. It...
BSOD Help and Support
Random BSODs Multiple files blamed!
I've had this computer for about a week or so and after I installed a new SSD and 4GB of ram. I did my research to ensure compatibility. I ran some memory tests that didn't find any issues but for the life of me I keep getting random BSODs. I used Blue Screen View and it shows multiple files...
BSOD Help and Support
I need help analyzing .dmp files due to frequent BSODS
I built my first gaming rig in january 2013, and everything went well. However about 2 days later i recieved my first BS0Ds, which was very dissapointing. I neglected to fix the issues and now all these BSODS are driving me crazy. I don't know how to analyze dmp files so any help would be...
BSOD Help and Support
Four BSODs and one system freeze this year, need help analyzing
This Toshiba laptop has been very stable until the last 5 weeks. I've had 4 BSODs and a system freeze requiring a power down to get things going again. The latest BSOD & the freeze both happened this week. I would appreciate suggestions in how to proceed. Thanks, Gordon Windows 7 - x64 ...
BSOD Help and Support
Can anyone help me further educate myself on analyzing DMP files?
Hey guys. I am very intrigued by dump files, and I have always wanted to learn how to successfully read and analyze them. With the help of your great guides in the Crash & Debugging forum, I have learned how to do most if not all of the basics as far as analyzing dump files in WinDbg goes. Now that...
General Discussion
Multiple BSODs - Help analysing dmp files
Hi there, My laptop is a clevo x7200 that I purchased on the 16th of December. Since the very first day I have been having BSODs at least every 3 days. Sometimes I have 2 or 3 of them in a day. I have run prime95 for 6h without any errors. I also run the extended windows memory test...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 19:12.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App