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: BSODs I have avoided dealing with, until now.

25 Jan 2013   #1

Windows 7 Home Premium 64bit

Hey, I have had alot of BSOD over the past few months. I think I had my first one while using demon tools and yasu cloaking... in this time I had no firewall for about 2 days. I got a virus via spotify but bitdefender dealt with that. I have had BSOD off and on since. I generally get them while running programs whether games or just chrome. I deceided to uninstall these programs and many have had errors running through them appart from BSOD since the first BSOD happened while they were open... I now have a Java Version 6 update 30 I cant uninstall and get error 1723. For which I cant find a solution for online.

Basically I want to try deal with these BSOD's
I have a number of minidump logs from these crashes

Thanks, CJ

Yeah here is the zip although I might of doubled up by clicking grab all twice. Anyway I dont really know what I am doing with this but I saw you guys helping others with BSOD so maybe you could help me :3

My System SpecsSystem Spec
25 Jan 2013   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Hi and Welcome to SevenForums.

I've run a few dumps and 1A Memory_Management is consistent.
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001ad2be0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )

Followup: MachineOwner

1: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
25 Jan 2013   #3

Windows 7 Home Premium 64bit

Thanks a lot, I'll have to get onto the testing later though as I'm getting some zzz now. It's also Australia Day tomorrow so I will reply in at least the next 2 days with the results. And thank you, any help is appreciated!
My System SpecsSystem Spec

25 Jan 2013   #4

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

You're welcome.

Look forward to your results
My System SpecsSystem Spec

 BSODs I have avoided dealing with, until now.

Thread Tools

Similar help and support threads
Thread Forum
BSODs, maybe when dealing with usb cord?
Hi, I don't know if these BSODs are random, or coincidental but a lot of them happen when i'm using an ipod connected to the usb charger on the PC. Here are the zip files
BSOD Help and Support
Time now for that long avoided re-install of win7 on laptop
Setup: Sager NP8760 Laptop Motherboard: Clevo W870CU Mobo chipset: Ibex Peak-M PM55 HDD: 2 500GB Hatachi drives I seem to have scrambled the system drive and a small boot partition to the point where the machine can not be booted and has ead to the error blocking...
General Discussion
Laptop beeps loudly on powering on. Can be avoided by pressing f10.
Hey, whenever i power on my laptop, there is a loud beeping sound which continues forever. I have to shut it down by pressing the power button for 5 seconds. What I have found is that when i start the laptop and keep pressing f10 and then exiting the page without saving the changes, the laptop...
Hardware & Devices
BSOD when dealing with controllers
I have uploaded the SF_Diagnostic_Tool.exe .rar as asked. Basically, my Win 7 BSOD back when I had my 360 controller hooked up to it. Well I noticed that the controller's wires were weak at the connection, when I moved it, it would unplug and plug, and enough of that would cause the BSOD. ...
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 01:35.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App