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

Need Help With BSODs


  • Please log in to reply
20 replies to this topic

#1 muskyj

muskyj

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 23 February 2012 - 06:09 AM

Mod Edit: Split from http://www.bleepingcomputer.com/forums/topic443512.html ~ Hamluis.

hi there
I hope it's OK to post here, I didn't want to create a new thread as this thread seemed appropriate.

I keep having blue screen reboots and have some of the logs below (been having this fault for a couple of months now!).
I tried system recovery but the problem persists. the funny thing is that the computer boots as normal and works normally every now and then, but when I shut down and try to reboot it goes into the same old cycle of rebooting. I have run a couple of antivirus software checks but no virus found.
any help much appreciated.



Mini022012-13.dmp
20/02/2012 22:51:13
UNEXPECTED_KERNEL_MODE_TRAP
0x1000007f
0x00000008
0x80042000
0x00000000
0x00000000
win32k.sys
win32k.sys+13a3c
Multi-User Win32 Driver Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+13a3c
win32k.sys+13abc
win32k.sys+13c79
win32k.sys+36ea1
C:\WINDOWS\Minidump\Mini022012-13.dmp
1
15
2600
90,112


Mini022012-12.dmp
20/02/2012 22:50:14
PAGE_FAULT_IN_NONPAGED_AREA
0x10000050
0xe2c22e54
0x00000000
0xbf808b4d
0x00000001
win32k.sys
win32k.sys+8b4d
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+8b4d win32k.sys+2979c
ntoskrnl.exe+666d8
C:\WINDOWS\Minidump\Mini022012-12.dmp
1
15
2600
90,112


Mini022012-11.dmp
20/02/2012 22:49:26
UNEXPECTED_KERNEL_MODE_TRAP
0x1000007f
0x00000008
0x80042000
0x00000000
0x00000000
win32k.sys
win32k.sys+13a3c
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit win32k.sys+13a3c
win32k.sys+13abc
win32k.sys+13c79
ntoskrnl.exe+666d8
C:\WINDOWS\Minidump\Mini022012-11.dmp
1
15
2600
90,112


Mini022012-10.dmp
20/02/2012 22:43:24
UNEXPECTED_KERNEL_MODE_TRAP
0x1000007f
0x00000008
0x80042000
0x00000000
0x00000000
win32k.sys
win32k.sys+13a3c
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+13a3c
win32k.sys+13abc
win32k.sys+89276
win32k.sys+86bdb
C:\WINDOWS\Minidump\Mini022012-10.dmp
1
15
2600
90,112


Mini022012-09.dmp
20/02/2012 22:07:14
UNEXPECTED_KERNEL_MODE_TRAP
0x1000007f
0x00000008
0x80042000
0x00000000
0x00000000
win32k.sys
win32k.sys+13a3c
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+13a3c
win32k.sys+13abc
win32k.sys+13c79
ntoskrnl.exe+666d8
C:\WINDOWS\Minidump\Mini022012-09.dmp
1
15
2600
90,112


Mini022012-08.dmp
20/02/2012 22:04:49
UNEXPECTED_KERNEL_MODE_TRAP
0x1000007f
0x00000008
0x80042000
0x00000000
0x00000000
win32k.sys
win32k.sys+13a3c
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+13a3c
win32k.sys+13abc
win32k.sys+13c79
ntoskrnl.exe+666d8
C:\WINDOWS\Minidump\Mini022012-08.dmp
1
15
2600
90,112


Mini022012-07.dmp
20/02/2012 22:03:11
UNEXPECTED_KERNEL_MODE_TRAP
0x1000007f
0x00000008
0x80042000
0x00000000
0x00000000
win32k.sys
win32k.sys+13a3c
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+13a3c
win32k.sys+13abc
win32k.sys+13c79
ntoskrnl.exe+666d8
C:\WINDOWS\Minidump\Mini022012-07.dmp
1
15
2600
90,112

