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

I think it's my RAM


  • Please log in to reply
8 replies to this topic

#1 Chexmix

Chexmix

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 02 September 2012 - 03:59 AM

OK my computer started giving me a bsod for a sec then reboots I'm thinking it has to do with my ram because I have 3 2gig sticks and when I goto fast defrag it shows I have only 4gigs.

but Ive ran windows memory manager? I think its called no errors i've also ran memtest86 for 5 hours and no errors, also if I do have bad ram how can I pinpoint which stick it is?

BC AdBot (Login to Remove)

 


#2 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:38 AM

Posted 02 September 2012 - 08:58 AM

Hello Chexmix,

We're sorry to hear that you are experiencing a BSOD problem. It would be helpful if you could provide a liitle more information about your computer by completing the following:


( 1 ) Was anything "new" just before the BSODs started (i.e. new hardware, software, malware, error messages)?


( 2 ) To get a view of your "minidump" files, please download Nirsoft's BlueScreenView.zip to your desktop: http://www.nirsoft.net/utils/bluescreenview.zip
  • Unzip the file and run BlueScreenView.exe.
  • When the scan has completed, click "Edit" from top menu, then "Select all."
  • Go to "File," "Save selected items."
  • Save it as BSOD.txt. Double click on the BSOD.txt, highlight the entire file, and copy it into your next post.
( 3 ) To help us get a better look at your computer hardware, please follow the instructions below to "Publish a Snapshot" of your system using Speccy.
http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792

Below is only for those who cannot get online:
  • Please take caution when attaching a text file to your post if you cannot copy/paste the link, per above instructions. You will need to edit the text file to make sure that your Windows Key is not present.

Regards,
Brooks



 


#3 Chexmix

Chexmix
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 02 September 2012 - 04:57 PM

Hi thanks for the quick response. As a matter of fact a month and half ago I just installed a video card and had a virus that someone on here helped me get rid of however this just started doing this after our recent hurricane It got so bad as it does it all the time I took it apart reinstalled my ram and seems to work however I want to see if you can find out if there is still something amiss in my system here are the following you've requested

http://speccy.piriform.com/results/o2WZrmtbIGOzDwDhFWFIJ7G

==================================================
Dump File : 090112-41621-01.dmp
Crash Time : 9/1/2012 8:43:37 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa80`05670960
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090112-41621-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,455
==================================================

==================================================
Dump File : 090112-38984-01.dmp
Crash Time : 9/1/2012 8:32:50 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00001236
Parameter 2 : fffffa80`06cd46d0
Parameter 3 : fffffa80`06cd47d0
Parameter 4 : 00000000`000ca15b
Caused By Driver : nwifi.sys
Caused By Address : nwifi.sys+11bb6d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090112-38984-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,455
==================================================

==================================================
Dump File : 090112-25178-01.dmp
Crash Time : 9/1/2012 8:07:57 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000040
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`04899668
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090112-25178-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,455
==================================================

==================================================
Dump File : 090112-26410-01.dmp
Crash Time : 9/1/2012 7:12:48 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`000b5927
Parameter 3 : fffff880`0aa940a0
Parameter 4 : 00000000`00000000
Caused By Driver : dfsc.sys
Caused By Address : dfsc.sys+6a1d0a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090112-26410-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,455
==================================================

==================================================
Dump File : 090112-29078-01.dmp
Crash Time : 9/1/2012 7:06:24 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`00112adf
Parameter 3 : 00000000`00000003
Parameter 4 : 00000000`00138fa9
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+8d91d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090112-29078-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,455
==================================================

==================================================
Dump File : 090112-27440-01.dmp
Crash Time : 9/1/2012 7:05:05 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000003`c0000582
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`0488b05a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090112-27440-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 301,455
==================================================

#4 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:38 AM

Posted 03 September 2012 - 08:53 AM

Hi Chexmix,

( 1 ) What is the make and model number of your Desktop computer?

( 2 ) Please start by running Windows Check Disk program to check for and fix any file system errors:
  • Double click on the "(My) Computer" icon on your Desktop or in your Start Menu.
  • Right click on the drive to test and click "Properties."
  • Select "Tools" tab and under "Error checking" click "Check now."
  • Make sure that only the following box is checked.
    • Automatically fix file system errors
  • Click "Start."
  • Click "Schedule disk check" then reboot your computer.

( 3 ) I know you have previously tested your memory, but you should test for a longer period of time. Please follow this post: Windows 7 - RAM - Test with Memtest86+ to either create a bootable CD or USB flash drive to run the test.
  • My recommendation would be to run MemTest86+ overnight; 12 hours rather than just 7 passes.
  • There should be NO errors reported.
  • The test can be stopped (press ESC key) as soon as an error is reported.
  • See Part 3: If you have errors. <==

( 4 ) From your Speccy Snapshot:
Hard Drives
WDC WD10 01FAES-60Z2A0 SATA Disk Device

Manufacturer: Western Digital
S.M.A.R.T
C7 UltraDMA CRC Error Count: 200 (200) Data 0000000003 <==
Partition 1
Partition ID: Disk #0, Partition #1
Disk Letter: C:
File System: NTFS
Volume Serial Number: EC30C154
Size: 919GB
Used Space: 805GB (88%)
Free Space: 115GB (12%) <==

UltraDMA CRC Error Count http://en.wikipedia.org/wiki/S.M.A.R.T.
  • "The count of errors in data transfer via the interface cable as determined by ICRC (Interface Cyclic Redundancy Check."
While this value is low, it can reflect a loose or bad SATA data cable. Check that the hard drive cable is firmly attached, especially if you have been working inside the tower. SATA cables that lock in place are best.

Hard drive free space at 12% is low and this can effect performance. It would be best to increase free space to 25% or better by offloading larger files to other media.

( 5 ) From Speccy:
Motherboard
Voltage
+3.3V: 2.773 V <==
(Tolerance should be +/- 5% (minimal tolerance +3.135 VDC) - above value is out of range. It could be a false reading or may implicate the power suppy)

Regards,
Brooks



 


#5 Chexmix

Chexmix
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 04 September 2012 - 04:02 PM

It's an HP p6674y I ran check disc and I will run memtest tonight and report back

#6 Chexmix

Chexmix
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 07 September 2012 - 10:47 PM

ok so no errors on chk disc and ran memtest for 24 hours 15 passes no errors It's not freezing or bsod anymore

#7 narenxp

narenxp

  • BC Advisor
  • 16,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:38 AM

Posted 07 September 2012 - 10:51 PM

Is this the same PC

http://www.bleepingcomputer.com/forums/topic467526.html

#8 Chexmix

Chexmix
  • Topic Starter

  • Members
  • 98 posts
  • OFFLINE
  •  
  • Local time:08:38 AM

Posted 07 September 2012 - 11:57 PM

no thats for my laptop the ram problem is for my desktop just so happens they both HP

#9 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:38 AM

Posted 08 September 2012 - 07:57 AM

It's not freezing or bsod anymore


I sounds as if your Desktop system is running better.

Regards,
Brooks



 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users