Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD and Random Freezes


  • Please log in to reply
12 replies to this topic

#1 Flagshipfail

Flagshipfail

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 20 February 2012 - 09:23 PM

I have been getting random BSODs and lockups. Not sure why. I have checked my ram with memtest switched it out and also swapped video cards. The BSODs I get are either 0x00000008e or 0x0000000A Attached are my crash reports. So if anyone can help that would be awesome.

BC AdBot (Login to Remove)

 


#2 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 20 February 2012 - 09:27 PM

here is the file didnt attach it with my first post

Attached Files

  • Attached File  PCHF.zip   414.87KB   5 downloads


#3 hamluis

hamluis

    Moderator


  • Moderator
  • 55,753 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:11 AM

Posted 20 February 2012 - 09:37 PM

For the sake of convenience for all members reading your topic...please do the following.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt, copy all content and paste it into your next reply.

Louis

#4 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 20 February 2012 - 09:41 PM

==================================================
Dump File : Mini022012-01.dmp
Crash Time : 2/20/2012 5:19:33 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xa14451bd
Parameter 2 : 0x00000001
Parameter 3 : 0xb7de98b6
Parameter 4 : 0x00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+68b6
File Description : IDE/ATAPI Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Crash Address : atapi.sys+68b6
Stack Address 1 : ntoskrnl.exe+1819f
Stack Address 2 : ACPI.sys+6e12
Stack Address 3 : ntoskrnl.exe+1819f
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022012-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini021712-01.dmp
Crash Time : 2/17/2012 10:18:26 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x8d000084
Parameter 2 : 0x00000000
Parameter 3 : 0xb7d12558
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+22f43
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini021712-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

==================================================
Dump File : Mini021512-02.dmp
Crash Time : 2/15/2012 9:54:36 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000001
Parameter 2 : 0x000000ff
Parameter 3 : 0x00000001
Parameter 4 : 0x8052872e
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini021512-02.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

==================================================
Dump File : Mini021512-01.dmp
Crash Time : 2/15/2012 7:02:48 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0xd4f71967
Parameter 2 : 0x000000ff
Parameter 3 : 0x00000000
Parameter 4 : 0x80545b7f
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+6d758
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+6d758
Stack Address 1 : ntkrnlpa.exe+6eb7f
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini021512-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