Mini022012-02.dmp
20/02/2012 20:21:37
0xc0000145
0xc0000142
0x00000000
0x00000000
0x00000000
ntoskrnl.exe
ntoskrnl.exe+21cc5
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
32-bit
ntoskrnl.exe+21cc5
ntoskrnl.exe+e617e
ntoskrnl.exe+1770a3
ntoskrnl.exe+1345c8
C:\WINDOWS\Minidump\Mini022012-02.dmp
1
15
2600
90,112

Mini021912-06.dmp
19/02/2012 18:03:32
PAGE_FAULT_IN_NONPAGED_AREA
0x10000050
0x8000003c
0x00000000
0xbf89dd20
0x00000000
win32k.sys
win32k.sys+9dd20
Multi-User Win32
Driver Microsoft® Windows® Operating System
Microsoft Corporation
5.1.2600.6188 (xpsp_sp3_gdr.120112-1716)
32-bit
win32k.sys+9dd20
win32k.sys+9de13
win32k.sys+9eeb9
win32k.sys+5303d
C:\WINDOWS\Minidump\Mini021912-06.dmp
1
15
2600
90,112

Edited by hamluis, 23 February 2012 - 08:28 AM.
PM sent new OP.


BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 23 February 2012 - 06:22 AM

@ muskyj: I will ask a Moderator to split this post off to a topic of your own.

The output from BlueScreenView in this instance is not overly helpful, so we have a good case for gathering some more information. Please do the following steps and I will have a look at the information (tomorrow) and see if I can shed some light on your BSOD issue.

:step1: Download the following 2 files and save both to the My Documents folder:

:step2: Go to the My Documents folder and run #1 (BSOD_XP_v1.3_jcgriff2_PROD_.exe). (That will also run #2.)

It will take a little time to complete: Please be patient and wait for it to finish.
A new folder named TSF_XP_Support will be created in My Documents.

:step3: Zip up the newly created TSF_XP_Support folder.
  • Right-click on the TSF_XP_Support folder > Send to ... > Compressed (zipped) Folder.
  • The newly created zip file will be located in the My Documents folder.

:step4: Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file.

Note: The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit).
See the suggestions in the following links for recommendations on file sharing websites:
  • http://lifehacker.com/388284/best-online-file-sharing-services
  • http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  • http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

:step5: Please Publish a Snapshot using Speccy, and post a link to it in this thread.
  • It is a convenient and accurate way of providing us with details of your computer specifications.

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

Posted Image

#3 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 23 February 2012 - 11:53 AM

here are the two links. appreciate the help.


http://www.mediafire.com/download.php?cq8wlq5g8gf01gg

http://speccy.piriform.com/results/0XlUUyaqNVmPYYPgP4NzSXB

#4 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 23 February 2012 - 06:46 PM

From the Speccy report ...

Disk Letter: C:
File System: NTFS
Volume Serial Number: 1C8BE7FC
Size: 69GB
Used Space: 66GB (97%)
Free Space: 2.11GB (3%)


The minimum free space that you should ever let your Windows system drive get down to is 15% (15% of 70 is 10.5 GB).
  • You should aim to keep at least 25% free space (25% of 70 is 17.5 GB).
The first thing you need to do is delete any unnecessary personal files and transfer at least 10 GB of your personal files (such as music and video) to another internal hard drive or to an external USB hard drive or flashdrive. Run CCleaner to get rid of some unnecessary junk (but do not use the registry cleaner part of CCleaner). Let's see what problems you have remaining after doing that.

The crash dumps do not provide anything much that may be useful indicators as to the cause of the problem.

If you wish later on, there are quite a few other things that can be also be tidied up, which may help make the system a bit faster too. There are startup items that are no longer valid (files missing), remnants of at least 2 previously installed antivirus programs that can be removed and the system drive can be defragmented.

Edited by AustrAlien, 23 February 2012 - 06:49 PM.

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

Posted Image

#5 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 25 February 2012 - 03:36 PM

thanks for having a look anyway.

I have freed up some badly needed space and defragmented the drive.

could this still be a virus problem do you think? or could it be some hardware failure like the ram?

#6 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 25 February 2012 - 03:44 PM

How much free space do you have on the system drive now?

