Solved BSOD 0x0000000a 0x0000001e 0x00000050 0x0000003b

[essenbe]

I don't know what you are reading it with download CPUz CPU-Z CPUID - System & hardware benchmark, monitoring, reporting and install it. Open ir and leave I open on the CPU tab. That is correct no matter what any other program says. Only use 1 program at a time to read the speed. CPUz is recognized as the proof of what speed the CPU is.

 

[Useless User]

That's what I'm using to obtain the CPU freqency readings.

 

[essenbe]

You are going to have to give me some time to wake up. It's hard at my age. Run Intel burn test at standard with CPUz open. It will tell you what your CPU is running t. You have to put stress on several cores at the same time for it to kick in. Download IntelBurnTest 2.54 Just watch out for the junk ware they want to install with it, Just uncheck the boxes.

 

[Useless User]

No sweat, it's not urgent, there are other users wanting advice, too. I am happy that the PC works as it should (so far) running my application. I ran IntelBurnTest at the highest setting during my oddyssey several times - max. frequency is always 3.5GHz. Maybe my CPU wants to retire...

 

[essenbe]

No, it's just me and getting old. That's my only problem. You should be seeing 3.8 turbo. I seriously doubt you will notice a great difference, but In your Bios, change the multiplier for all cores from Auto(which I believe they are set at to 38 and see what happens. That should be your stock settings. I don't have an E series chip, but with Sandy Bridge and Ivy Bridge too, non e series, when you change the multiplier, you only change the turbo speed. Try that and see how you run. If you start to BSOD, Just go back and change it back. I would leave the voltage alone right now.

 

[Useless User]

Ok, a venture into BIOS land it is. I'll give that a try and revert, if something odd happens.

 

[essenbe]

Good. I had a board that was the same way. If set to auto, it wouldn't give me the correct turbo, so I set to what it is supposed to be and it worked great.

 

[Useless User]

Update on this neverending quest: In the meantime, I bought new memory kits - same BSODs as before - and I bought new motherboards - same BSODs as before - so that means I buy a new cheap-o graphics card next. If that changes nothing for the better, it can only be the CPU.

If only computer components could signal with certainty, if they are defective or not; all that wasted time (and money) could be saved...

 

[essenbe]

Post the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Also post screenshots of CPUZ CPU, Mainboard, Memory, and SPD tabs, Just the slots with memory in them on the SPD tabs. This will tell you how to post screenshots here.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Useless User]

Long time, no post... Since last time, I have purchased new DIMMs, motherboards, graphics cards to be able to exchange existing for new parts. With every new hardware component exchanged or added, I always wiped the SSD, reinstalled Windows 7, drivers and updates. As before, I have installed only my 3D light simulation software (which happily runs on other and equivalent PCs). So, apart from the CPU that always passes with Intel's IPDT, all key parts are brand new.

So far, I had no BSOD, but my software (the only non-Microsoft application installed) freezes the PC after 10-30 minutes or stops working ("A problem caused the program to stop working correctly..."). See also attached "MR crash info.png" from the Event Viewer.

What on Earth is going on here, after all these tests, clean installs and new components purchased TWICE(!)?

Please find the files attached... much appreciated!

ps: Should I open a "fresh" thread for this? It's practically a new PC?

 

[essenbe]

Please go into BIOS and tell me what your Turbo Multiplier is set to, and what your Vcore is set to and what mode you are using for Vcore, plus your Dram Voltage.

 

[essenbe]

If you haven't already, since you have changed Hardware, please make sure your System Specs are updated to reflect your new hardware. Maybe this will be of some help for you to do that.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html


EDIT: I don't know if it will make a difference for you, but update your CPUz, you are a few editions behind. You are running 1.68 and the newest version is 1.71 http://www.cpuid.com/softwares/cpu-z.html​

 

[Useless User]

I have made no changes to the BIOS and checked that the on-board switches are at their factory setting (no overclocking, underclocking or other modes selected).

I found that Vcore reads 1,272 V. The BIOS's "Ai Tweaker" screen shows, in yellow text, "All Core Target CPU Turbo-Mode Speed: 3800MHz" and below "Target DRAM Speed: 1600MHz". The DRAM has a "XMP" setting set. On the same BIOS screen, I see "DRAM Voltage(CHA, CHB)" is set to 1.65 V and DRAM Voltage(CHC, CHD)" is set to 1.65V. I do not see a "Turbo Multiplier" setting on the BIOS screens.

I finally got the good old 0x1e BSOD back on my latest configuration with new parts, so please find the SF-Tool's ZIP file attached.

 

[essenbe]

I know we've been here before, I think but hewe is what the dump file says

intelppm
start             end                 module name
fffff880`04c00000 fffff880`04c16000   intelppm   (pdb symbols)          c:\symcache\intelppm.pdb\08BB31C0378D48EC8CB513240E096A171\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: c:\symcache\intelppm.sys\4A5BC0FD16000\intelppm.sys
    Image path: intelppm.sys
    Image name: intelppm.sys
    Timestamp:        Mon Jul 13 18:19:25 2009 (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     intelppm.sys
    OriginalFilename: intelppm.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Processor Device Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That is the Intel Processor Driver There were also no other causes but quite a few references to the NTFS file system and possibly the hard drive.

What I would do is, check the hard drive with Seatools, Seagate's diagnostic test (SeaTools for DOS | Seagate) on your Mechanical Drive, run disk check (Tutorial search - Windows 7 Help Forums ) on the Mechanical Drive, check the SSD with Samsung Magician for any problems as well as a Firmware update. Then run all Windows Updates and check Installed updates for any that have failed. If you find failed ones, check further and make sure they were not installed again at a later date, otherwise install them again. Next go to the Intel Download Center (https://downloadcenter.intel.com/default.aspx) and run the Driver Update Tool and let it scan your computer for drivers and see if it finds any that need updating.

 

[Useless User]

Thanks for looking through yet another dump file. Nighttime here in old Europe; I come back with the results of what you suggest me to do tomorrow afternoon...

 

[essenbe]

Great, no problem. I may suggest after that is completed open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[Useless User]

Thanks; I had already used the sfc /scannow command and it came back with no errors. I do what you suggest in post #134 above once back from the workshop this late afternoon...

 

[essenbe]

Yes, I know you already ran it, but we've done a few things now and I wanted you to run it again and make sure everything is OK still.

 

[Useless User]

Sure; better be safe than sorry...

 

[essenbe]

If it does not help after you've done everything again, run http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html again and I'll take a look at it.