blue screens all the time

Page 1 of 2 12 LastLast

  1. xaar81
    Posts : 7
    windows 7 x64
       New #1

    blue screens all the time


    where do i start about 2 months ago i upgraded my system bought a E8500 cpu and 4870x2 gpu
    computer was fine before that no blue screens at all,was getting bsod all the time thought it was my gpu so bought a gtx 470 and i also bought new ram 4gb black dragon,installed windows 7 again but NO bsod again,
    im getting the same error PAGE_FAULT_IN_NONPAGED_AREA its usually a memory error but its brand new and ive tested it with memtestx86 passed here is a list of the errors

    PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ntoskrnl.exe
    PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 spsys.sys
    PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 atapi.sys
    PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ataport.SYS
    PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 nvlddmkm.sys then one says

    0x00000124 ntoskrnl.exe
    im really going crazy dont know what to do cant figure out whats the problem after i bought the new gpu and memory i thought that would clear it up maybe its cpu or motherboard maybe even psu or hd here is the full specs

    E8500
    Asus P5Q-Deluxe
    Gtx 470
    4GB Black dragon p8500 1066ram
    Akasa Powermax 850w here is the link for psu specs

    http://cgi.ebay.ie/Akasa-Powermax- [...] 45f425d345

    cpu failed on prime 95 in place large ffts with this error
    [Sat Jul 31 13:48:08 2010]
    FATAL ERROR: Rounding was 0.5, expected less than 0.4
    Hardware failure detected, consult stress.txt file.
    FATAL ERROR: Rounding was 0.5, expected less than 0.4
    Hardware failure detected, consult stress.txt file.
    [Sat Jul 31 16:31:54 2010]
    Self-test 8K passed!
    Self-test 8K passed!
    [Sat Jul 31 16:47:35 2010]
    Self-test 10K passed!
    Self-test 10K passed!

    memory tested and is fine

    im really stuck as to what the problem may be dont want to buy a new cpu and find out its the motherboard or psu or even hd any help would be gladly taken

    here are the errors

    073110-26239-01.dmp 7/31/2010 4:04:47 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`069f5994 00000000`00000000 fffff880`05ee2847 00000000`00000005 atapi.sys atapi.sys+2a10 x64 C:\Windows\Minidump\073110-26239-01.dmp 2 15 7600
    073110-19125-01.dmp 7/31/2010 4:03:21 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a0`0155015b 00000000`00000000 fffff880`05a98d66 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\073110-19125-01.dmp 2 15 7600
    073110-18829-01.dmp 7/31/2010 4:02:02 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`0133a479 00000000`00000000 fffff880`05a2fd66 00000000`00000005 ataport.SYS ataport.SYS+60c5 x64 C:\Windows\Minidump\073110-18829-01.dmp 2 15 7600
    073110-19188-01.dmp 7/31/2010 3:18:45 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`017058d6 00000000`00000000 fffff880`05b9ed66 00000000`00000005 atapi.sys atapi.sys+2a10 x64 C:\Windows\Minidump\073110-19188-01.dmp 2 15 7600
    073110-19047-01.dmp 7/31/2010 3:17:25 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`085deea6 00000000`00000000 fffff880`0613bd66 00000000`00000005 spsys.sys spsys.sys+10efc x64 C:\Windows\Minidump\073110-19047-01.dmp 2 15 7600
    073110-25552-01.dmp 7/31/2010 10:59:00 AM 0x00000124 00000000`00000000 fffffa80`04fde8f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a5f3c NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\073110-25552-01.dmp 2 15 7600
    073110-25927-01.dmp 7/31/2010 3:32:42 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`02618ea8 00000000`00000000 fffff880`05d22d66 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\073110-25927-01.dmp 2 15 7600
    073110-16021-01.dmp 7/31/2010 12:33:40 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`029e4877 00000000`00000000 fffff880`0522fd66 00000000`00000005 spsys.sys spsys.sys+10efc x64 C:\Windows\Minidump\073110-16021-01.dmp 2 15 7600
    073110-22604-01.dmp 7/31/2010 12:26:10 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`017ef876 00000000`00000000 fffff880`0522fd66 00000000`00000005 spsys.sys spsys.sys+10efc x64 C:\Windows\Minidump\073110-22604-01.dmp 2 15 7600
    073110-16333-01.dmp 7/31/2010 12:23:49 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`0ce4e83b 00000000`00000000 fffff880`05199d66 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\073110-16333-01.dmp 2 15 7600
    073010-16676-01.dmp 7/30/2010 8:49:16 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`01263f14 00000000`00000000 fffff880`05b1ad66 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\073010-16676-01.dmp 2 15 7600
    073010-17066-01.dmp 7/30/2010 5:28:18 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`015c0878 00000000`00000000 fffff880`0522fd66 00000000`00000005 atapi.sys atapi.sys+16e4 x64 C:\Windows\Minidump\073010-17066-01.dmp 2 15 7600
    072910-15116-01.dmp 7/30/2010 6:06:21 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a0`0199d03d 00000000`00000000 fffff880`022aad66 00000000`00000000 spsys.sys spsys.sys+10efc x64 C:\Windows\Minidump\072910-15116-01.dmp 2 15 7600
    073010-24024-01.dmp 7/30/2010 4:12:53 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`0128c929 00000000`00000000 fffff880`04c5cd66 00000000`00000005 atapi.sys atapi.sys+2764 x64 C:\Windows\Minidump\073010-24024-01.dmp 2 15 7600
    073010-21138-01.dmp 7/30/2010 3:02:54 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`011cbf08 00000000`00000000 fffff880`05bbed66 00000000`00000005 spsys.sys spsys.sys+10efc x64 C:\Windows\Minidump\073010-21138-01.dmp 2 15 7600
    073010-18236-01.dmp 7/30/2010 2:25:48 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`01d85365 00000000`00000001 fffff880`05638895 00000000`00000005 nvlddmkm.sys nvlddmkm.sys+1f3f1e x64 C:\Windows\Minidump\073010-18236-01.dmp 2 15 7600
    073010-17019-01.dmp 7/30/2010 2:15:59 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`018d1f8f 00000000`00000000 fffff880`05721d66 00000000`00000005 spsys.sys spsys.sys+10e7c x64 C:\Windows\Minidump\073010-17019-01.dmp 2 15 7600
    073010-17877-01.dmp 7/30/2010 12:25:02 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffad8`05d39c98 00000000`00000001 fffff880`0fed28d8 00000000`00000005 nvlddmkm.sys nvlddmkm.sys+1f066e x64 C:\Windows\Minidump\073010-17877-01.dmp 2 15 7600
    072910-16161-01.dmp 7/29/2010 11:57:53 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`00ea5ea9 00000000`00000000 fffff880`0522fd66 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\072910-16161-01.dmp 2 15 7600
    072910-24476-02.dmp 7/29/2010 11:22:48 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`0190afd7 00000000`00000000 fffff880`056eed66 00000000`00000005 spsys.sys spsys.sys+10e7c x64 C:\Windows\Minidump\072910-24476-02.dmp 2 15 7600
    072910-18018-01.dmp 7/29/2010 11:16:04 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`013919be 00000000`00000000 fffff880`0562fd66 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\072910-18018-01.dmp 2 15 7600
    072910-24476-01.dmp 7/29/2010 11:11:32 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`02debfb7 00000000`00000000 fffff880`0575fd66 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\072910-24476-01.dmp 2 15 7600
    072910-31964-01.dmp 7/29/2010 10:48:18 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a1`067f298e 00000000`00000000 fffff880`0542fd66 00000000`00000005 atapi.sys atapi.sys+2764 x64 C:\Windows\Minidump\072910-31964-01.dmp 2 15 7600
      My Computer
    Quote Quote

  3. merkat106
    Posts : 474
    Windows 7 Enterprise x64 SP1
       New #2

    I know you copy and pasted your debugging, but could you actually attach the files?
    https://www.sevenforums.com/tutorials...ms.html?filter[3]=Crashes and debugging
      My Computer
    Quote Quote

  4. NTFS
    Posts : 100
    Windows 7 Home Premium x86-64
       New #3

    Did you run Driver Sweeper to clean out the old drivers? Is the hardware at stock?
      My Computer
    Quote Quote

  6. ttran
    Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       New #4

    Yes, please upload your minidump to us, in the meantime, here are few things you want to try:

    Stop code 124 is almost always related to hardware. As you mentioned, memtestx86 run ok, so here is other stress test you might want to try:
    Test hard drive: HD Diagnostic (Download HD test from Manufacture's site)
    Try this free stress test: http://www.mersenne.org/freesoft/
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    The Test selection box and the stress.txt file describes what components that the program stresses.
    Test your temps: SpeedFan - Access temperature sensor in your computer

    Read this article to know what is stop code 124 and what to try:
    https://www.sevenforums.com/crash-loc...-what-try.html
      My Computer
    Quote Quote

  7. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #5

    Please test your hardware. First, RAM.
    JK said:
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
    Next comes hard drive: HD Diagnostic

    Then CPU: https://www.sevenforums.com/tutorials...t-prime95.html

    Test your temps: SpeedFan - Access temperature sensor in your computer

    Are you doing any overclocking? If so, reset to defaults.

    Please follow these directions for the future: https://www.sevenforums.com/crashes-d...tructions.html

    Edit: Sorry I didn't see you there ttran.
      My Computer
    Quote Quote

  8. xaar81
    Posts : 7
    windows 7 x64
    Thread Starter
       New #6

    sorry guys heres the dump files
      My Computer
    Quote Quote

  10. xaar81
    Posts : 7
    windows 7 x64
    Thread Starter
       New #7

    ive tested the memory no errors its brand new ram a few days old so im at a loss to what the problem is
      My Computer
    Quote Quote

  11. ttran
    Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       New #8

    Again, all the crash dump suggest this is hardware issue. personally I suspect the hard drive. Please follow all the stress test that Jonathan King suggested.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.173\073110-22604-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Sat Jul 31 06:24:53.992 2010 (UTC + 7:00)
System Uptime: 0 days 0:01:24.553
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a1017ef876, 0, fffff8800522fd66, 5}

Unable to load image \SystemRoot\system32\drivers\spsys.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys

Could not read faulting driver name
Probably caused by : spsys.sys ( spsys+2fd66 )

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  12. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #9

    I see several issues. First, where did you get your copy of Windows 7?

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

    Install the latest ATK0110 Utilitiy Driver for Vista/7: ASUSTeK Computer Inc.-Support-

    Your video card drivers were blamed by one dump, but I'm willing to ignore that for the time being.

    ...Summary of the Dumps:
    Code:
    
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug  1 20:32:11.899 2010 (UTC - 4:00)
System Uptime: 0 days 1:30:23.476
BugCheck 50, {fffff8a102629812, 0, fffff88006f3bd66, 5}
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : spsys.sys ( spsys+2fd66 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 19:23:54.955 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:18.641
BugCheck 50, {fffffad805d39c98, 1, fffff8800fed28d8, 5}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a68d8 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 18:21:23.410 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:38.095
BugCheck 50, {fffff8a10190afd7, 0, fffff880056eed66, 5}
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : spsys.sys ( spsys+2fd66 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jul 30 01:05:15.967 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:21.528
BugCheck 50, {fffff8a00199d03d, 0, fffff880022aad66, 0}
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : spsys.sys ( spsys+2fd66 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  sppsvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
      My Computer
    Quote Quote

  13. xaar81
    Posts : 7
    windows 7 x64
    Thread Starter
       New #10

    i did a sfc/scannow scan it found errors here is the cbs log if it helps
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
Uploaded dump files. it's been happening for weeks now. I'm not sure why but i have multiple STOP codes at the blue screen too. http://www.filedropper.com/rob-pc-2708201419253404
Hi, I have problem with my new computer, random BSODs from time to time, please help Thanks!
Rogue Blue screens/Black screens
in BSOD Help and Support

And I'm back again giving you another annoying dilemma to help me with. Okay, the problems are on my main pc. The specs are below: Windows 7 Ult. 64bit Gigabyte 880GA-UD3H AMD Phenom II X6 1100T 4GB DDR3 PNY RAM 500GB Seagate HDD Dynex 400 Watt Power Supply
Blue Screens started out of the blue.
in BSOD Help and Support

All of a sudden when I was playing Black Ops I got a Blue Screen and ever since I've been getting random BS's once in a while and I have no idea why and would highly appreciate any help I can get. I was googling around and found this site and saw you had helped a lot of people so I thought why not...
Blue Screens
in Hardware & Devices

Hi all, I purchased a new desktop recently and installed Windows 7 Home Basic on it. Since then I have been receiving constant blue screens which point to Windows system processes (.dmp files attached). I took it in and they replaced the RAM, but the problem continues. Can anyone offer some...
Our Sites
Site Links
About 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 17:39.
Find Us