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

Blue Screen of death


  • Please log in to reply
6 replies to this topic

#1 KINGLERMAN

KINGLERMAN

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:25 PM

Posted 09 March 2010 - 12:02 AM

Hey guys,

Not really sure about how to post this exactly to guidelines but I'll try.

Currently running windows XP SP3, currently fully updates. I run AVG free and Webroot antivirus spysweeper. I started having this problem a few months ago, and it had stopped for a while however now it is coming back worse than ever. Usually it happens when I start up a game after the PC has been turned on long enough, it will begin to load up and as it moving from my desktop to the game will just crash, blue screen.

PAGE FAULT IN NON-PAGED AREA

I tried to replicate it this morning to catch the digits as last time it happened was before I slept and I didn't write it down.

Another issue that causes crashing and I am sure they are related is every now and again high pitched noises (from watching movies or games) will suddenly cause my computer to keep looping the same noise over and over again. With 1 movie specifically you can even play one part and it will 100% crash however no error message comes up and I am forced to kill the laptop with the power switch.

I use all 3 uni blue products, the driver scanner, speed up my PC and registry booster each time I restart so I think I clear all the temp data and have checked the drivers and things (I mean thats why I have the programs right).

I have scanned my PC with both AVG free and Webroot and other than a few cookies that keep putting themselves there every restart I find nothing. I also used trendmicros housecall and that found a few minor problems with the system however this did not seem to fix it.

I was looking around the forums and saw some similar topics, but you said not to copy the methods to fix it so if there is any advice or suggestions you could offer it would be much appreciated because it is happening more and more. Next time it happens I will jot down the numbers, however are there any scans you could suggest to check my hardware and system services? I have had a look through event logs and read about this type of error online, I didn't try to fix anything however I just had a look around to see if I could see anything obvious (but I am not a tech so didn't want to tinker) and I suspect its my services. Mainly because there is an internal clock discrepancy between the crash and when I reboot, according to the computer I crashed at 11 18 but rebooted again at 11 17 ? That has to cause some problems I imagine, and 4 services report an error at the same time.

I am not sure if that is one or two problems, I am sure its 1 however if it is 2 perhaps I should make a second post in the hardware section about the sounds crashing my PC? Or are they the same?

I hope this is as clear as I can make it, I am not really a technical person with these sorts of things.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,723 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:25 AM

Posted 09 March 2010 - 08:53 AM

You can try the following:

BlueScreenView - http://www.nirsoft.net/utils/blue_screen_view.html

Double-click on BlueScreenView.exe file to run the program.

When scanning is done, go Edit/Select All...then File/Save Selected Items. Save the report as BSOD.txt.

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

Louis

#3 KINGLERMAN

KINGLERMAN
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:25 PM

Posted 10 March 2010 - 12:01 AM

