BSOD When booting, or logging into Windows

[moocows]

Hello,
Since Nov 11, ive have been having random blue screens. The first 2 i did not catch the code in time. But the third, fourth, and fifth (5th having been today) I do have. The third's was STOP 0x24, fourths was STOP 0x19 and todays was STOP 0x3B. After the stop 0x19 i thought it was enough so i did a system restore, which fixed it for a few days until today. Because of my restore the minidumps were erased but i have the minidump from todays, STOP 0x3b. I have no idea how to attach it, and have tried emailing it to my uncle. I dont know how to open the file and wouldnt even know what it meant if i did open it. Can someone please help? I just want this to stop. After the blue screens it restarts and runs normally and such, it does not keep constantly happening like most of the cases ive read. I suspect it is a driver but i cant read the minidump to tell. Would someone be able to tell me how to attach it to this forum so someone can read it and tell me what is the problem??? And if so what i can do about it??? Please this is really concerning me and i just want it to stop.
Thank you

Things I have tried:
chkdsk c: /f /r
sfc /scannow
system restore to before the date of blue screens.

I even uniinstalled any program i had installed near that time, but it shouldnt matter either way as the system was restored. Please help, and thank you for your time.

 

[Brink]

Hey moocows, and welcome to Seven Forums.

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help.

 

[moocows]

File

I did as it says and got this zip file. Here you go.
Thank you

 

[moocows]

Please help

Hello,
After a day of not happening the blue screens are back worse than before. Today it has blue screened me everytime I boot the PC. Usually a short time after logging into windows. The errors I got today are:
STOP 0x1A
STOP 0x1e
STOP 0x50
I will attach the file I have obtained that contains todays errors and the error from the 23rd. It is notable to add that strangely every time I booted it up, after the Starting Windows screen, it would say no DVI signal. Then the windows log in would appear and id log in. The format of the taskbar was all messed up, anytime I opened Firefox the top taskbar would have a large white line over it covering the minimize, maximize, and X buttons. It ran a bit slower than usual. I ran a Windows Memory Diagnostics Test and it said everything was fine. I am extremely concerned and would really like help.
This brings the total error list to (in order):
STOP 0x24
STOP 0x19
STOP 0x3b
STOP 0x1A
STOP 0x1e
STOP 0x50

Thank you for your time

 

[moocows]

Please help (continued)

I thought i should add that back in june i upgraded my graphics card. From a geforce gtx 560 to a geforce gtx 660. After the upgrade the auto detecter on the nvidia website couldnt detect my gpu. After that i downloaded the geforce expirience program from nvidia which updates my driver. After that it was fine. Recently around the time of the one blue screen my pc did a check for consistency. After that it rebooted and green and pink lines covered the lower part of my background. I restarted the pc and it went away. Could any of this be related? Im very eager for an admin to read the dmp files and id the problem.
Thank you

 

[YoYo155]

Hi moocows, welcome to 7F .

Some information filled files are missing, so I'm not getting the full picture.
Please run the SFDT again and let it run its course it can take 15min at times to collect all the data necessary.
There should be eight files generated not including the dumps.

The majority of the bug checks appear to have been due to Norton,
please upload the rest of the files needed as your most recent driver is dated;

Tue Feb 14 12:55:35 2012

.

Please remove Norton using the appropriate tool that matches your installed software:

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Install Microsoft Security Essentials as an alternative:

• Microsoft Security Essentials - Microsoft Windows

If you're concerned about your GPU you can test the hardware,
Test for thermals and stability:

• Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).

Post back with the results and the rest of the files.

 

[moocows]

It did run its course, it said information gather complete. I did exactly as instructed. I have Norton on 2 other computers and has never caused problems, could a fresh install fix this? The problem now is that I cannot even access the computer for the most part. I get a wermgr.exe error that says The exception Illegal Instruction. I am so confused an upset by whats happening that I consider whipping the entire hard drive. How could I do this and if I do how can I get drivers for my hardware again? My mobos river disk causing a blue screen when I use the install all feature. Also would I need a new windows key? Or will the one I used for the intial build be enough?

Edit: I do have my original Windows 7 disk. I don't know if this would help with anything such as wiping. I would rather not wipe it but I want this solved, and if that will solve it then so be it.

 

[YoYo155]

It did run its course, it said information gather complete. I did exactly as instructed. I have Norton on 2 other computers and has never caused problems, could a fresh install fix this?

You can always reinstall it at the end of the troubleshooting procedure and test if the issue
reemerges. I can only suggest you do so the final decision is yours.

The problem now is that I cannot even access the computer for the most part. I get a wermgr.exe error that says The exception Illegal Instruction.

wermgr is the messenger reporting an issue, what does it say?

I am so confused an upset by whats happening that I consider whipping the entire hard drive.

You can if you wish, again it's your PC.

How could I do this and if I do how can I get drivers for my hardware again? My mobos river disk causing a blue screen when I use the install all feature.