==================================================
Dump File : Mini011912-01.dmp
Crash Time : 1/19/2012 9:09:24 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xc9f62920
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x80502cd1
Caused By Driver : hal.dll
Caused By Address : hal.dll+298e
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+2bcd1
Stack Address 1 : hal.dll+298e
Stack Address 2 : ntoskrnl.exe+6a67c
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011912-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini011812-01.dmp
Crash Time : 1/18/2012 12:25:07 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x54fc1dfb
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000001
Parameter 4 : 0x8050327b
Caused By Driver : afd.sys
Caused By Address : afd.sys+1085a
File Description : Ancillary Function Driver for WinSock
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6142 (xpsp_sp3_gdr.110817-1643)
Processor : 32-bit
Crash Address : ntoskrnl.exe+2c27b
Stack Address 1 : ntoskrnl.exe+2bf51
Stack Address 2 : ntoskrnl.exe+2b13e
Stack Address 3 : ntoskrnl.exe+2b32b
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011812-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini011512-02.dmp
Crash Time : 1/15/2012 3:38:07 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xca4cf8a2
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x80502eb4
Caused By Driver : portcls.sys
Caused By Address : portcls.sys+4fa
File Description : Port Class (Class Driver for Port/Miniport Devices)
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Crash Address : ntoskrnl.exe+2beb4
Stack Address 1 : ntoskrnl.exe+25943
Stack Address 2 : ntoskrnl.exe+2597c
Stack Address 3 : portcls.sys+4fa
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011512-02.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini011512-01.dmp
Crash Time : 1/15/2012 1:31:52 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xf7d106f6
Parameter 2 : 0x00000008
Parameter 3 : 0xf7d106f6
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address :
Stack Address 1 : Ntfs.sys+300a
Stack Address 2 : ntoskrnl.exe+1819f
Stack Address 3 : ntoskrnl.exe+1819f
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011512-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini011412-01.dmp
Crash Time : 1/14/2012 7:38:41 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xf31c73e8
Parameter 2 : 0x00000001
Parameter 3 : 0x805ad757
Parameter 4 : 0x00000002
Caused By Driver : aswSnx.SYS
Caused By Address : aswSnx.SYS+37829
File Description : avast! Virtualization Driver
Product Name : avast! Antivirus System
Company : AVAST Software
File Version : 6.0.1367.0
Processor : 32-bit
Crash Address : ntoskrnl.exe+d6757
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011412-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini011312-02.dmp
Crash Time : 1/13/2012 8:27:44 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xa14f9cd8
Parameter 2 : 0x00000001
Parameter 3 : 0x8054b168
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74168
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+74168
Stack Address 1 : ntoskrnl.exe+7475f
Stack Address 2 : ntoskrnl.exe+e8efa
Stack Address 3 : ntoskrnl.exe+e9272
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011312-02.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini011312-01.dmp
Crash Time : 1/13/2012 4:21:52 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x06004803
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x804ff882
Caused By Driver : hal.dll
Caused By Address : hal.dll+2427
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+28882
Stack Address 1 : hal.dll+2ef2
Stack Address 2 : hal.dll+2427
Stack Address 3 : ati2mtag.sys+51c7
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011312-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini010712-01.dmp
Crash Time : 1/7/2012 10:52:29 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x804ed79f
Parameter 3 : 0xa270e988
Parameter 4 : 0x00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+6f56
File Description : Microsoft Filesystem Filter Manager
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+1679f
Stack Address 1 : fltmgr.sys+6f56
Stack Address 2 : fltmgr.sys+5df3
Stack Address 3 : fltmgr.sys+6366
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010712-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini120111-01.dmp
Crash Time : 12/1/2011 12:59:57 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xca1b5fe8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xb2d99720
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+1b720
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Crash Address : USBPORT.SYS+1b720
Stack Address 1 : usbohci.sys+18fd
Stack Address 2 : usbohci.sys+2bd3
Stack Address 3 : USBPORT.SYS+84aa
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini120111-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini113011-01.dmp
Crash Time : 11/30/2011 10:25:29 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xff814f00
Parameter 2 : 0x00000008
Parameter 3 : 0xff814f00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1f5ba
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
Processor : 32-bit
Crash Address :
Stack Address 1 : win32k.sys+1f614
Stack Address 2 : ntoskrnl.exe+6a67c
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini113011-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini112611-02.dmp
Crash Time : 11/26/2011 4:24:16 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe6d09b14
Parameter 2 : 0x00000001
Parameter 3 : 0xbf83a9e9
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+3a9e9
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
Processor : 32-bit
Crash Address : win32k.sys+3a9e9
Stack Address 1 : win32k.sys+3a9bb
Stack Address 2 : ati3duag.dll+abb28
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112611-02.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 106,496
==================================================

==================================================
Dump File : Mini112611-01.dmp
Crash Time : 11/26/2011 4:10:25 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xca197128
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0xb8499b54
Caused By Driver : usbohci.sys
Caused By Address : usbohci.sys+1b54
File Description : OHCI USB Miniport Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Crash Address : usbohci.sys+1b54
Stack Address 1 : usbohci.sys+2bd3
Stack Address 2 : USBPORT.SYS+84aa
Stack Address 3 : USBPORT.SYS+9768
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112611-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 106,496
==================================================

==================================================
Dump File : Mini082211-04.dmp
Crash Time : 8/22/2011 8:54:29 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x80ee56e8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xb8328c8e
Caused By Driver : PCIIDEX.SYS
Caused By Address : PCIIDEX.SYS+c8e
File Description : PCI IDE Bus Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Crash Address : PCIIDEX.SYS+c8e
Stack Address 1 : atapi.sys+7aff
Stack Address 2 : sptd.sys+18a29
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082211-04.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 106,496
==================================================

