Solved BSOD right after "Starting Windows" screen goes away

[cedsays]

Hello All, unfortunately, I'm back again with more problems. Few weeks ago I ran into some internet problems when I'm not sure are related or not. But that went away and then my compute would freeze and I would have to reboot. After I noticed what was happening I just new BSOD was next. Yesterday was completely fine. I turned the computer on and BSOD after BSOD. I've managed to get into safemode with networking so I can make this post and it's been about.. 30mins and everything seems fine. Also I went into BIOS and heard a BEEP then the computer froze. Going to try to boot normally and see where I get if not I'll be back into safe mode waiting for further help. Thank you.

 

[surge411]

It contains no dump file.. Do you know the error on the bsod, or the STOP code (like HIGH_IQRL_NOT_LESS_OR_EQUAL; STOP 0xD1)

 

[cedsays]

It contains no dump file.. Do you know the error on the bsod, or the STOP code (like HIGH_IQRL_NOT_LESS_OR_EQUAL; STOP 0xD1)

Took this just in case. Hope it helps

http://i.imgur.com/BGwlpsd.jpg

 

[surge411]

Ok, it seems to be 0xD1, when a driver tries to access an address in the memory that, simply putting it, it isn't allowed to access. It could be a symptom for one of the following problems:

• Driver Problem
• Faulty RAM
• Faulty Motherboard
• Or another faulty device

It is normally caused by drivers but, it could be caused by some other faulty device, especially RAM. I recommend running MEMTEST86+ for 1-4 passes (2 is the best to be sure, if you want you can do more) Here is a good guide: Guide to using Memtest86+ - Geeks to Go Forums

Next I would put on Driver Verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html It will detect faulty drivers and BSOD when it is found.

Now to the driver causing the issue: It seems to be PCIIDEX.SYS which is a Microsoft Driver, specifically the PCI IDE Bus Driver. BSODs are usually not caused by MS Drivers, so a BSOD pointing to it gives a bigger chance of hardware failure. Also, is it always the same, or are there random BSODs at random times?

 

[cedsays]

Ok, it seems to be 0xD1, when a driver tries to access an address in the memory that, simply putting it, it isn't allowed to access. It could be a symptom for one of the following problems:

• Driver Problem
• Faulty RAM
• Faulty Motherboard
• Or another faulty device

It is normally caused by drivers but, it could be caused by some other faulty device, especially RAM. I recommend running MEMTEST86+ for 1-4 passes (2 is the best to be sure, if you want you can do more) Here is a good guide: Guide to using Memtest86+ - Geeks to Go Forums

Next I would put on Driver Verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html It will detect faulty drivers and BSOD when it is found.

Now to the driver causing the issue: It seems to be PCIIDEX.SYS which is a Microsoft Driver, specifically the PCI IDE Bus Driver. BSODs are usually not caused by MS Drivers, so a BSOD pointing to it gives a bigger chance of hardware failure. Also, is it always the same, or are there random BSODs at random times?

Got an email with your reply while I was at school. I came home booted my pc to do what you suggested and more BSOD. I got the second BSOD while in safe mode with networking. I tried safemode without and it still stuck on a black screen.

Edit: On the laptop. I can't get any mode to work and it freezes in the BIOS.
Edit2: Did the verifier stop..kinda afraid to reboot this PC again. Will do memtest overnight if the PC allows me.

 

[cedsays]

Going to let it go for another pass. So far so good.

 

[cedsays]

3rd pass.

 

[cedsays]

Update 11/26

After the starting windows screen, I see a quick(what I think is) BSOD then monitors, keyboard etc.. loses signal and I'm forced to restart.

After 4 freezes I finally got to my desktop and it froze.

 

[surge411]

Hello, sorry for the late reply (I myself have been having some technical problems )

Ok, I have a very strong feeling it is a hardware problem. There is all the evidence to prove it; Random errors, random drivers.

Seems like your RAM is fine. Have you ran CHKDSK? It's really important in my opinion because the second suspect after RAM is HDD. Go into CMD (As admin) and run chkdsk /r /f and then type Y. Restart and wait. (I suggest you do this overnight because it will take hours). I hope you are able to get into the desktop long enough.

When it freezes does it blue screen? Try to wait a while and see if it does.

 

[cedsays]

Hello, sorry for the late reply (I myself have been having some technical problems )

Ok, I have a very strong feeling it is a hardware problem. There is all the evidence to prove it; Random errors, random drivers.

Seems like your RAM is fine. Have you ran CHKDSK? It's really important in my opinion because the second suspect after RAM is HDD. Go into CMD (As admin) and run chkdsk /r /f and then type Y. Restart and wait. (I suggest you do this overnight because it will take hours). I hope you are able to get into the desktop long enough.

When it freezes does it blue screen? Try to wait a while and see if it does.

I've ran CHKDSK and sfc/ scannow yesterday and both shows no errors. I've never left it on long enough to see if it BSOD after a freeze. I'll wait it out next time to see if it will.

 

[surge411]

Open msconfig and check diagnostics boot. It will boot without loading startup items.

