Random BSOD errors 0x00000A/0x000001E

[essenbe]

Ibebryan, your system specs list 1 hard drive. How many hard drives/ SSDs do you have in your computer. Which ports are each connected to? A hard drive should not be making a 'grinding' noise. What brand and size of PSU do you have? Please look in bios and give me the readings of your +12V, +5V and +3.3V. If you have an SSD, is the firmware up to date? Please go into BIOS and check your sata controller and remember what it is set to. When you do that press F5. That should be the key to set everything to optimized defaults. After doing that and confirming that is what you want to do, set your ram frequency to manufactures specs as well as the timings and voltage to manufacturer's specs. Set your sata controller to what it is right now. It should be set to AHCI by default, but make sure it is set to what it is right now. Set your boot order, save an exit. If you have an SSD, make sure it is connected to port 0 or 1. If you can do without the grinding hard drive, disconnect the sata data and power cable. Check the other drives cables on both ends to make sure they are firmly seated. If you are overclocking your graphics card, set it to defaults. Also, when is the last time you did a clean install and what anti Virus are you running?

 

[Ibebryan]

Ibebryan, your system specs list 1 hard drive. How many hard drives/ SSDs do you have in your computer. Which ports are each connected to? A hard drive should not be making a 'grinding' noise. What brand and size of PSU do you have? Please look in bios and give me the readings of your +12V, +5V and +3.3V. If you have an SSD, is the firmware up to date? Please go into BIOS and check your sata controller and remember what it is set to. When you do that press F5. That should be the key to set everything to optimized defaults. After doing that and confirming that is what you want to do, set your ram frequency to manufactures specs as well as the timings and voltage to manufacturer's specs. Set your sata controller to what it is right now. It should be set to AHCI by default, but make sure it is set to what it is right now. Set your boot order, save an exit. If you have an SSD, make sure it is connected to port 0 or 1. If you can do without the grinding hard drive, disconnect the sata data and power cable. Check the other drives cables on both ends to make sure they are firmly seated. If you are overclocking your graphics card, set it to defaults. Also, when is the last time you did a clean install and what anti Virus are you running?

first off for the things i can answer now, i only have the 1tb hard drive in my computer, I clean installed windows maybe 2 weeks ago to try to stop the BSOD errors, it worked for about a day and then it started crashing again with the same errors. i updated my bios to the latest version. i use the anti virus recommended by you guys. i have already set everything to optimized default as well. Thats everything i can answer now. i will do everything else you recommended in the next couple hours and post back. thanks for the help!

 

[essenbe]

OK, thanks. I'm just trying to get everything as it should be and try to determine where your I/O errors are coming from. Your hard drive is a 1TB Western digital Green drive isn't it? They run very quiet and shouldn't be making any sounds. I'm not a BSOD analysist, but with a hard drive making grinding sounds and I/O errors, to me points to a hard drive problem. It can have other problems than bad sectors. I'm not saying to go out and buy a new hard drive, but if you have another around or a friend who would loan you one, you could try a minimal clean install for a few days, just to see if that is the problem. Or it could be a loose or bad cable. Of course there are other things that could cause it too. But, a noisy hard drive and I/O errors points to a hard drive issue to me. Check the other stuff and I will post back in the morning or X BlueRobot will.

 

[Ibebryan]

3.3V= 3.360V
5V= 5.120V
12V= 12.288V
CPU= 1.140V

my hard drive is connected to port 1 and all the cables are seated firmly. I have thought for a month or two that my hard drive has had some issues. I'm planning on replacing it soon so if nobody else has any possible problems, i will just replace it and clean install windows and see if that fixes these problems.

 

[essenbe]

OK. I believe with a Z68 board, you can put a flash drive in and boot into bios and press F12 and it will put a picture of the page you are looking at on the flash drive, if that helps. I believe it will be a .BMP picture, but you can use the snipping tool and save it as a JPEG to upload it.

 

[Ibebryan]

i tried to upload files from my phone but it failed and still posted i edited that

3.3V= 3.360V
5V= 5.120V
12V= 12.288V
CPU= 1.140V

my hard drive is connected to port 1 and all the cables are seated firmly. I have thought for a month or two that my hard drive has had some issues. I'm planning on replacing it soon so if nobody else has any possible problems, i will just replace it and clean install windows and see if that fixes these problems.

 

[essenbe]