You can download them prior to wiping the HDD.
And that shouldn't happen, do you have the dumps from those crashes?

Also would I need a new windows key? Or will the one I used for the intial build be enough?

   Warning

DO NOT! post your product key!

You might need to activate it via a phone activation afterwards, please post a picture of your sticker
with the product key blocked out!.

 

[moocows]

Progress (?)

So after redoing the SF Diagnostic, this time in safe mode, I got all the 8 files and dumps you were talking about. To elaborate the error I got was wermgr.exe - Application Error. "The exception Illegal Instruction. An attempt was made to execute an illegal instruction. (0xc000001d) occurred in the application at location 0xf7667cd7.". On next boot another thing popped up saying Windows Explorer has encountered an error. Then it would close and then a thing would appear that said Windows Explorer is restarting. It would keep cycling like this until I eventually restarted in safe mode. Everytime it cycled the desktop would reload and I could not do anything. This leads me to believe it is a program or driver error. After reviewing the files included, do you still think this is a Norton problem? Or does this point to something else?? What do these new errors mean??

I was thinking that after I remove whatever is causing this, should I do a Windows Repair Install?? Would you recommend this??? Thank you

PS. The Blue Screen dump caused by my MOBO driver disk is the very first one from August 2013.
Thank you

 

[YoYo155]

Please remove Norton if you wish to continue troubleshooting this issue.
As for the dump from August with regards to the drivers CD, it appears to have been due to
Intel Rapid Storage Technology, I advise against installing it and any other utilities
that usually come per-bundeled in such OEM driver CDs, if in fact you do decide to wipe the entire OS.

As for a repair install you can, just make sure you understand the procedure and prerequisites.

• http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[moocows]

The Problem Returns

So the blue screens had stopped for a while, and i continued using both Norton and just the PC in general. I read on norton forums that a windows update conflicts with norton sometimes and can cause blue screens. The update effected IE 10, so i have tried many times to remove it since it will not affect my machine, every time it either freezes or says failed to configure updates. I have been extremely sick recently recently and have barely used my pc and whenever i have it has been a day tues-thurs, out of paranoia and my noticing that the blue screens only happened on Fri-mon i avoided using it on the weekend for the longest time, especially since i was extremely sick and mainly just laid in bed. Today i have had the first blue screen in a couple of weeks. I will post the files, it is the 141213 file. Would you be able to tell me what has caused this one? And do you think this weekend blue screen thing is a coincidence or a pattern? The screen i got today was STOP 0x1a (or a1 i forgot) and said memory management at the top.
Thank you

 

[YoYo155]

Hi, I hope you're feeling better .
The latest bugcheck is the of the type that the culprit is no longer around when the fault is discovered
which makes us have to work a little harder to find it.

Please follow the procedure detailed below, to try and find the culprit.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[moocows]

I have not yet had time to run memtest yet, but I have run the windows one before and it passed. I will still be running memtest for 8 passes as you recommend though. I have 4 ram sticks though, 4 gigs each. Will the same memtest still work? And if any stick fails will it tell me which slot produced the failing stick? Thank you

 

[YoYo155]

Windows Memory Diagnostic Tool, is not a good enough of a test.
Even Memtest86+ is not perfect and by no means 100% fault-proof.
You can test all of the sticks simultaneously, it's fine, but no it won't be specific as to which
is failing that is where trail and error comes in.

 

[moocows]

Okay thank you, ill do the memtest sometime between today and monday. I just havent had enough time to allot time for the tests. I had a question though, if whether or not having my previous graphics cards driver on my machine with my new graphics card could cause this. When i installed the new gpu i dont think i removed the old gpus drivers due to lack of knowledge on how to. So i just installed the new drivers for the new card and went on my way.
Thank you

 

[moocows]

Memtest: Complete

Hello,
Sorry for the lack of communication, i have had a good amount on my plate and was only recently able to get a disc to burn memtest on to. I am in the middle of the test, 7 passes and 0 errors so far, so hoping that i get an 8th pass. I had a question about the driver verifier. Once it BSODs from the verifier will the driver that caused the BSOD be listed on the screen, in the minidump, or both? Thank you very much. I feel like im one giant step closer to fixing this.

 

[YoYo155]

Hello,
Sorry for the lack of communication, i have had a good amount on my plate and was only recently able to get a disc to burn memtest on to. I am in the middle of the test, 7 passes and 0 errors so far, so hoping that i get an 8th pass. I had a question about the driver verifier. Once it BSODs from the verifier will the driver that caused the BSOD be listed on the screen, in the minidump, or both? Thank you very much. I feel like im one giant step closer to fixing this.

It's OK, we all have life to deal with .

Yes Driver Verifier is especially designed to catch drivers red-handed, so hopefully it will prove revealing.
Most of the times the offending driver is being displayed at the BSOD itself but not all the time.