==================================================
Dump File : Mini102009-02.dmp
Crash Time : 10/20/2009 9:33:25 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0x00000001
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0xf78c6d24
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini102009-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini102009-01.dmp
Crash Time : 10/20/2009 1:12:19 AM
Bug Check String :
Bug Check Code : 0x00008086
Parameter 1 : 0x00000000
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : iaStor.sys
Caused By Address : iaStor.sys+a43e
File Description : Intel Matrix Storage Manager driver - ia32
Product Name : Intel Matrix Storage Manager driver
Company : Intel Corporation
File Version : 8.9.2.1002
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini102009-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101909-01.dmp
Crash Time : 10/19/2009 8:00:47 AM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0x00000001
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x9a176960
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini101909-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101709-01.dmp
Crash Time : 10/17/2009 5:11:29 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0xc00000b5
Parameter 2 : 0xc00000b5
Parameter 3 : 0x00000000
Parameter 4 : 0x074f4000
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini101709-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100509-01.dmp
Crash Time : 10/5/2009 4:54:22 AM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0xc00000b5
Parameter 2 : 0xc00000b5
Parameter 3 : 0x00000000
Parameter 4 : 0x0a837000
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini100509-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100409-03.dmp
Crash Time : 10/4/2009 4:24:59 PM
Bug Check String :
Bug Check Code : 0x00008086
Parameter 1 : 0x00000000
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : iaStor.sys
Caused By Address : iaStor.sys+a43e
File Description : Intel Matrix Storage Manager driver - ia32
Product Name : Intel Matrix Storage Manager driver
Company : Intel Corporation
File Version : 8.9.2.1002
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini100409-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100409-02.dmp
Crash Time : 10/4/2009 4:13:43 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0x00000001
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0xa4388c4c
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini100409-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100409-01.dmp
Crash Time : 10/4/2009 2:26:32 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0x00000001
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0xa1cc8960
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini100409-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini092609-01.dmp
Crash Time : 9/26/2009 7:49:41 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0x00000001
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0xf78d2d24
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.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini092609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini060609-01.dmp
Crash Time : 6/6/2009 4:23:51 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe4a6d304
Parameter 2 : 0x00000000
Parameter 3 : 0xbf8a61a9
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+a61a9
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5863 (xpsp_sp3_gdr.090814-1258)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini060609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini031709-01.dmp
Crash Time : 3/17/2009 2:52:18 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbfa84477
Parameter 3 : 0xaa457738
Parameter 4 : 0xaa457434
Caused By Driver : atikvmag.dll
Caused By Address : atikvmag.dll+10477
File Description : Virtual Command And Memory Manager
Product Name : Virtual Command And Memory Manager
Company : ATI Technologies Inc.
File Version : 6.14.10.0070
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031709-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini030609-01.dmp
Crash Time : 3/6/2009 4:48:29 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : 0x863d0420
Parameter 2 : 0x8614e260
Parameter 3 : 0x86153be0
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1983d
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5863 (xpsp_sp3_gdr.090814-1258)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini030609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini123108-01.dmp
Crash Time : 12/31/2008 1:11:36 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x03b3a583
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22e0b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini123108-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini120608-01.dmp
Crash Time : 12/6/2008 4:58:34 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xa6d4ffcb
Parameter 3 : 0xa45e971c
Parameter 4 : 0x00000000
Caused By Driver : RtkHDAud.sys
Caused By Address : RtkHDAud.sys+59fcb
File Description : Realtek® High Definition Audio Function Driver
Product Name : Realtek® High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
Company : Realtek Semiconductor Corp.
File Version : 5.10.0.5440 built by: WinDDK
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini120608-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111808-01.dmp
Crash Time : 11/18/2008 3:11:52 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbfa84477
Parameter 3 : 0xaac9a310
Parameter 4 : 0x00000000
Caused By Driver : atikvmag.dll
Caused By Address : atikvmag.dll+10477
File Description : Virtual Command And Memory Manager
Product Name : Virtual Command And Memory Manager
Company : ATI Technologies Inc.
File Version : 6.14.10.0070
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini111808-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111708-01.dmp
Crash Time : 11/17/2008 3:32:42 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe46d69e8
Parameter 2 : 0x00000001
Parameter 3 : 0xbfaf6b26
Parameter 4 : 0x00000001
Caused By Driver : ati3duag.dll
Caused By Address : ati3duag.dll+20b26
File Description : ati3duag.dll
Product Name : ATI Technologies Inc. Radeon DirectX Universal Driver
Company : ATI Technologies Inc.
File Version : 6.14.10.0555
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini111708-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111408-03.dmp
Crash Time : 11/14/2008 12:03:32 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000006
Parameter 2 : 0x860b0da8
Parameter 3 : 0x88fcc80c
Parameter 4 : 0x805d10da
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22e0b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini111408-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111408-02.dmp
Crash Time : 11/14/2008 11:39:28 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x00ffffff
Parameter 3 : 0xa45d2bf0
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini111408-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111408-01.dmp
Crash Time : 11/14/2008 10:51:47 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x000000ac
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x806e4a2a
Caused By Driver : hal.dll
Caused By Address : hal.dll+2a2a
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
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini111408-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini090908-01.dmp
Crash Time : 9/9/2008 1:42:33 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000005
Parameter 2 : 0x893300e0
Parameter 3 : 0x80862835
Parameter 4 : 0x88eae6c8
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+ecc3
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
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini090908-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