Your voltages look good. I'd hate for you to spend money and find out you had some other problem. That's why I try to test it before spending money, if at all possible.

 

[Ibebryan]

Your voltages look good. I'd hate for you to spend money and find out you had some other problem. That's why I try to test it before spending money, if at all possible.

i only need a 500gb hard drive so they aren't that expensive, honestly i would spend hundreds to solve this problem! Dealt with constant and random bsod for 4-6 months.

 

[essenbe]

Hopefully spending that kind of money won't be necessary. Maybe we can find out something simple that will fix it. The Green drives are not very fast and spin down when not actively being used, so when called upon for data they have to spin up first, the Blue drives are good drives if you aren't rough with them. They can't take a lot of banging around and usually are fairly reasonably priced. You usually get fairly good speed with them. The performance drives with WD are the Black drives. They are fairly expensive, but are usually pretty fast, but not quiet at all. The Blue drives are pretty reasonable and the price difference between a 500 GB and a 1 TB is usually about $10-15. Seagate drives are usually a little cheaper. A lot of people don't like Seagate drives, but I use them and have had no problems with them. I use both and have no preference. Maybe that will help you a little. We'll hang with you and try to resolve this problem. We have some of the best people you can find here. I think you've seen that with X BlueRobot and Koolkat. They are great at what they do.

 

[Ibebryan]

Hopefully spending that kind of money won't be necessary. Maybe we can find out something simple that will fix it. The Green drives are not very fast and spin down when not actively being used, so when called upon for data they have to spin up first, the Blue drives are good drives if you aren't rough with them. They can't take a lot of banging around and usually are fairly reasonably priced. You usually get fairly good speed with them. The performance drives with WD are the Black drives. They are fairly expensive, but are usually pretty fast, but not quiet at all. The Blue drives are pretty reasonable and the price difference between a 500 GB and a 1 TB is usually about $10-15. Seagate drives are usually a little cheaper. A lot of people don't like Seagate drives, but I use them and have had no problems with them. I use both and have no preference. Maybe that will help you a little. We'll hang with you and try to resolve this problem. We have some of the best people you can find here. I think you've seen that with X BlueRobot and Koolkat. They are great at what they do.

yeah, you dont understand how much I appreciate the help!

 

[essenbe]

That's what we're here for. We'll help as much as possible, but you are the one who has to do the work. Just hang in there.

 

[x BlueRobot]

my hard drive is constantly running and has a very noticeable grinding sound. could replacing it resolve these issues? also before every crash my devices connected to the USB ports usually stop working. usually my mouse and headset specifically

Almost all the calls within the the call stack are reserved for the use of Microsoft only, so they're not documented with the WDK (Windows Driver Kit) docs, which is really irritating.

