BSOD - diffrent ones tryed alot

[misticJP]

i have BSOD's alot of diffrent ones and freezes during dump
saved some dump files,, if any one has some idea's i could try
checked all hardware everything seems to function normaly
tryed to update all drivers i think i just missed something
added dmp's dont know how to read those might have to start learning that

--> packard bell Imedia 1710

 

[koolkat77]

Eset seems to be contributing to your BSOD's. Please remove it for the time being.

Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

If this does not provide stability. Test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

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

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[misticJP]

allready had a friend test my RAM everything seems to be fine
i've tested it aswel on my own and no problems what so ever found ESET is now gone
Hard drive check turns up clean aswel,, well what i can read of it that is

 

[misticJP]

the scannow made some loggs will add them

2013-11-16 22:53:52, Info CBS Starting TrustedInstaller initialization.
2013-11-16 22:53:52, Info CBS Loaded Servicing Stack v6.1.7601.17592 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cbscore.dll
2013-11-16 22:53:54, Info CSI 00000001@2013/11/16:21:53:54.928 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7feef7cf0ad @0x7feefa89849 @0x7feefa534e3 @0xff48e97c @0xff48d799 @0xff48db2f)
2013-11-16 22:53:54, Info CSI 00000002@2013/11/16:21:53:54.952 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7feef7cf0ad @0x7feefad6816 @0x7feefaa2aac @0x7feefa535b9 @0xff48e97c @0xff48d799)
2013-11-16 22:53:54, Info CSI 00000003@2013/11/16:21:53:54.953 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7feef7cf0ad @0x7fef6c48738 @0x7fef6c48866 @0xff48e474 @0xff48d7de @0xff48db2f)
2013-11-16 22:53:54, Info CBS Ending TrustedInstaller initialization.
2013-11-16 22:53:54, Info CBS Starting the TrustedInstaller main loop.
2013-11-16 22:53:54, Info CBS TrustedInstaller service starts successfully.
2013-11-16 22:53:54, Info CBS SQM: Initializing online with Windows opt-in: False
2013-11-16 22:53:54, Info CBS SQM: Cleaning up report files older than 10 days.
2013-11-16 22:53:54, Info CBS SQM: Requesting upload of all unsent reports.
2013-11-16 22:53:54, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2013-11-16 22:53:54, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2013-11-16 22:53:54, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2013-11-16 22:53:54, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2013-11-16 22:53:54, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2013-11-16 22:53:54, Info CBS NonStart: Checking to ensure startup processing was not required.
2013-11-16 22:53:55, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xecfd30
2013-11-16 22:53:55, Info CSI 00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
2013-11-16 22:53:55, Info CSI 00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1f0
2013-11-16 22:53:55, Info CSI 00000007@2013/11/16:21:53:55.023 CSI perf trace:
CSIPERF:TXCOMMIT;26492
2013-11-16 22:53:55, Info CBS NonStart: Success, startup processing not required as expected.
2013-11-16 22:53:55, Info CBS Startup processing thread terminated normally
2013-11-16 22:53:55, Info CSI 00000008 CSI Store 2546128 (0x000000000026d9d0) initialized
2013-11-16 22:53:55, Info CBS Session: 30335766_1481913264 initialized by client WindowsUpdateAgent.
2013-11-16 22:53:55, Info CBS Read out cached package applicability for package: Package_for_KB2840149~31bf3856ad364e35~amd64~~6.1.1.0, ApplicableState: 112, CurrentState:112
2013-11-16 22:53:55, Info CBS Session: 30335766_1482023264 initialized by client WindowsUpdateAgent.
2013-11-16 22:53:55, Info CBS Read out cached package applicability for package: Package_for_KB2656356~31bf3856ad364e35~amd64~~6.1.1.1, ApplicableState: 80, CurrentState:112
2013-11-16 22:53:55, Info CBS Session: 30335766_1482573264 initialized by client WindowsUpdateAgent.
2013-11-16 22:53:55, Info CBS Read out cached package applicability for package: Package_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1, ApplicableState: 80, CurrentState:0
2013-11-16 22:53:55, Info CBS Session: 30335766_1483203264 initialized by client WindowsUpdateAgent.
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-11-16 22:53:55, Info CBS Warning: Unrecognized packageExtended attribute.
2013-11-16 22:53:55, Info CBS Expecting attribute name [HRESULT = 0x800f080d -

 

[misticJP]

2x BSOD now 1ste on was 0xA 2end one was 0xD1,, friend told me to check those

 

[NoelDP]

Please upload the entire CBS.log file so we can take a look - the snippet there doesn't show anything badly wrong.

 

[misticJP]

it wouldnt upload the file the first time
i'll try again after i fix the network card,, since somehow my modem ( ziggo's shit ) started making a high sound and that took out the 2 netwrok cards of the PC's that where running. i dont know how something like that could happen but shamely i will need some time to fix it