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 comes up intermittently


  • Please log in to reply
11 replies to this topic

#1 summerof91

summerof91

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 29 April 2013 - 01:54 PM

Hello, I have recently bought a used laptop and installed xp. I received blue screen a couple of times during installation than changed to another hard drive and everything went ok. Now i have xp installed but can not upgrade to sp3 as halfway through the update BSOD apears and computer reverts to  sp2. Also BSOD apears when trying to play back videos from you tube. I downloaded and installed drivers, and no viruses either.  It worked fine all day with light browsing.

 

The laptop is hp compaq nx7010 with 2gb of memory, ATI display.

 

The error I am getting is following:

error signature

BCCode : 100000be     BCP1 : CCE5D000     BCP2 : 3B5EA161     BCP3 : B82039B0
BCP4 : 0000000B     OSVer : 5_1_2600     SP : 2_0     Product : 256_1     

technical details

C:\DOCUME~1\sky\LOCALS~1\Temp\WER7e5f.dir00\Mini042913-03.dmp
C:\DOCUME~1\sky\LOCALS~1\Temp\WER7e5f.dir00\sysdata.xml

 

I sent the report but Microsoft can not help much here.
 

 

 



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:10 PM

Posted 29 April 2013 - 02:13 PM

Please download MiniToolBox  , save it to your desktop and run it.

 

Checkmark the following checkboxes:

  List last 10 Event Viewer log

  List Installed Programs

 List Users, Partitions and Memory size.

 

Click Go and paste the content into your next post.

 

Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link.  Do not copy/paste data from the report.

 

Louis



#3 summerof91

summerof91
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 30 April 2013 - 11:38 AM

Hello, the bsod comes now more often, always when trying to play a video. I suspect something wrong with the video adapter perhaps. I removed one gig of ram, also, the hdd has no caddy metal thingy, but i don't see how should it make any difference.  Anyway, here are the crash details, all over the place. BSOD acame already during windows installation a couple of times. 

windows version: Windows XP Service Pack 2, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Pentium® M processor 1.70GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 1073070080 total
VM: 2147352576, free: 2075119616

 

 

On Tue 4/30/2013 4:09:30 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043013-10.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9A90E)
Bugcheck code: 0x10000050 (0xFFFFFFFF9A357980, 0x0, 0xFFFFFFFF8057190E, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

 

 

On Tue 4/30/2013 3:28:24 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043013-08.dmp
This was probably caused by the following module: epfwtdi.sys (epfwtdi+0x4D00)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB80CC8D0, 0xFFFFFFFFB80CC5CC, 0xFFFFFFFFB80CC9C9)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\epfwtdi.sys
product: ESET Smart Security
company: ESET
description: ESET Personal Firewall TDI filter
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: epfwtdi.sys (ESET Personal Firewall TDI filter, ESET).
Google query: ESET NTFS_FILE_SYSTEM

 

 

 

 

 

On Tue 4/30/2013 3:21:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043013-07.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8599E703)
Bugcheck code: 0x100000D1 (0xC, 0x2, 0x0, 0xFFFFFFFF8599E703)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

 

 

 

 

 

 

On Tue 4/30/2013 2:19:51 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043013-05.dmp
This was probably caused by the following module: usbuhci.sys (usbuhci+0x3415)
Bugcheck code: 0x100000D1 (0x54, 0x2, 0x1, 0xFFFFFFFFF7B09415)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\usbuhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: UHCI USB Miniport Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

 

 

 

 

 

On Tue 4/30/2013 2:09:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043013-03.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x3545)
Bugcheck code: 0x100000D1 (0xFFFFFFFF86A9D2F5, 0x2, 0x0, 0xFFFFFFFFF7B19545)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

 

 

 

 

On Tue 4/30/2013 2:09:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043013-03.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x3545)
Bugcheck code: 0x100000D1 (0xFFFFFFFF86A9D2F5, 0x2, 0x0, 0xFFFFFFFFF7B19545)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

 

 

 

 

 

On Mon 4/29/2013 8:54:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042913-11.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xE051)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB7E5A414, 0xFFFFFFFFB7E5A110, 0xFFFFFFFFF767FF3E)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

 

 

 

 

 

On Mon 4/29/2013 8:43:24 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042913-09.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA09C8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805779C8, 0xFFFFFFFFF6330A8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/29/2013 8:42:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042913-08.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x3974)
Bugcheck code: 0x100000D1 (0x68, 0x2, 0x0, 0xFFFFFFFFF7AE1974)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



#4 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:40 AM

Posted 30 April 2013 - 11:54 AM

Hi Summerof91

 

It seems like you have a hardware issue and most likely it is RAM. I suggest running "Memtest" over night and see it detects any defects. BSOD during installation is a likely indication of memory corruption. Read the below guide carefully to do a proper RAM test.

 

 http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 
It may take several hours to complete so please be patient.


#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:10 PM

Posted 30 April 2013 - 12:31 PM

You also have a STOP 24 error...which usually indicates a possible problem with the file system (NTFS) or the hard drive itself.

 

Please download MiniToolBox  , save it to your desktop and run it.

 

Checkmark the following checkboxes:

  List last 10 Event Viewer log

  List Installed Programs

 List Users, Partitions and Memory size.

 

Click Go and paste the content into your next post.

 

Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link.  Do not copy/paste data from the report.

 

Louis



#6 summerof91

summerof91
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 30 April 2013 - 01:19 PM

Thanks for answers. Good call Anshad. The problem was the stick. I bought the new laptop because the old's laptops screen went dead a couple months after I upgraded ram. Never realized it was causing all the trouble. i removed it  from under the keyboard and swapped with the old that always worked fine and problems gone. The specs of the stick are the same, although the problematic has engraved ddr1 instead of ddr. ill post later a photo, architecture looks different.



#7 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:40 AM

Posted 30 April 2013 - 02:10 PM

Hi

 

Don't worry about the writings. If the RAM is an unsuitable one you shouldn't be able to fit it in the slot and it won't work even if you managed to fit in the wrong slot somehow. Sine the laptop boots fine RAM is OK and compatible with your system. Slight changes in speed (ie 333 vs 400 MHz) is also won't matter.  DDR and DDR1 are essentially the same. If it is different  it should have written DDR2 or DDR3 (or PC2 and PC3 sometimes) 



#8 summerof91

summerof91
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 01 May 2013 - 07:34 AM

The stick has no manufacturer on it or a code bar, the way any other I have do, bought it off eBay as new. Now I am pretty sure it destroyed my earlier laptop. Laptop was the same but there was no warnings for some reason. The screen was getting more red until finally the display was gone although it powered ok. 



#9 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:05:40 AM

Posted 01 May 2013 - 12:04 PM

Hi summerof91

 

How the laptop works after RAM replacement ? . Do you encounter anymore BSOD ?



#10 summerof91

summerof91
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 01 May 2013 - 12:14 PM

no, its fine. 



#11 summerof91

summerof91
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 01 May 2013 - 12:24 PM

One problem left  there seem to be  NTFS support gone. i try to install win7 via usb but can nor format flash into NTFS, just FAT32 option remains. Before I had a choice. I also tried to reinstall xp on another partition and it will not let me, most likely the same cause.



#12 summerof91

summerof91
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:10 AM

Posted 01 May 2013 - 12:39 PM

have solved it by optimize disk by performance through device manager/advanced options/policies






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users