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

Stubborn Computer BSODs and reformatting.


  • Please log in to reply
33 replies to this topic

#1 Peregrina

Peregrina

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 04:15 AM

I've been building a desktop at home and it seems the BSODs just never stop coming. as soon as I fix one a new one appears. I'm considering reformatting to see if that does anything. Any ideas on that? Will it help? this is the most recent BSOD:

==================================================
Dump File : 100610-22198-01.dmp
Crash Time : 10/6/2010 5:08:40 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`07ed50c8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`10d7c25e
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100610-22198-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

Happened while browsing the internet.
Posted Image

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:31 PM

Posted 06 October 2010 - 08:04 AM

Please perform the following, so that we can get the exact specs of your computer. This will better assist us in helping you more.

Publish a Snapshot using Speccy

The below is for those who cannot get online

Please take caution when attaching a text file to your post if you cannot copy/paste the link to your post, you will need to edit it to make sure that your Windows Key is not present.

#3 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 12:39 PM

http://speccy.piriform.com/results/lvZJLbBlT5NH5KGcI2XZUDs
Posted Image

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:31 PM

Posted 06 October 2010 - 12:55 PM

Is this the only time that it has blue screened on you, or are there multiple times?

#5 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 01:28 PM

Multiple times for many different reasons. I've corrected some of them but like I mentioned before, there always seems to be another problem.
If you'd like to see the extent of different types of BSODs I'm dealing with here are all of the recent types the most common being SYSTEM_SERVICE_EXCEPTION

==================================================
Dump File : 100310-30404-01.dmp
Crash Time : 10/3/2010 12:45:14 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`049fe988
Parameter 3 : fffff880`049fe1f0
Parameter 4 : fffff800`02ca38e4
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+213d8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100310-30404-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 091510-43383-01.dmp
Crash Time : 9/15/2010 11:01:31 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00027694
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\091510-43383-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 100610-22198-01.dmp
Crash Time : 10/6/2010 5:08:40 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`07ed50c8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`10d7c25e
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100610-22198-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 100610-25194-01.dmp
Crash Time : 10/6/2010 8:53:12 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`0001ecd9
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`0001dd96
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100610-25194-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 092610-21325-01.dmp
Crash Time : 9/26/2010 9:29:19 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0441257b
Parameter 3 : fffff880`09e8fc50
Parameter 4 : 00000000`00000000
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+1257b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\092610-21325-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 100610-22276-01.dmp
Crash Time : 10/6/2010 1:33:59 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff880`06568000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff880`06568000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100610-22276-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 100210-23587-01.dmp
Crash Time : 10/2/2010 11:57:31 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02ce68e4
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100210-23587-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

Edited by Peregrina, 06 October 2010 - 01:29 PM.

Posted Image

#6 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:31 PM

Posted 06 October 2010 - 01:32 PM

Have you made sure that all your drivers are updated?

I see one dealing with USBPORT.sys.

If you have done that, then I would like for you to do the following:


How to Test your RAM



Guide Overview

The purpose of this guide is to teach you how to check whether your system's RAM (Ramdom Access Memory) is working properly. Bad RAM can lead to a whole host of problems, often which do not appear to have a single cause -- appearing as systemwide glitches, blue screens, and other system trouble. MemTest86+ provides a very good detection mechanism for failed RAM, and is about as good a test you get short of actually replacing the module itself.

Tools Needed
Please perform these steps from a separate, working, machine.Perform these steps on the problem machine.
  • Put your CD in the drive and configure your machine to boot to the CD. This is different on all machines, but it's usually by pressing F12 or F10 as your system boots, and selecting either "CDROM" or your cdrom drive. If you are unable to force a CDRom boot, reply with the make and model of your machine and I should be able to get you exact instructions.
  • If you've done it correctly, MemTest86+ will start to run automaticly, as shown below:
    Posted Image
  • If you want to be reasonably your RAM is OK, then allow MemTest to run until you see this message:
    Posted Image

    On the other hand, if you want to be completely sure your RAM is OK, allow MemTest to run overnight. Memtest will run forever until power is pulled on the machine.
  • Check the MemTest screen for any reported errors. Errors will appear as RED warnings at the bottom of the screen, similar to the following screenshot:
    Posted Image
  • Hard-Reset the machine, removing the MemTest disk in the process.
If you didn't get an error screen, Congratulations! :huh:

#7 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 01:37 PM

Naturally, having so many problems I check my driver's regularly but I'll double check the USBPORT.sys deal.

I've run memtest86 on my RAM twice before letting it run for a good 4 hours with no errors. I'll do it over night, though I guess.

Edited by Peregrina, 06 October 2010 - 01:41 PM.

Posted Image

#8 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:31 PM

Posted 06 October 2010 - 01:40 PM

Do the driver updates first, also what USB Devices do you have installed on this computer? They maybe incompatible with Windows 7.

#9 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 01:42 PM

I have a Razer Mamba and a Logitech G15 keyboard as my only two USB devices.
Posted Image

#10 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 01:45 PM

I used Driver Wiz (I don't know if you would recommend using it or not) and it actually found 11 drivers out of date. I'll see to them right now.
Posted Image

#11 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:31 PM

Posted 06 October 2010 - 01:47 PM

Driver for your G15 Keyboard

Drivers and Firmware for your Razer Mamba Mouse

#12 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 06 October 2010 - 01:58 PM

Driver for your G15 Keyboard

Drivers and Firmware for your Razer Mamba Mouse


Thanks for the quick links, they're updated now. Should I just sit for now and see what happens and report back the next blue screen?
Posted Image

#13 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:31 PM

Posted 06 October 2010 - 01:59 PM

Yeah see if the bsod's persist and if they do post back give it a good 48 hours.

#14 hamluis

hamluis

    Moderator


  • Moderator
  • 55,746 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:31 PM

Posted 07 October 2010 - 03:14 PM

That STOP 24 error points (probably) at your hard drive or the file system (which may again point to the hard drive). All of the others could be the result of a bad hard drive or file system, IMO.

Louis

#15 Peregrina

Peregrina
  • Topic Starter

  • Members
  • 61 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Columbus, Ohio
  • Local time:01:31 PM

Posted 08 October 2010 - 09:27 PM

That STOP 24 error points (probably) at your hard drive or the file system (which may again point to the hard drive). All of the others could be the result of a bad hard drive or file system, IMO.

Louis


Thanks for the input!

Well throughout the two days I had three blue screens and once it froze up without blue screening.

Here are the three that showed up:

==================================================
Dump File : 100810-27300-01.dmp
Crash Time : 10/8/2010 2:04:11 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff960`002eb7e3
Parameter 3 : fffff880`0924d170
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1fb7e3
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100810-27300-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 100810-31683-01.dmp
Crash Time : 10/8/2010 12:16:47 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`02000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`045c49d2
Caused By Driver : afd.sys
Caused By Address : afd.sys+629d2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100810-31683-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 100710-34039-01.dmp
Crash Time : 10/7/2010 12:22:05 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`02000001
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`02d63b73
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+7ace4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\100710-34039-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
This last one looks like a videocard driver issue, but I know I updated the video card driver when I first posted.

Edited by Peregrina, 08 October 2010 - 09:31 PM.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users