==================================================
Dump File : Mini082211-03.dmp
Crash Time : 8/22/2011 6:38:54 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xb965b1f0
Parameter 2 : 0x00000000
Parameter 3 : 0xbf8022af
Parameter 4 : 0x00000002
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+22af
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
Processor : 32-bit
Crash Address : win32k.sys+22af
Stack Address 1 : win32k.sys+28c9
Stack Address 2 : win32k.sys+1e83
Stack Address 3 : win32k.sys+19ede
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082211-03.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 106,496
==================================================

==================================================
Dump File : Mini082211-02.dmp
Crash Time : 8/22/2011 2:01:01 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041284
Parameter 2 : 0x7fc18001
Parameter 3 : 0x00001a84
Parameter 4 : 0xc0883000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22f43
Stack Address 1 : ntoskrnl.exe+4c339
Stack Address 2 : ntoskrnl.exe+4cbbf
Stack Address 3 : ntoskrnl.exe+4cfd8
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082211-02.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini082211-01.dmp
Crash Time : 8/22/2011 1:59:30 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x80cf4740
Parameter 2 : 0x00000002
Parameter 3 : 0x00000008
Parameter 4 : 0x80cf4740
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address :
Stack Address 1 : ntoskrnl.exe+2b32b
Stack Address 2 : ntoskrnl.exe+6eeef
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082211-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini082011-01.dmp
Crash Time : 8/20/2011 9:53:37 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x4294a628
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x805095fb
Caused By Driver : hal.dll
Caused By Address : hal.dll+29f0
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Crash Address : ntoskrnl.exe+325fb
Stack Address 1 : ntoskrnl.exe+1a806
Stack Address 2 : afd.sys+124ba
Stack Address 3 : afd.sys+11670
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082011-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 2600
Dump File Size : 106,496
==================================================

==================================================
Dump File : Mini092310-01.dmp
Crash Time : 9/23/2010 7:58:38 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x895cbda8
Parameter 2 : 0x8992b008
Parameter 3 : 0x89abdd00
Parameter 4 : 0x00000001
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+d0ddb
File Description : NVIDIA Windows XP Display driver, Version 285.58
Product Name : NVIDIA Windows XP Display driver, Version 285.58
Company : NVIDIA Corporation
File Version : 6.14.12.8558
Processor : 32-bit
Crash Address : nv4_disp.dll+d0d98
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini092310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 77,291
==================================================

#5 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:11:11 PM

Posted 21 February 2012 - 01:58 AM

I've had a quick look at some of the recent minidumps that you attached to your second post, and it is clear that there is a hardware problem, most likely with the RAM.

I couldn't help but notice that the RAM sticks you have been using at various times (both the 1GB and 2GB sticks) are ECC type.

Current Memory Type 0140h - ECC DIMM


I checked the specifications of the motherboard and it requires that you use non-ECC type.

Supports DDR3 1600(OC)/1333/1066/800 non-ECC, un-buffered memory

Motherboard: ASRock M3A770DE http://www.asrock.com/mb/overview.asp?model=m3a770de

I suspect this may be the source of your long-term problem with system crashes. Would you please check and confirm this "quick guess" of mine.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 21 February 2012 - 11:09 AM

I have no way of getting any new memory. And that makes no sense because my girlfriend has the exact same motherboard and memory(for longer I might add) so why did she not have any issues and I had more that a few

Update: After looking at the original memory and the memory I have currently in the system they both are non ecc unbuffered memory

Edited by Flagshipfail, 21 February 2012 - 11:13 AM.


#7 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 21 February 2012 - 11:18 AM

I am wondering how you knew what kind of memory I had when I had not posted any of that information.

#8 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:11:11 PM

Posted 21 February 2012 - 05:24 PM