What problems do you have after freeing up some disk space?

Is the system still crashing?
Zip up the minidumps and attach to a post.

Is the system still having problems starting normally after shutting it down normally?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 25 February 2012 - 04:42 PM

started computer after freeing up space 26% free space now.
computer started OK but crashed a few minutes in. then went through a cycle of trying to start-up but continuous rebooting.
eventually it started OK and is still running OK at the moment.

http://www.mediafire.com/download.php?bcdbs3sn8m6q5dn

#8 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 26 February 2012 - 04:57 AM

could this still be a virus problem do you think? or could it be some hardware failure like the ram?

I'm still working on that .... both are possibilities, but seem to be unlikely. For now, I think we are most likely looking for a device driver problem, so let's try the following and see what happens ...

Run Driver Verifier following the instructions DRIVER VERIFIER - Windows 7 & Vista ... by jcgriff2
  • Notes:
  • There are a few minor differences for XP, but the steps are essentially the same.
    • You will notice that a couple of the options are not available when manually configuring Driver Verifier in XP.
  • Do not omit the first step, to create a System Restore point before enabling Driver Verifier.
  • Read the instructions on how to check the Driver Verifier Status.
  • Read the instructions on how To Turn Driver Verifier OFF when you have finished with it.
  • Read the instructions (and record them on paper so you have them if needed) about what to do IF you cannot start the system normally after it crashes under Driver Verifier.
  • Run Driver Verifier for 36 hours unless the system crashes. It doesn't matter whether you are using the computer or not during that time.
If your system BSOD’s under the Driver Verifier
  • Locate the dump file:
    • C:\Windows\minidump <<< folder
  • Zip up the most recent minidump file:
    • Right-click on the most recent minidump file > Send to ... > Compressed (zipped) Folder.
    • The zip file will be located in the same place
  • Attach the zip file to your next post in this thread.
    • When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message

Edited by AustrAlien, 26 February 2012 - 05:00 AM.

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

Posted Image

#9 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 27 February 2012 - 02:03 PM

ok it crashed while driver verifier was running at least once. minidumps attached.

Attached File  Mini022712-01.zip   20.58KB   7 downloads
Attached File  Mini022712-02.zip   21.15KB   3 downloads

#10 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 27 February 2012 - 02:08 PM

sorry, meant to add that the first minidump was after the crash. the second appeared after the internet crashed on me while i was trying to upload the first. thought i would add it anyway.

#11 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 27 February 2012 - 09:00 PM

Neither of the two most recent crashes were flagged by Driver Verifier, so are of little benefit.

I might have bee wrong in choosing to go straight to Driver Verifier.
Let's get back to basics and see if you can run memtest86+ for 24 hours without an error.
  • Please allow memtest86+ to run for 24 hours unless you see an error beforehand.

Test the memory (RAM).

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.
Reference: Overclockers forums Memtest86+ Guide/How To's
http://www.overclockers.com/forums/showthread.php?t=409152