btw thanks so much for helping!

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,723 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:25 AM

Posted 10 March 2010 - 10:23 AM

I would suggest that you stop using the Uniblue product.

The Memory-Optimization Hoax - http://windowsitpro.com/article/articleid/...ation-hoax.html

Registry cleaner - Wikipedia, the free encyclopedia - http://en.wikipedia.org/wiki/Registry_cleaner. See Disadvantages.

Should I Use A Registry Cleaner - http://aumha.net/viewtopic.php?t=28099

You seem to have a variety of driver problems and STOP errors...which, IMO, may indicate either file system or hard drive problems...or something more serious with hardware. (Statement was made before I realized that some of these errors are pretty old).

Bug Check Code/STOP error 0x00000077: A page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection.

0x00008086: Seems to point to hard drive/file system problems. I would try to run chkdsk /r on the partition/drive. Iastor.sys is the driver for onboard Intel SATA support, it allows hard drives and other peripherals attached to an Intel motherboard via the SATA controller to work.

Some suggest that this could be a BIOS setting problem involving the AHCI setting.

0x10000050: Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems. One of your errors points at video drivers.

0x1000007e: Numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Your error points to atikvmag.dll, which appears to be an ATI/video driver file, provided you have an ATI chipset or card.

0x000000ea: A device driver problem has caused the system to pause indefinitely (hang). Typically, this is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter, or a faulty video driver.

0x0000004e: This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists. Since we have other pointers indicating video driver problems...I would go with that guess, at this point.

0x1000008e: Nearly always hardware compatibility issues, which sometimes means a driver issue. In your case, both your audio and video drivers are indicated as causes.

0x000000f4: One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. Error points to ntoskrnl.exe, which may be misleading...because, IMO, ntoskrnl.exe is probably a victim of whatever stopped the system or caused ntoskrnl.exe to stop the system. My guess (nothing more) would be a hardware failure, possbly hard drive.

0x1000000a: Typically due to a bad driver, or faulty or incompatible hardware or software. Error points to hal.dll, a very necessary Windows file. My guess would be that the file is being blamed for something initiated by a different file. Typically...problems with this file result in inability to boot the system.

0x000000fe: USB driver problem.

I went through the whole list...even though some of these errors are quite old...just for purposes of information.

What system hardware changes have been made...which can be associated with either the start or termination of these errors?

As for troubleshooting...I would start with attempting to run chkdsk /r on the hard drive. If problems develop, I would move data files, then run the appropriate hard drive diagnostic. I like to know that the basic things are OK before I start on something else as a suspect.

If the hard drive passes, I'd move on to video drivers (uninstall, then reinstall).

Louis

#5 KINGLERMAN

KINGLERMAN
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:25 PM

Posted 15 March 2010 - 02:02 AM

Sorry for leaving this a few days, i was outside the city due to potential political problems in my country and didn't have internet access.

I did chkdsk /f im not sure if it worked properly, it only came up for a second then said the disk was clean and ended... When I do /f /r it takes way longer and generally finds a few things to fix.

I reinstalled my video driver and haven't had the issue come up, but instead have just had videos and games simply freeze and the sound which is playing keeps jumping over and over again. This was happening before but not as often as the blue screen.

#6 joseibarra

joseibarra

  • Members
  • 1,180 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:09:25 AM

Posted 15 March 2010 - 05:30 AM

The crashes you sent are old and I don't remember how many you can do with BlueScreenView, so I would whack the old crash dumps so we only look at the ones that happen now. You could just move the old dumps someplace else, but get rid of the old ones somehow by moving or deleting them.

