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 on vista


  • Please log in to reply
14 replies to this topic

#1 Thor2911

Thor2911

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 07 August 2011 - 09:40 AM

I've been getting the BSOD at several different time when mostly using the internet. I have several minidump files but do not know how to read them. I will attach the most recent to this post an maybe someone could take a look. Thank you for your help in advance. :thumbup2:

Attached Files



BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 07 August 2011 - 10:04 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 07 August 2011 - 02:32 PM

==================================================
Dump File : Mini080711-01.dmp
Crash Time : 8/7/2011 12:25:30 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001904aa
Parameter 2 : 0x8cb4ba08
Parameter 3 : 0x8cb4b704
Parameter 4 : 0x82ef582a
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+19fff
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+cdb3f
Stack Address 1 : Ntfs.sys+19fff
Stack Address 2 : Ntfs.sys+a4a6f
Stack Address 3 : ntkrnlpa.exe+a5e22
Computer Name :
Full Path : C:\Windows\Minidump\Mini080711-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 149,472
==================================================

==================================================
Dump File : Mini080511-01.dmp
Crash Time : 8/5/2011 11:08:08 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82f07010
Parameter 3 : 0x99381b24
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+ee010
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+ee010
Stack Address 1 : ntkrnlpa.exe+22fd80
Stack Address 2 : ntkrnlpa.exe+22fc3a
Stack Address 3 : ntkrnlpa.exe+1f6291
Computer Name :
Full Path : C:\Windows\Minidump\Mini080511-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 149,904
==================================================

==================================================
Dump File : Mini080411-01.dmp
Crash Time : 8/4/2011 10:55:42 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0x84436f30
Parameter 3 : 0x84436f30
Parameter 4 : 0x18000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+770c
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+cdb3f
Stack Address 1 : ntkrnlpa.exe+ed184
Stack Address 2 : ntkrnlpa.exe+a7332
Stack Address 3 : Ntfs.sys+1122f
Computer Name :
Full Path : C:\Windows\Minidump\Mini080411-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 150,352
==================================================

==================================================
Dump File : Mini073111-02.dmp
Crash Time : 7/31/2011 6:04:01 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 0x00056349
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82f29010
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4dfd9
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+4dfd9
Stack Address 1 : ntkrnlpa.exe+ee010
Stack Address 2 : CLASSPNP.SYS+6d9c
Stack Address 3 : CLASSPNP.SYS+147a7
Computer Name :
Full Path : C:\Windows\Minidump\Mini073111-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 146,400
==================================================

==================================================
Dump File : Mini073111-01.dmp
Crash Time : 7/31/2011 10:52:05 AM
Bug Check String : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code : 0x000000be
Parameter 1 : 0xd6c42000
Parameter 2 : 0x4097b1d9
Parameter 3 : 0x999d87fc
Parameter 4 : 0x0000000b
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+a0e2d
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+98379
Stack Address 1 : ntkrnlpa.exe+4ddd4
Stack Address 2 : ntkrnlpa.exe+a9073
Stack Address 3 : ntkrnlpa.exe+5ad78
Computer Name :
Full Path : C:\Windows\Minidump\Mini073111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 148,888
==================================================

==================================================
Dump File : Mini072411-01.dmp
Crash Time : 7/24/2011 4:28:05 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82f21010
Parameter 3 : 0xbd186aa4
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+ee010
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+ee010
Stack Address 1 : ntkrnlpa.exe+231d13
Stack Address 2 : ntkrnlpa.exe+22da9c
Stack Address 3 : ntkrnlpa.exe+23b034
Computer Name :
Full Path : C:\Windows\Minidump\Mini072411-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 149,320
==================================================

#4 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 07 August 2011 - 02:36 PM

Those are all different errors and could mean any number of things. Could be malware, a bad motherboard, bad ram, or some other problem(s). Let's do some basic troubleshooting:

1) To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

2) To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

3) Please open device manager - any yellow or red symbols?

#5 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 07 August 2011 - 02:51 PM

I have no yellow or red symbols in the device manager. I have a mem test built into the board is it ok to run that instead of the other one?

#6 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 07 August 2011 - 02:56 PM

sure

#7 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 07 August 2011 - 09:31 PM

I ran Mem checker 1.2 (onboard checker) and it showed ok. I did run chkdsk /r and it did find one bad sector that it moved. I can't find the chkdsk log to post though.

#8 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 07 August 2011 - 09:34 PM

I found the log for chkdsk here it is.

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. 614080 file records processed. 1468 large file records processed. 0 bad file records processed. 2 EA records processed. 74 reparse records processed. 703696 index entries processed. 0 unindexed files processed. 614080 security descriptors processed. Cleaning up 8644 unused index entries from index $SII of file 0x9. Cleaning up 8644 unused index entries from index $SDH of file 0x9. Cleaning up 8644 unused security descriptors. CHKDSK is compacting the security descriptor stream... 44809 data files processed. CHKDSK is verifying Usn Journal... 134565672 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc000009c at offset 0xaad000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xaba000 for 0x1000 bytes. Windows replaced bad clusters in file 24214 of name \Windows\winsxs\X8AF34~1.180\519CC5~1.SYS. 614064 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 21753336 free clusters processed. Free space verification is complete. Adding 1 bad clusters to the Bad Clusters File. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 488384511 KB total disk space. 400265680 KB in 529645 files. 272796 KB in 44812 indexes. 4 KB in bad sectors. 832683 KB in use by the system. 65536 KB occupied by the log file. 87013348 KB available on disk. 4096 bytes in each allocation unit. 122096127 total allocation units on disk. 21753337 allocation units available on disk.

#9 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 08 August 2011 - 06:57 AM

Okay, well let's see what happens.

#10 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 08 August 2011 - 08:35 AM

So you think that would be enough to cause the BSOD. I ran Superantimalware and Malwarebytes and it only found 4 tracking cookies so no major bugs that way. Hopefully, this will take care of the problem. :thumbup2:

#11 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 08 August 2011 - 08:58 AM

I have no idea. As I said, let's see.... :)

And btw, neither of the apps you mentioned is an anti virus application.

Edited by Allan, 08 August 2011 - 08:59 AM.


#12 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 08 August 2011 - 10:32 AM

Nope, they are malware removers. I have Avast! v 6.0.1203 with virus definitions v 110808-0 for my antivirus. I switched from AVG. Seems to work ok.

#13 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 08 August 2011 - 10:40 AM

Okay, good :)

#14 Thor2911

Thor2911
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:10:40 PM

Posted 10 August 2011 - 09:23 AM

So far so good. No BSOD. My son had it happen on his PC and I ran CHKDSK on it and it had some issues that it corrected. Thanks for telling me about the blue screen reader that will help in the future. Thanks for your help! I will post on here again if it happens in the next week or so.

#15 Allan

Allan

  • BC Advisor
  • 8,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:40 PM

Posted 10 August 2011 - 01:06 PM

You're welcome and good luck :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users