Also, it seems there are no errors. So I think not a disk problem. Do you have other disks? Try removing them temporarily.

Run an indepth virus scan, including root kits. (Malware bytes is a good scanner, although if your antivirus supports root kits it's fine)

Is it a possibility to reinstall? I'm not saying we should give up, but it seems like a hardware error anyways, so it would be a good step in trouble shooting.

What, exactly, did you do when "your computer was running fine"? New software? New headsets? Anything like that is important! Have you tried system restore? If not, try to remove any hardware except keyboard and mouse, and then restore to a restore point before the problems started.
You also said something about your in Internet not working before. What network card do you use? If it integrated to the motherboard?

 

[cedsays]

Open msconfig and check diagnostics boot. It will boot without loading startup items.

Also, it seems there are no errors. So I think not a disk problem. Do you have other disks? Try removing them temporarily.

Run an indepth virus scan, including root kits. (Malware bytes is a good scanner, although if your antivirus supports root kits it's fine)

Is it a possibility to reinstall? I'm not saying we should give up, but it seems like a hardware error anyways, so it would be a good step in trouble shooting.

What, exactly, did you do when "your computer was running fine"? New software? New headsets? Anything like that is important! Have you tried system restore? If not, try to remove any hardware except keyboard and mouse, and then restore to a restore point before the problems started.
You also said something about your in Internet not working before. What network card do you use? If it integrated to the motherboard?

There are no other disks. I've ran a full scan with both Megabytes and Microsoft Security Essentials and nothing was found.

Left the computer on and went to familes( Happy Thanksgiving btw) came home and it was froze. Keyboard and mouse lights were still on. Both monitors were fine and I can hear the fan running. In the mess of all the reboots the windows repair tool did a system reboot and it changed nothing.


Attached is a snip of my device manager.

 

[cedsays]

Update 11/28

Got the computer to run for about 20-30 mins. I went downstairs to get a drink and when I came back it was frozen. I rebooted and as soon as it got to the desktop it froze. Again, rebooted. This time it was stuck on the starting windows screen. I waited a good 10 minutes to make sure it just wasn't booting slow. Rebooted once again and startup repair opened. That's running now.

 

[cedsays]

Booted PC into safe mode and right after it loaded all files it flashed a BSOD screen and everything lost signal. I tried 3 times to reboot and there was no beep. after uh.. 5 minutes of trying it finally booted and I shut it down before it could freeze again.Haven't touched it since.

 

[cedsays]

Got into safemode twice and both times after about 10 minutes everything lost signal. PC was still running but both monitors, mouse, and keyboard had no signal.

 

[cedsays]

Computer no longer gets passed the starting windows screen. Always freezes right there. It either freezes in safemode or once in safemode everything loses signal as stated above.

 

[Arc]

A stop 0xD1 with pciidex.sys as the probable cause.
A stop 0x24 with ntfs.sys as the probable cause.

Stop 0xD1 is usually a driver related issue. Whereas pciidex.sys is the system native ATA controller. It cannot fail on itself. And a stop 0x24 is a file system error. So both are indicating to disc subsystem.

Do some Disc checks.

1. Reseat the sata and power. If possible, change the SATA cable, and apply the SATA cable on an unused port on the motherboard.
   
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

Similarly, there are some errors with the VTunes Display Control Panel.

Event[34376]:
Log Name: System
Source: Service Control Manager
Date: 2013-10-08T10:15:56.790
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ceds-PC
Description:
The TBPanel service failed to start due to the following error:
The system cannot find the file specified.

If the disc checks are all positive, we may need to concentrate on this part.

 

[cedsays]

A stop 0xD1 with pciidex.sys as the probable cause.
A stop 0x24 with ntfs.sys as the probable cause.

Stop 0xD1 is usually a driver related issue. Whereas pciidex.sys is the system native ATA controller. It cannot fail on itself. And a stop 0x24 is a file system error. So both are indicating to disc subsystem.

Do some Disc checks.

1. Reseat the sata and power. If possible, change the SATA cable, and apply the SATA cable on an unused port on the motherboard.
   
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

Similarly, there are some errors with the VTunes Display Control Panel.

Event[34376]:
Log Name: System
Source: Service Control Manager
Date: 2013-10-08T10:15:56.790
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ceds-PC
Description:
The TBPanel service failed to start due to the following error:
The system cannot find the file specified.

If the disc checks are all positive, we may need to concentrate on this part.

By reseat do you mean to unplug then plug back in(sorry).
Currently running chkdsk /f/r
and I don't have any blank CD's. is it possible to boot that from a usb by chance?

 

[Arc]

If you can make a bootable USB, it will work. Otherwise you may get a blank disk soon.

Yes, Reseat means unplug and plug back

 

[cedsays]

If you can make a bootable USB, it will work. Otherwise you may get a blank disk soon.

Yes, Reseat means unplug and plug back

Cool. I did so before the chkdks. It's on stage of 5 now. No errors
I went online and found a bootable USB for seatools for DOS.
Stage 5 is at 20%, so once that finishes I'll be running seatools the I'll get back to you.
Thanks again for helping.