BSOD when logging into windows 7 - 0x0000001E.

[Skev]

Hi

For some reason overnight my PC now gives me the BSOD when i log into windows from the start up screen.

I have tried starting up my PC with the graphics card removed, RAM changed and DVD drive removed but it still does it. Starting in safe mode is 100% fine though.

Attached is the DM log. Please help!

 

[Skev]

screenshot of BSOD added

 

[Arc]

Hi Skev.

You havent uploaded all the necessary files generated by the tool. From what we have, it looks like a memory issue. It may not be the RAM necessarily, but due to lack of data, we should start from the RAM test.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
__________________________

BugCheck 50, {ffffffffffffffff, 8, ffffffffffffffff, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f )

Followup: MachineOwner
---------

BugCheck 1E, {ffffffffc0000005, fffff800036429c6, 0, 7}

Probably caused by : ntkrnlmp.exe ( nt!CmpGetContextAnchorForThisThread+26 )

Followup: MachineOwner
---------

 

[Skev]

Hi, thanks for the quick reply - this new zip file should have all the info missing from the other one!

Hi Skev.

You havent uploaded all the necessary files generated by the tool. From what we have, it looks like a memory issue. It may not be the RAM necessarily, but due to lack of data, we should start from the RAM test.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
__________________________

BugCheck 50, {ffffffffffffffff, 8, ffffffffffffffff, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f )

Followup: MachineOwner
---------

BugCheck 1E, {ffffffffc0000005, fffff800036429c6, 0, 7}

Probably caused by : ntkrnlmp.exe ( nt!CmpGetContextAnchorForThisThread+26 )

Followup: MachineOwner
---------

 

[Arc]

Thats good. That will be needed after knowing the result of the memtest.

 

[Skev]

Hi, memtest was fine. Ran it with each stick in each slot for 8 passes and all fine.
Any ideas?

 

[Arc]

If memtest passed good, then the source of the memory corruption is a driver most possibly. 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.