Windows 10: i keep having this error, I've tried a couple different tests and looked things up but no...

Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 5/25/2024 2:19:32 PM Event ID: 41 Task Category: 63 Level: Critical Keywords: 70368744177664,2 User: SYSTEM Computer: DESKTOP-H9G6GPB Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 41 9 1 63 0 0x8000400000000002 57159 System DESKTOP-H9G6GPB 275 0x19 0x1

:)

 

RPi2 from Windows cross compilation Error "The test for linking against libxcb failed!"

Error in Cross Compilation, I am using Qt5.0, Windows10, Raspberry Pi 2.
I was following this tutorial and the process failed at step 16 and tried with its suggestion but cannot find a solution.

Error prompted after step 16 is:

Running configuration tests...
The test for linking against libxcb failed!
Use of pkg-config is not enabled, maybe you want to pass -force-pkg-config?
You might need to install dependency packages for libxcb.
See src/plugins/platforms/xcb/README.

and when I printed log in file as tutorial suggested, there are some errors mentioned like:

• cc1plus.exe: error: unrecognized command line option '-fuse-ld=gold'
  
• error "Symbolic function binding on this architecture may be broken, disabling it (see QTBUG-36129)."
  
• etc.
  

I tried but still find no solution.

 

hd6950 to hd 6970

ok
i ve tried everything:with atiflash from dos,winflash.step by step with bios powercolor hd 6970 from the database.
nothing,doesn´t work.any suggestion????

 

 HDD TEST

This last BSOD is quite different to the one I analysed before. It is not so clear from the analysis what is causing this system service exception. I would suggest that a check of the hard disk might be worth running. If this looks OK we can move on to RAM testing.




Diagnostics Test [/i] HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.