===============================
BSOD BUGCHECK SUMMARY: 2 minidumps on 27th February
...............................................................
Loading Dump File [C:\CactusIsland\muskyj_BC\Mini022712-01\Mini022712-01.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Tue Feb 28 04:50:02.031 2012 (UTC + 11:00)
System Uptime: 1 days 5:28:54.206
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
Could not read faulting driver name
Probably caused by : avgntflt.sys ( avgntflt+bcfc )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: avgnt.exe
FAILURE_BUCKET_ID: 0x50_avgntflt+bcfc
Bugcheck code 10000050
Arguments ffffffef 00000000 84c37057 00000000
BiosVersion = 3.07
BiosReleaseDate = 01/27/2006
SystemManufacturer = Compaq Presario 061
BaseBoardManufacturer = Hewleet-Packard
BaseBoardProduct = Asterope
BaseBoardVersion = 1.0
CPUID: " Intel® Celeron® CPU 3.06GHz"
MaxSpeed: 3060
CurrentSpeed: 3065
...............................................................
Loading Dump File [C:\CactusIsland\muskyj_BC\Mini022712-02\Mini022712-02.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Tue Feb 28 05:52:01.938 2012 (UTC + 11:00)
System Uptime: 0 days 0:24:59.384
Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+55 )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+55
Bugcheck code 1000000A
Arguments 94984008 00000002 00000001 8051f78f
BiosVersion = 3.07
BiosReleaseDate = 01/27/2006
SystemManufacturer = Compaq Presario 061
BaseBoardManufacturer = Hewleet-Packard
BaseBoardProduct = Asterope
BaseBoardVersion = 1.0
CPUID: " Intel® Celeron® CPU 3.06GHz"
MaxSpeed: 3060
CurrentSpeed: 3064
...............................................................


====================================
BSOD BUGCHECK SUMMARY
...............................................................
Loading Dump File [C:\CactusIsland\muskyj _BC\TSF_XP_Support\Mini022012-13.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Tue Feb 21 09:50:27.750 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:38.339
Probably caused by : win32k.sys ( win32k!WatchdogDrvCreateDeviceBitmap+66 )
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: explorer.exe
FAILURE_BUCKET_ID: 0x7f_8_win32k!WatchdogDrvCreateDeviceBitmap+66
Bugcheck code 1000007F
Arguments 00000008 80042000 00000000 00000000
BiosVersion = 3.07
BiosReleaseDate = 01/27/2006
SystemManufacturer = Compaq Presario 061
BaseBoardManufacturer = Hewleet-Packard
BaseBoardProduct = Asterope
BaseBoardVersion = 1.0
CPUID: " Intel® Celeron® CPU 3.06GHz"
MaxSpeed: 3060
CurrentSpeed: 3065
...............................................................

***There were 16 minidumps very similar to the above one (almost identical).***
...............................................................
Loading Dump File [C:\CactusIsland\muskyj _BC\TSF_XP_Support\Mini022012-12.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Tue Feb 21 09:49:31.531 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:29.097
Could not read faulting driver name
Probably caused by : memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: logonui.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 10000050
Arguments e2c22e54 00000000 bf808b4d 00000001
...............................................................
Loading Dump File [C:\CactusIsland\muskyj _BC\TSF_XP_Support\Mini022012-02.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Tue Feb 21 07:20:55.781 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:33.359
Probably caused by : ntkrnlpa.exe ( nt!KiFastCallEntry+f8 )
Unknown bugcheck code (c0000145)
BUGCHECK_STR: 0xc0000145_c0000142
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: drwtsn32.exe
FAILURE_BUCKET_ID: 0xc0000145_c0000142_nt!KiFastCallEntry+f8
Bugcheck code C0000145
Arguments c0000142 00000000 00000000 00000000
...............................................................
Loading Dump File [C:\CactusIsland\muskyj_BC\TSF_XP_Support\Mini021912-06.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Mon Feb 20 04:59:43.491 2012 (UTC + 11:00)
System Uptime: 0 days 0:12:44.254
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!xxxDW_DestroyOwnedWindows+47 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: 0x50_win32k!xxxDW_DestroyOwnedWindows+47
Bugcheck code 10000050
Arguments 8000003c 00000000 bf89dd20 00000000
...............................................................
Loading Dump File [C:\CactusIsland\muskyj_BC\TSF_XP_Support\Mini021912-03.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Mon Feb 20 04:44:30.890 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:23.457
Unable to load image ati2dvag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
Could not read faulting driver name
Probably caused by : ati2dvag.dll ( ati2dvag+102d1 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: 0x50_ati2dvag+102d1
Bugcheck code 10000050
Arguments 868bfffb 00000008 868bfffb 00000000
...............................................................
Loading Dump File [C:\CactusIsland\muskyj_BC\TSF_XP_Support\Mini021912-02.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Mon Feb 20 04:40:54.921 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:22.511
Unable to load image ati2dvag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
Could not read faulting driver name
Probably caused by : ati2dvag.dll ( ati2dvag+102d1 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: 0x50_ati2dvag+102d1
Bugcheck code 10000050
Arguments 868bfffb 00000008 868bfffb 00000000
...............................................................
Loading Dump File [C:\CactusIsland\muskyj _BC\TSF_XP_Support\Mini021812-01.dmp]
Built by: 2600.xpsp_sp3_gdr.111025-1629
Debug session time: Sun Feb 19 06:44:16.296 2012 (UTC + 11:00)
System Uptime: 0 days 0:00:25.867
Probably caused by : ntkrnlpa.exe ( nt!KiTrap0E+cc )
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: 0xFC_nt!KiTrap0E+cc
Bugcheck code 000000FC
Arguments f6f6ed64 10180163 f6f6ecec 00000001
BiosVersion = 3.07
BiosReleaseDate = 01/27/2006
SystemManufacturer = Compaq Presario 061
BaseBoardManufacturer = Hewleet-Packard
BaseBoardProduct = Asterope
BaseBoardVersion = 1.0
CPUID: " Intel® Celeron® CPU 3.06GHz"
MaxSpeed: 3060
CurrentSpeed: 3065
...............................................................

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

Posted Image

#12 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 29 February 2012 - 04:21 PM

ok i followed your procedure and ran memtest for just a bit over 24 hours. it was showing 75 passes and zero errors.

#13 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 01 March 2012 - 01:49 AM

That's good to rule out memory as a possible issue here.
----------------

The two Event logs previously collected by the jcgriff2 application are corrupt.

Please gather the info by the following means, and upload it for my review.

:exclame: Create a new folder on your Desktop, and name it EventLogs.

:step1: Event logs
  • Go to Start > Run and type eventvwr.msc and press <ENTER>
  • When the Event Viewer window has opened, on the left side, click on System.
  • On the top main menu bar, click Action > Save Log File As ...
  • Enter system as the "File Name" and choose the EventLogs folder on your Desktop as the "Location" to save it.
    (Leave the "Save as type:" as the default setting of "Event Log (*.evt)").
  • Click Save.
Do the same for the Application log:
  • On the left side, click on Application.
  • On the top main menu bar, click Action > Save Log File As ...
  • Enter application as the "File Name" and choose the EventLogs folder on your Desktop as the "Location" to save it.
    (Leave the "Save as type:" as the default setting of "Event Log (*.evt)").
  • Click Save.
Close the Event Viewer window.


:step2: At your Desktop, zip up the EventLogs folder
  • Right-click on the folder > Send to ... > Compressed (zipped) Folder.
.
and attach the zip file to your next post in this thread.
  • When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.
Note: The BC forums will allow a total attachment size of only 512 kb and what you need to attach may exceed this limit. In that case, please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file.

See the suggestions in the following links for recommendations on file sharing websites:
  • http://lifehacker.com/388284/best-online-file-sharing-services
  • http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  • http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html
=============
Note: If your Event logs are corrupt try fixing them by the following means ...
Fix Corrupt Event Log Files
http://technet.microsoft.com/en-us/library/bb457024.aspx

Edited by AustrAlien, 01 March 2012 - 01:51 AM.

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

Posted Image

#14 muskyj

muskyj
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:12:39 AM

Posted 01 March 2012 - 05:16 PM

the files didn't seem to be corrupt so here they are.

Attached File  EventLogs.zip   85.67KB   3 downloads

Edited by muskyj, 01 March 2012 - 05:18 PM.


#15 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:39 AM

Posted 01 March 2012 - 07:38 PM

I managed to open the Event logs this time ... but upon trying to navigate through the entries, was stopped by another "event log is corrupt" message.

Let's try saving the logs as text files:
  • Start > Run and type eventvwr and press <ENTER>
  • In the left pane, click on Application to highlight it.
  • Go to Action > Save Log File As ...
  • At the top beside Save in, choose a convenient location (the Desktop) to save the file.
  • Beside File name, type in application for the name of the file.
  • Beside Save as type, use the drop-down menu to select Text (Tab delimited)(*.txt)
  • Click Save

Do the same for the System Event Log, naming the saved text file system.

At the Desktop, select both the text files that you have just created, zip them up and attach the .zip file to your reply.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users