I am wondering how you knew what kind of memory I had when I had not posted any of that information.

The WinDbg output on running the minidumps provides a lot of information. You might wish to take a look at the output I got running the most recent minidump. See the Spoiler below.

You said in your first post: "I have checked my ram with memtest".
  • Did you test each stick individually?
  • Did you test each stick for a minimum of 24 hours?
  • Did you use memtest86+ ?
Before considering the possibility that the problem might lie elsewhere, I think we should rule out the RAM with as much certainty as possible. I noticed that you seem to be avoiding the first slot (the slot closest to the CPU) when installing the RAM sticks. Is there any reason for you doing that? Normally it is suggested that you use the first slot as a preference when running or testing a single stick of RAM. I will ask that you use the first slot for all your testing. I will include my instructions for running memtest86+ below.

Memory needs to be tested outside of Windows, so memtest86+ is run from a bootable CD.

:step1: To make a bootable CD with memtest86+:
  • Extract the downloaded zip file:
    • In Windows XP, right-click on the zip file and choose Extract all.
      The contents of the zip file (the .ISO image file) will be extracted to a folder in the same location as your zip file.
  • Burn the .ISO image to CD: If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
    • Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image
  • When the CD has been burned and verified as successful, it will be bootable.

:step2: Boot from the newly created CD.
  • You may need to configure BIOS or the Boot Menu to boot first from the CD.
  • memtest86+ will begin running automatically: You need do nothing else at this time.
  • Allow memtest86+ to run un-interrupted.
See the screenshots in this informative link: Diagnose with Memtest86+

There MUST be NO errors what-so-ever:
  • If you see an error, stop the test.
  • Then proceed to test each stick of RAM separately to sort the good from the bad.
A minimum test for some confidence in the result, should be 7 full passes (each "pass" is a series of different types of tests), with NO errors.
  • Allow memtest86+ to run for 24 hours for maximum confidence in the test result.
memtest86+ will continue running until you stop it:
  • Press the <ESCAPE> key to re-boot the computer, removing the memtest86+ CD.
===================
WinDbg output: Mini022012-01.dmp
Spoiler

Edited by AustrAlien, 21 February 2012 - 05:26 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 21 February 2012 - 06:20 PM

Well I dont see how it could be the memory when I swapped it all out for another set of memory that has not had any issues. Also I went to the manufactures site and checked both sets of memory. They both are Non ECC unbuffered memory.

Edited by Flagshipfail, 21 February 2012 - 06:23 PM.


#10 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:11:11 PM

Posted 21 February 2012 - 07:25 PM

So far, so good. Thanks for confirming all is well with the RAM type. Swapping RAM sticks with known good ones is always a good move to use as a test.

Try looking at running memtest86+ as ... using a known good stick of RAM to test the motherboard and CPU. We really need to know that with one stick of RAM in the first slot, you can run memtest86+ for 24 hours without error. Whether or not that can be done will determine the direction we proceed to trouble-shoot the BSOD problem.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 24 February 2012 - 12:08 AM

Well I switched them a bit ago and the issues are still happening. Does that still point to memory as the issue?

#12 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:11:11 PM

Posted 24 February 2012 - 05:41 AM

I'll have a closer look at the crash dumps tomorrow and let you know what I am thinking then.

Edit: Is there any sign at all that you may have a malware infection on the system, or have had to deal with an infection previously? Are there any other problems/issues with the system at all?

Edited by AustrAlien, 24 February 2012 - 05:46 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#13 Flagshipfail

Flagshipfail
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:11 AM

Posted 24 February 2012 - 11:50 AM

Other than the blue screens I have not had any issues. I have scanned with malwarebytes antimalware and I have avast and I scan with spybot everyother day.

Edit: I do have one question that I think may be the issue. Could a faulty memory slot be the issue? Cause if so That may be the issue. I read on newegg where I bought my motherboard that someone was having issues similar to my own.

Edited by Flagshipfail, 24 February 2012 - 11:57 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users