It Guy beaten

[jeepjkdan]

Windows 7 PRO
x64 OEM from MWAVE
3 year hardware
6 months of win 7 pro

.Dmp attached What is going wrong??
Please any info would be great

 

[panais]

Windows 7 PRO
x64 OEM from MWAVE
3 year hardware
6 months of win 7 pro

.Dmp attached What is going wrong??
Please any info would be great

Hi,welcome to SF
Ur minidump points to win32k.sys that error it may caused by SuperCopier.
So please do the follows,
Download and install CCleaner - Optimization and Cleaning - Free Download
Uninstall SuperCopier,clean registry with ccleaner,restart.
-------------------
Please post back with any results!

 

[jeepjkdan]

Done and no good

Still Blue screens here are the new logs.

Thanks for your help. Any more would be Great!!

 

[jeepjkdan]

Once this is fixed i am thinking i might learn how to debug myself are there any sites i can check to learn how to get answers from these .dmp myself??
or ones that could be recomended?

Cheers Guys

 

[zigzag3143]

Once this is fixed i am thinking i might learn how to debug myself are there any sites i can check to learn how to get answers from these .dmp myself??
or ones that could be recomended?

Cheers Guys

There is a really steep learning curve. Your best bet (if you want to do them for others) is to start with an app like blue screen view and check answer already in place. Then ask someone who is doing them.

 

[jeepjkdan]

I am using blue screen view already, Couldnt manage to sort out this problem so i thought i might as well take the next step....

I cant even figure out how the first dumps pointed to super copier even though it wasnt the cause...?

 

[jeepjkdan]

Sorry I Should probabily have asked if there was any new info in the Dump files after i followed
this instruction Uninstall SuperCopier,clean registry with ccleaner,restart.

 

[zigzag3143]

Still Blue screens here are the new logs.

Thanks for your help. Any more would be Great!!

Newest is related to memory corruption from an unknown driver (ipodservice suspect) Please run these.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[jeepjkdan]

Ok A few things I have tried tried ram with no faults removed 1 stick seems to make it bsod less but couldnt get a bad result from memtest over the 3 or 4 I have already done tried diffrent combinations and diffrent sticks (Borrowed from work)
verifier with testing all did not fault
verifier /reset done after about 4 reboots with no BSOD....

Im pretty stumped, I will try this stuff again tonight but i am thinking the result wont change....

 

[zigzag3143]

Ok A few things I have tried tried ram with no faults removed 1 stick seems to make it bsod less but couldnt get a bad result from memtest over the 3 or 4 I have already done tried diffrent combinations and diffrent sticks (Borrowed from work)
verifier with testing all did not fault
verifier /reset done after about 4 reboots with no BSOD....

Im pretty stumped, I will try this stuff again tonight but i am thinking the result wont change....

Laptop or desktop?

Heat, power, etc?

 

[jeepjkdan]

desktop, Fans everywhere & Power should be ok, Modems Etc on same board that are all ok, With playstation 3. So it should go as well if there was an issue..
PSU on the the other hand could be on its way out though it is only 6 months old...... But i would expect the raid card to drop drives if there was a power issue....

 

[jeepjkdan]

Well it's 2 tests down on the memtest but I think it will pass... I guess if it's a driver issue or a windows issue maybe I should just format the hdd or swap it for a spare and install windows again and do some testing. That should fully confirm if I'm looking at a hardware or a software issue... Any thoughts?

 

[zigzag3143]

Well it's 2 tests down on the memtest but I think it will pass... I guess if it's a driver issue or a windows issue maybe I should just format the hdd or swap it for a spare and install windows again and do some testing. That should fully confirm if I'm looking at a hardware or a software issue... Any thoughts?

RAID??? bet that is the cause. try updating the driver.

 

[jeepjkdan]

Ok, it crashed again last night, Memory test was fine, I reinstalled raid drivers this morning.

Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version Dump File Size
061811-24812-01.dmp 18/06/2011 8:42:49 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`0b297001 00000000`00000000 fffff700`01080000 ntoskrnl.exe ntoskrnl.exe+70700 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16792 (win7_gdr.110408-1633) x64 C:\Windows\Minidump\061811-24812-01.dmp 4 15 7600 276,560
061811-280312-01.dmp 18/06/2011 7:11:10 AM BAD_POOL_HEADER 0x00000019 00000000`00000020 fffffa80`022972d0 fffffa80`02297c50 00000000`0498000c ntoskrnl.exe ntoskrnl.exe+70700 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16792 (win7_gdr.110408-1633) x64 C:\Windows\Minidump\061811-280312-01.dmp 4 15 7600 276,560
061711-23468-01.dmp 17/06/2011 10:27:18 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+706d0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16792 (win7_gdr.110408-1633) x64 C:\Windows\Minidump\061711-23468-01.dmp 4 15 7600 276,560
061711-24390-01.dmp 17/06/2011 8:20:31 AM DRIVER_CORRUPTED_EXPOOL 0x000000c5 fffff900`00002258 00000000`00000002 00000000`00000000 fffff800`02db822f ntoskrnl.exe ntoskrnl.exe+70700 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16792 (win7_gdr.110408-1633) x64 C:\Windows\Minidump\061711-24390-01.dmp 4 15 7600 276,560
061711-29171-01.dmp 17/06/2011 7:49:09 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`3160381b 00000000`00000000 fffff800`02ce761f 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+70700 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16792 (win7_gdr.110408-1633) x64 C:\Windows\Minidump\061711-29171-01.dmp 4 15 7600 276,592



So im thinking now that the .dmp files yelded no results & we are kinda looking at drivers its a hit or miss approach. So im better off with a full format and reinstall of windows 7 pro + Raid drivers Etc

 

[jeepjkdan]

Should have put ???? Any ideas or is that probably the way to go??

 

[zigzag3143]

Should have put ???? Any ideas or is that probably the way to go??

Your choice, but clean install (with format) is usually the fastest way to fix the problem and make your system more efficient as well.

They are a pain, but I do them every 4 months regardless.,

 

[jeepjkdan]

So clean install.
Raid driver install
Updates
Started ninite install of everything

Then....

BSOD

Must be hardware ! What now?

 

[jeepjkdan]

here is the dmp

 

[jeepjkdan]

Also when testing bios voltages CPU changes between 1.248 to 1.240. All others ok... Could my psu cause intermittent bsod....??