Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

3 bsod error codes


  • Please log in to reply

#1
brandonhinsz

brandonhinsz

    Member

  • Member
  • PipPip
  • 26 posts
Howdey all - Been haveing some issues with my current build. Have had this thing for a little over a year and never had any problems. Recently the machine would throw BSOD and shut down, the first was X0A - followed the instructions from this site to repair and was not able to fix it, so i sent all of my crucial data to a usb external. about 200 gigs worth of crap. It transfered over fine, and I re formated and reinstalled xp without an issue. Installed mobo drivers off of disk, then went to the website to update. This went off fine. Installed msi 8800 gt vid card and this went fine. No issues at all untill I tried copying my stuff back over. I would get about 8 gigs in and hit the bsod again, mainly x0a, but also have seen 0x24 and 0x50. I have removed the vid card, and reinstalled the driver for the onboard vid, ran memtest on the ram 10 times no errors.

I have gotten to the point several times where windows will not restart at all untill I run the repair option and chkdsk /r. Will be runing chkdsk /f tonight, I have also removed the ram chips one at a time and gotten bsod on both.

I have windbg files ready to email if anyone would like to check them. Any ideas would be greatly appreciated.

Thank you - Brian
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello brandonhinsz.... Welcome to GeeksToGo, :) :) :)

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
Please understand we are all volunteers and we are not here all the time. Sometimes it may be a extended amount of time to get back to you. If it has been more then 3 days please shoot me a PM and I will try to get back to you quickly then.


Please do the following so we can get a more accurate ideal of the BSOD's you are experiencing.

BSOD in safe mode:
Right click MY COMPUTER and then PROPERTIES
Click ADVANCED and then click the SETTINGS button In the Startup And RECOVERY section
Uncheck AUTOMATICALLY RESTART. Click APPLY and OK.
Now reboot. This will result in the BSOD error being halted so you can now copy and reply with the STOP ERROR and any parameters.
  • 0

#3
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
give us your system specs too...
  • 0

#4
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
hello there - I completely understand the time issues as real life has to take precedence over the internet.

I have already unchecked the box described and can copy the error codes down when they come in - most recently this morning it was 0x50, and windows is currently runing chkdsk as i asked it to by right clicking the c drive etc...

hardware specs - intel dg33tl mobo, intel e6750 core 2 duo proc, 2 g ddr2800 corsair ballistix tracer, msi 8800 gt vid card ( currently not installed since it is a periphrial ) wd 7200 rpm hd either 320 g or 500 g i cant remember. should only have around 160 to 200 g used. anything else ?
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
We need more then 0x50
There should be a entire description of error code and message stating what the error is related to.
  • 0

#6
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
this particular one was a page fault error - the 0xa error was irq not equal or less than - i forget what the 0x24 was.

Should I post the minidump files so that you can see them ?

I will copy down the whole code the next time it shows up.

another one I have seen is "unmountable boot volume" 0x000000ed (0x8a3559e0, 0x0000032, 0x00000000,0x00000000)

I just remembered I shot a video of the error code a few days ago - here is the 0xa code. IRQL not less or equal - 0x0000000a (0xc0a06001, 0x00000002, 0x00000001, 0x806e6a2a)
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

#8
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
here ya go.


--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sun 9/13/2009 10:10:28 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xFF55550F, 0x0, 0x80526653, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 9/13/2009 5:20:59 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFF801F, 0x2, 0x0, 0x805153EB)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 9/12/2009 10:40:12 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xB84E7AAC, 0xB84E77A8, 0xB7E74487)
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
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 9/12/2009 10:37:59 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x8DE75B00, 0x2, 0x0, 0x805153E9)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 9/12/2009 8:10:11 AM your computer crashed
This was likely caused by the following module: sr.sys
Bugcheck code: 0x1000000A (0x0, 0x2, 0x0, 0x8051BB93)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Restore Filesystem Filter Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 9/11/2009 10:00:58 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xC28B0A98, 0x2, 0x1, 0x8051AE21)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 9/11/2009 9:59:28 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x99925AB0, 0x2, 0x0, 0x805153E9)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 7:42:18 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1000000A (0xC0A06001, 0x2, 0x1, 0x806E6A2A)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 7:29:58 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF828B2F, 0xB4574BDC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 7:27:47 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0xE0DD4288, 0x1, 0xB7E592DA, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 12:22:06 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41284, 0x2ED3001, 0x5682, 0xC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 12:13:44 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x10000050 (0x80E0E870, 0x0, 0x804F4CFA, 0x2)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 11:52:49 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x780, 0xC06B0BA0, 0x81DBB400, 0x4C0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 9/10/2009 2:30:21 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x2888050, 0x2, 0x1, 0x805172D6)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 9/9/2009 3:21:28 AM your computer crashed
This was likely caused by the following module: netbt.sys
Bugcheck code: 0x1000000A (0xE838A829, 0x2, 0x0, 0x804EF78E)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\netbt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MBT Transport driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 9/8/2009 9:45:44 AM your computer crashed
This was likely caused by the following module: sr.sys
Bugcheck code: 0x1A (0x780, 0xC06A8938, 0x81F2D130, 0x4C0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Restore Filesystem Filter Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 9/8/2009 4:56:37 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x99C25250, 0x2, 0x0, 0x805153E9)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

17 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#9
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
should I run memtest with only 1 ram and test them both that way ?
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
If they passed together ther eshould be no issue but you can go ahead and try it.
I see in your WhoCrashed log that all your crashes are due to the OS itself. Let's try to xheck and repair and system files that may be corrupt or damaged by doing the following.

Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions
  • 0

Advertisements


#11
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
ok - i went through that and it did ask for the disk. I assume there was something missing.

Should I try to make it bsod again or is there another way to see if it is repaired ?

Thank you for the help - Brian
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
If it asked for the disk and you had the disk it should hopefully had fixed the issue.
Are you saying you don't have the XP disk?
  • 0

#13
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
naw i have it and put it in and all that - but that almost seems too easy of a fix for the two weeks of trying to repair it that i just went through :) will stress the system tonight and see if i cant get it to happen again. If it doesent then thank you very much for the help.
  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Also I would advise you go thru the malware techs and check out your system and the backup files to make sure everything is clean.
After testing the system then:
I suggest you go to the Malware Removal and Spyware Removal Forum and run all the steps located in the START HERE. These self-help tools will help you clean up 70% of problems on your own. If you are still having problems after doing the steps, then please post the reguested logs in THAT forum. If you are unable to run any of the tools then start a new topic in the malware forum and put this in the subject line...I am unable to run any malware tools

If you are still having problems after being given a clean bill of health from the malware expert, then please return to THIS thread and we will pursue other options to help you solve your current problem(s).
  • 0

#15
brandonhinsz

brandonhinsz

    Member

  • Topic Starter
  • Member
  • PipPip
  • 26 posts
right on - thanks again.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP