|
I've googled this but can't find a definitive answer that I can do.
My setup:
2600k
Crucial M4 128gb
P8Z68-v LE
8gb Corsair Vengeance
6870
I cannot boot into safe mode, I get a blue screen while loading classpnp.sys
I cannot boot normally, I get a blue screen.
I cannot open startup repair, I get a blue screen.
I cannot boot from Windows 7 disc, I get a blue screen.
I have tried:
1. disabling my overclock (4.5ghz)
2. safe mode, startup repair, and booting from disc.
3. using different HDDs
4. unplugging all peripherals and gpu
5. reseating memory.
Before this error, I was streaming. I thought my overclock just wasn't stable enough and tried to reboot, but I've been having this error since. Before this, my overclock was stable for the last month.
The BSOD errors I get are 0x000000a and sometimes 0x00000e7
Mostly the first, though. The 2nd one when booting from disc.
This is apparently a driver issue, but I don't know how to fix it, as I can't get into windows and cant change drivers.
|
This is how all people should post when asking for help with a bluescreen. Thank you for this, Nabutso. Best request for help I've seen in a long ass time 
How long have you been having this problem, and was any new hardware or software installed prior to this?
Is there any problems with the motherboard itself? I.E. scorching/burn marks near power plugs, popped capacitors, anything else out of the ordinary?
Will it allow you to boot into "Last Known Good Configuration" ?
Just spitballing a bit here, I'll try and look into it a little further.
|
On February 28 2012 02:51 HackBenjamin wrote:This is how all people should post when asking for help with a bluescreen. Thank you for this, Nabutso. Best request for help I've seen in a long ass time How long have you been having this problem, and was any new hardware or software installed prior to this? Is there any problems with the motherboard itself? I.E. scorching/burn marks near power plugs, popped capacitors, anything else out of the ordinary? Will it allow you to boot into "Last Known Good Configuration" ? Just spitballing a bit here, I'll try and look into it a little further.
This problem came about this morning after my pc crashed while streaming.
There are no problems with the motherboard. I checked this aswell but forgot to mention.
I cannot boot into last known config, either. I tried this aswell and did not mention.
Just tried reseating the cmos, still bsod.
|
I'm not sure what to suggest here actually.. You get blue screens even booting off the Win7 CD? After trying different hard drives?
Anything I suggest here is pure guesswork, so forgive me if I suggest things you've already tried or don't seem relevant. I'm seriously in the dark here.
-Try and run of a single stick of ram. If you still get blue screens, swap a stick for one you haven't tried yet, to eliminate the memory as a point of failure.
-Are you able to get into any kind of command prompt? If so, renaming classpnp.sys to classpnp.old should cause it to recreate the driver, if I'm reading and understanding the information online correctly.
-Something else I was reading said that a guy was having the same blue screens as yourself, and they stopped after he unplugged his RGB cable, since it was considered a plug and play device? Not sure if I agree with this, but worth a shot.
-Lastly, I read something from another BSOD victim that said classpnp.sys was loading properly, but the blue screens were being caused by the driver that was loading after it. Is it specifically naming classpnp.sys in the BSOD?
Anyone else? TheToast is really good with these kind of errors.
|
May be faulty hardware. Try removing your RAM and put in one at a time.
If it were a faulty driver you should be able to boot into safe mode. Also as you get the same BSOD when using different HDDs it points at faulty hardware.
Maybe RAm, maybe the MoBo
Oh and maybe try removing all plugged in devices, such as Webcams, mouse, keyboard etc (as stupid as it may sound)
|
On February 28 2012 03:07 HackBenjamin wrote:
I'm not sure what to suggest here actually.. You get blue screens even booting off the Win7 CD? After trying different hard drives?
Anything I suggest here is pure guesswork, so forgive me if I suggest things you've already tried or don't seem relevant. I'm seriously in the dark here.
-Try and run of a single stick of ram. If you still get blue screens, swap a stick for one you haven't tried yet, to eliminate the memory as a point of failure.
-Are you able to get into any kind of command prompt? If so, renaming classpnp.sys to classpnp.old should cause it to recreate the driver, if I'm reading and understanding the information online correctly.
-Something else I was reading said that a guy was having the same blue screens as yourself, and they stopped after he unplugged his RGB cable, since it was considered a plug and play device? Not sure if I agree with this, but worth a shot.
-Lastly, I read something from another BSOD victim that said classpnp.sys was loading properly, but the blue screens were being caused by the driver that was loading after it. Is it specifically naming classpnp.sys in the BSOD?
Anyone else? TheToast is really good with these kind of errors.
I cannot get into any command prompt, and it bsod's AFTER loading classpnp.sys in the safe mode screen. I don't know for sure if it's classpnp.sys causing it or the driver after, but I don't know what comes after.
Memory is OK, and I tried the monitor cable fix aswell. I'll try to find out the next driver...
|
What exactly makes you think the memory is ok when you can't even boot from the Win7 disc?
|
On February 28 2012 03:32 jaj22 wrote:
What exactly makes you think the memory is ok when you can't even boot from the Win7 disc?
I tried both sticks and another stick of ddr3 that I didn't have in my pc earlier.
|
Have you tried switching between the AHCI and IDE mode in bios?
Can you start if you remove the IDE-connector from the motherboard?
classpnp.sys is a SCSI related driver, so I definitely think it has something to do with corrupt harrdrive or ssd, but you said you tried with different ones... It's a bit strange you can't boot from CD however. I mean, if you just format everything and install some other OS, what kind of error would occur then? When did this start anyway? Maybe you could try using another bootable media, like recovery disks, where you can sector-scan/chkdsk or format everything?
|
On February 28 2012 03:37 Shauni wrote:
Have you tried switching between the AHCI and IDE mode in bios?
Can you start if you remove the IDE-connector from the motherboard?
classpnp.sys is a SCSI related driver, so I definitely think it has something to do with corrupt harrdrive or ssd, but you said you tried with different ones... It's a bit strange you can't boot from CD however. I mean, if you just format everything and install some other OS, what kind of error would occur then? When did this start anyway? Maybe you could try using another bootable media, like recovery disks, where you can sector-scan/chkdsk or format everything?
I have tried changing between IDE and AHCI mode, yes.
I just unplugged my normal SSD and HDD, and plugged in one I had laying around, and tried to boot with the windows 7 disc as if I was installing onto that disc, but it gave me the usual bluescreen 0x0000000A at the same exact point while windows is loading (JUST before the flag finishes).
I tried this earlier but I feel like this confirms it's not a problem with my SSD or HDD.
Edit: According to safe mode boot however, it stops at disk.sys instead of classpnp.sys
|
This definetely sounds like broken RAM or memory controller. Grab a memtest86(+) disc and check if it returns any errors.
|
On February 28 2012 03:51 Alvin853 wrote:
This definetely sounds like broken RAM or memory controller. Grab a memtest86(+) disc and check if it returns any errors.
Isn't this something that would've started when I first built the system?
|
I would lean on it being something with the mobo considering everything you have tried. I don't really have a good way for you to verify it though (other than to keep eliminated the other possibilities).
|
On February 28 2012 03:53 Nabutso wrote:Show nested quote +On February 28 2012 03:51 Alvin853 wrote:
This definetely sounds like broken RAM or memory controller. Grab a memtest86(+) disc and check if it returns any errors. Isn't this something that would've started when I first built the system?
I would agree with you, but overclocking does tend to put a bit more wear and tear on the system. Although I'm not sure of the correlation between overclocking and the memory controller... but I would say the controller sounds like it could be the problem, given that you have tested all the ram sticks individually.
|
My memory speed keeps trying to change to 1333mhz, even though it's supposed to be at 1600mhz.
edit: If the memory controller is the culprit, what should my next action be?
|
Sorry for the double post, but I'd really like to try to figure out what I'm going to do with this today.
If I could boot into linux would I somehow be able to replace the classpnp.sys and disk.sys and hopefully boot properly afterwards? I can't even boot from the windows 7 disc so I don't think I could even reformat.
If it is the memory controller, I'd have to get a new cpu, correct? Is there a way to make sure that's what it is? I don't have another system to test the cpu in, unfortunately, unless i opened up my laptop.
|
On February 28 2012 03:51 Alvin853 wrote:
Grab a memtest86(+) disc and check if it returns any errors.
I'm sorry, I seem to have missed the memtest86(+) results, can you post them again?
And yes, the memory controller is integrated on your CPU, and overclocking the CPU may have damaged the controller. Get the memtest-results and go from there, right now it's just guessing what the problem could be.
|
Sorry about that. I'll go ahead and make a memtest disc now; I just assumed since I had no memory problems for about 3 months that it couldn't be the issue. I'll be back with the results and I'll make sure I do plenty of passes.
|
I can't get my pc to read the memtest86+ disc. I've tried it with the iso, with the folder, with the contents of the folder, with different cd formats.. nothing. It just won't take.
|
You're probably doing it wrong. Don't use the "data disc" option of your CD writing software. Use "write image to disc" or similar.
Also if your memory keeps dropping down to 1333MHz, that's probably the SPD default and 1600 needs extra voltage. Leave it at 1333 until it's stable.
|
I must be doing something wrong or using the wrong files because I can't even run memtest off a usb.
I have tried using the boot folder itself.
I have tried using the iso.
I have tried using just the contents of the boot folder.
Nothing is running memtest. I swear, I am not bad with computers.
|
|
|
A difficult problem. I agree it's a driver/registry corruption, and the usual fix would be to do system repair, then restore to an earlier point. But you can't get to the repair part even using a boot disc.
What I'd do is try fiddling with my hardware and BIOS settings until I'd have my fill. (maybe CPI APIC support, Plug and Play OS) And if I still couldn't boot to the windows disc to repair the system, I would make a non-win7 boot option, use that to save any vital data, nuke the hard drive, then install again from scratch.
|
I ran 3 passes of memtest and there were no errors.
I'm starting to suspect my sata ports on my motherboard. Unfortunately ALL of them seem to bring about this bsod.
memtest wouldn;t work through my cd drive, and neither my ssd or any hdds work either.
|
Sorry to double post again but I'm at a total loss now.
No memtest errors with many passes done, reseated everything, tried every sata port, tried every boot cd I have (xp, w7 32bit, w7 64bit). I feel like the problem is my sata controller but I have no way to fix that, do I?
|
I'd like to update the status of this.
I've tried a new mobo, still gets the same error.
I went and bought a new stick of DDR3 aswell, same error.
The only thing it can possibly still be is the PSU or the CPU, as those are the only parts that have been in each one of these tests.
Is it possible for it to crash at an EXACT SAME POINT due to the PSU? I don't think so...
The last possible option then is the CPU... but it works fine if I boot into linux from my usb.
Edit: strange update.
I just disabled both hyperthreading and limited my cpu to 1 core and it booted fine.
edit#2: it seems my cpu can't boot into windows unless I have 3 of it's cores disabled.
|
On March 02 2012 10:54 Nabutso wrote:
I just disabled both hyperthreading and limited my cpu to 1 core and it booted fine.
and how did u do that? in bios?
|
On August 17 2012 07:49 mat.mich wrote:Show nested quote +On March 02 2012 10:54 Nabutso wrote:
I just disabled both hyperthreading and limited my cpu to 1 core and it booted fine. and how did u do that? in bios?
In the bios, yep.
By the way, replacement CPU from intel fixed the issue.
|
damn.. i have same problem but no such option in bios. thanks
|
Bot edit.
User was banned for this post.
|
|
|
|
|
|
EPT
