Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD When booting, or logging into Windows


14 Dec 2013   #11

Windows 7 64 bit
 
 
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




Attached Files
File Type: zip SF_14-12-2013.zip (1.92 MB, 1 views)
My System SpecsSystem Spec
.

15 Dec 2013   #12

Windows 7 Home Premium x64
 
 

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.
Quote   Quote: Originally Posted by Arc View Post
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.

Quote   Quote: Originally Posted by Arc View Post
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:
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
16 Dec 2013   #13

Windows 7 64 bit
 
 

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
My System SpecsSystem Spec
.


17 Dec 2013   #14

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
19 Dec 2013   #15

Windows 7 64 bit
 
 

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
My System SpecsSystem Spec
13 Jan 2014   #16

Windows 7 64 bit
 
 
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.
My System SpecsSystem Spec
15 Jan 2014   #17

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by moocows View Post
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.
My System SpecsSystem Spec
Reply

 BSOD When booting, or logging into Windows




Thread Tools



Similar help and support threads for2: BSOD When booting, or logging into Windows
Thread Forum
Solved BSOD when logging in Windows 7 BSOD Help and Support
BSOD while scanning with AVG, logging into windows. Random times. BSOD Help and Support
BSOD occurs after logging in to windows BSOD Help and Support
BSOD 5-10 min after logging into windows (with info) BSOD Help and Support
Solved BSOD a few seconds after logging into windows, bad_pool_header BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:55 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33