0: kd> [COLOR=SeaGreen]k[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`086c6098 fffff800`02f55bf0 nt!KeBugCheckEx
01 fffff880`086c60a0 fffff800`02ed5cee nt! ?? ::FNODOBFM::`string'+0x4518f
02 fffff880`086c6200 fffff800`02f2636e [COLOR=Red]nt!KiPageFault[/COLOR]+0x16e
03 fffff880`086c6398 fffff800`032df7fe [COLOR=Red]nt!wcsstr[/COLOR]+0x56
04 fffff880`086c63a0 fffff800`032df860 nt!SiIsWinPEBoot+0x4e
05 fffff880`086c63e0 fffff800`032e2952 [COLOR=Red]nt!SiCheckForUfdWinpeBoot[/COLOR]+0x30
06 fffff880`086c64c0 fffff800`032e2a1d [COLOR=Red]nt!SiCheckForAlternateSystemDisk[/COLOR]+0x12
07 fffff880`086c64f0 fffff800`032e479e nt!SiGetBiosSystemDisk+0x9d
08 fffff880`086c6570 fffff800`032fa4a7 nt!SiGetBiosSystemPartition+0x2e
09 fffff880`086c65c0 fffff800`032dfb5a nt!SiGetSystemPartition+0x27
0a fffff880`086c65f0 fffff800`0326554d nt!SiGetSystemDeviceName+0x3a
0b fffff880`086c6650 fffff800`032e5207 nt!IopRetrieveSystemDeviceName+0xac
0c fffff880`086c66b0 fffff800`0323c6f9 nt!IoQuerySystemDeviceName+0x37
0d fffff880`086c66f0 fffff800`031e33ad nt! ?? ::NNGAKEGL::`string'+0x52a6c
0e fffff880`086c6aa0 fffff800`02ed6e53 nt!NtQuerySystemInformation+0x4d
0f fffff880`086c6ae0 00000000`76fe161a nt!KiSystemServiceCopyEnd+0x13
10 00000000`0104c098 00000000`00000000 0x76fe161a

I'm also guessing that the SiCheckForUfdWinpeBoot function, is a way of system is checking for a Windows PE (Preinstallation Environment) on a UFD (or bootable USB Flash Drive).

wcsstr is a C++ string library function, which is used to search a substring (selected group of characters) within a wide string.

To be honest, I'm not completely sure why it's being called, but the problem is generated when the Kernel attempts to page some data into physical memory, but isn't able to because of a I/O error.

SiCheckForAlternateSystemDisk function makes me feel that there is a problem with the hard-drive too, checking for a alternate bootable partition?

 

[Ibebryan]

my hard drive is constantly running and has a very noticeable grinding sound. could replacing it resolve these issues? also before every crash my devices connected to the USB ports usually stop working. usually my mouse and headset specifically

Almost all the calls within the the call stack are reserved for the use of Microsoft only, so they're not documented with the WDK (Windows Driver Kit) docs, which is really irritating.

0: kd> [COLOR=SeaGreen]k[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`086c6098 fffff800`02f55bf0 nt!KeBugCheckEx
01 fffff880`086c60a0 fffff800`02ed5cee nt! ?? ::FNODOBFM::`string'+0x4518f
02 fffff880`086c6200 fffff800`02f2636e [COLOR=Red]nt!KiPageFault[/COLOR]+0x16e
03 fffff880`086c6398 fffff800`032df7fe [COLOR=Red]nt!wcsstr[/COLOR]+0x56
04 fffff880`086c63a0 fffff800`032df860 nt!SiIsWinPEBoot+0x4e
05 fffff880`086c63e0 fffff800`032e2952 [COLOR=Red]nt!SiCheckForUfdWinpeBoot[/COLOR]+0x30
06 fffff880`086c64c0 fffff800`032e2a1d [COLOR=Red]nt!SiCheckForAlternateSystemDisk[/COLOR]+0x12
07 fffff880`086c64f0 fffff800`032e479e nt!SiGetBiosSystemDisk+0x9d
08 fffff880`086c6570 fffff800`032fa4a7 nt!SiGetBiosSystemPartition+0x2e
09 fffff880`086c65c0 fffff800`032dfb5a nt!SiGetSystemPartition+0x27
0a fffff880`086c65f0 fffff800`0326554d nt!SiGetSystemDeviceName+0x3a
0b fffff880`086c6650 fffff800`032e5207 nt!IopRetrieveSystemDeviceName+0xac
0c fffff880`086c66b0 fffff800`0323c6f9 nt!IoQuerySystemDeviceName+0x37
0d fffff880`086c66f0 fffff800`031e33ad nt! ?? ::NNGAKEGL::`string'+0x52a6c
0e fffff880`086c6aa0 fffff800`02ed6e53 nt!NtQuerySystemInformation+0x4d
0f fffff880`086c6ae0 00000000`76fe161a nt!KiSystemServiceCopyEnd+0x13
10 00000000`0104c098 00000000`00000000 0x76fe161a

I'm also guessing that the SiCheckForUfdWinpeBoot function, is a way of system is checking for a Windows PE (Preinstallation Environment) on a UFD (or bootable USB Flash Drive).

wcsstr is a C++ string library function, which is used to search a substring (selected group of characters) within a wide string.

To be honest, I'm not completely sure why it's being called, but the problem is generated when the Kernel attempts to page some data into physical memory, but isn't able to because of a I/O error.

SiCheckForAlternateSystemDisk function makes me feel that there is a problem with the hard-drive too, checking for a alternate bootable partition?

but why is it looking for an alternate bootable partition?

 

[x BlueRobot]

Since, it maybe can't read the boot sector on your current Active partition.

 

[Ibebryan]

I just clean installed windows on my new hard drive. Got a western digital 1tb black drive. No problems and it's been about 12 hours. I will mark this as solved in a few days if no errors occur if not, I'll be back

 

[essenbe]

Great news. I hope your problem is solved by a new hard drive. Congratulations.

 

[x BlueRobot]

That's great to know, let's hope it solves the issue