The folder where the crash dumps are is here:

c:\windows\minidump

If you want, just leave the last 2 or 3 most recent. We need ones that happened lately, not last year.

Delete all the .dmp files in that folder, now recreate your situation, then run BlueScreenView again. You can look a the file names and dates and they will tell you the date of the dumps. This is just to avoid confusion.

High pitched noises + games sometimes means heat (too much). Windows has crashed or is about to! Systems that are not specifically designed with games in mind can overheat because of the more intense system demands (especially video).
They were not built with games in mind, but folks put intense games on them sometimes later and expect thing to work.

If it is a particular game, what is the name and we can look it up and compare the minimal requirements against your system specs.

Sometimes there is no BSOD when things get to hot - XP just stops/crashes and you have to reboot and then it might work for a while or sometimes you can let things cool off and it will work again - for a while. If you are not playing games, things are fine - for a while.

Have you started playing any newer game lately since the crashes? Any of that sound familiar? Are games a new thing for you? How are things when your system has been switched ff for a while?

Desktop or laptop (we'll find out shortly). Have you done any dust hygiene on it lately/ever to be sure it is sufficiently ventilated?

Have any hardware oriented changes been made to the system since it worked? RAM, video card, storage (hard disks, USB devices), hardware drivers, device drivers?

Disable Automatic restart on system error to stop the error on your screen so you can see it:

Right click My Computer, Properties, Advanced, Startup and Recovery Settings.

In the System failure section, untick the Automatically restart box, OK, OK.

Here are some BSOD blue screen of death examples showing information you need to provide:

http://www.codinghorror.com/blog/images/Windows_XP_BSOD.png
http://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpg

Send the information pointed to with the red arrows (3-4 lines total). Skip the boring text unless it looks important to you. We know what a BSOD looks like, we need to know the other information that is specific to your BSOD.

Then it would be good to catch a BSOD when it happens and find out the information on the screen, it sill be the same as BSV, but you can learn how to configure your system to do this anyway (what if there was no BSV program!).

Provide system information:

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste back here.

There would be some personal information (like System Name and User Name) or whatever appears to be only your business that you can delete from the paste.

For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information.

Run a test of your RAM with memtest86+ (I know it is boring and will cost you a CD).

Memtest86+ is a more up to date version of the old memtest program and they are not the same.

The memtest86+ will not run under Windows, so you will need to download the ISO file and create a bootable CD, boot on that and then run the memtest86+ program.

If even a single error is reported that is a failure and should make you suspicious of your RAM.

If you have multiple sticks of RAM you may need to run the test on them one at a time and change them out to isolate the failure to a particular single stick. Always keep at least the first bank of RAM occupied so the test will find something to do and there is enough to boot your system.

Sometimes, reseating the RAM in the slots will relieve the error but any failure is still cause for suspicion.

The file and instructions are here:

http://www.memtest.org/

If you schedule chkdsk to run on the next reboot you need to be sure it does run properly (not just think it ran properly), you will not be able to see a log of the results, but the results will be in the Event Log:

When chkdsk runs automatically on a reboot, the results are saved in the Event Viewer Application log.

To see the Event Viewer logs, click Start, Settings, Control Panel, Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box enter:

%SystemRoot%\system32\eventvwr.msc

Click OK to launch the Event Viewer.

Look in the Application log for an event sourced by Winlogon, something like:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Description:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

39070048 KB total disk space.
25151976 KB in 78653 files.
48256 KB in 10264 indexes.
0 KB in bad sectors.
237080 KB in use by the system.
65536 KB occupied by the log file.
13632736 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
3408184 allocation units available on disk.

Windows has finished checking your disk.
Please wait while your computer restarts.

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#7 hamluis

hamluis

    Moderator


  • Moderator
  • 55,723 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:25 AM

Posted 15 March 2010 - 10:01 AM

Did you actually uninstall the old video drivers...before reinstalling same?

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users