Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
It could be a bad video card or the video card driver. Try to install the newest driver. If still happens, replace the card with something you have from old computers.
Can you help answer these questions from other members on NexusFi?
I don't think you need Malwarebytes if you're using MSE, but I'm not familiar with that software. It may unnecessarily be using resources.
Blue Screen of Death (BSoD) = hardware, BIOS, driver, or heat issue.
I'll also add this is a good example when hardware support provided by a major manufacturer (Lenovo, Dell, or HP) is worth it. It would have been resolved weeks ago. Related to another thread about building your own PCs.
lol, guess we all got offtrack there trying to help.
Yeah keyboard lock up is not normal using trading software. If the keyboard works perfectly fine in all other programs you use than it's the trading software that has a problem. In that case I would contact the company that makes the trading software you are using.
If the keyboard doesn't work in other programs than you can try a keyboard driver update, and if the update doesn't fix it, get a new keyboard.
Away back at the 1st post Tarkus11 suggested this. I tried but did not understand how to use the Event Log. I got a keyboard lockup today at 4:31 and found the following in my Event Log
Event Id 10
Event Source – Microsoft Windows WMI
Locale Id – 1033
I did a google search and found that someone with a Dell Laptop with similar error found the error was caused by some utility sending PC health status back to Dell.
so I used Msconfig to disable a few of my not necessary start up programs
programs removed from StartUP
i. Jing
ii. GoogleToolBarnotification
iii. Secunia – this checks drivers for updates
Left but questioning
i. DelReg – greenpower
ii. Catalyst – AMI video card
iii. Java update notification
iv. Google update
I have tried most of the suggestions, especially to do with Hardware -
I am tracking all changes and monitoring all results
WMI is supposed to give you details on which program caused the error but there is something not registered and the SELECT statement to select the error cause does not work until I fix the problem. I am not a WMI expert, so I am going to look at the StartUp programs as possible the source of the problem
Final Solution
Problem: Blue screen of death (BSOD) and/or system lock up would occur at least 1 time a week.
Environment
. I7 920 computer with MSI X58 Pro motherboard
. OS on 2 hard drives
... OCZ Vertex 3 Solid State Drive
... Western Digital black Caviar drive
. ATI Radeon 4870 video card
. 2 monitors
. 6 GB RAM
. Windows 7 Home Premium
. Transact Futures with Sierra Charts
I was surprised at BSOD because my understanding is that BSOD was fixed in Win7
Since I had BSOD lots in the past with other Windows products I tried a few solutions of my own
o Since USB2 ports can be fussy I swapped out USB mouse and keyboard for PS2 mouse and keyboard
o Swapped put Optical mouse for Roller Ball mouse
Now I got serious
I posted my problem to futures.io (formerly BMT) forum and got lots of different suggestions which I tried all except the dangerous BIOS update Why is BIOS update dangerous, because I have been warned many times that if I do this wrong or my PC goes down in the middle of the update I will end up with a Brick for a Mother board
I tried each fix one at a time and waited a maximum of 2 weeks for another BSOD
Memtest86 – ran this for 23 hours without any errors.
Monitored CPU with CoreTemp for heat, CPU, RAM, equal usage of cores
Checked Win7 Event Log
Monitored CPU activity with Task monitor for strange CPU or RAM events at time of problem
Checked Win7 > accessories > System Tools > System Information
... Checked all hard ware for status and error codes
... Did notice several devices on same IRQ, IRQ status all showed OK
... Checked Software environment for error codes
... Checked Windows Error Reporting
...... The Win7 errors did not align up with my manual BSOD tracking
I moved the schedule for any non-trade related activity (backups) to afternoon time
I Kept a log of day time and what programs I was running when each event happened to look for patterns
Now for some professional help
---------------------------------------
Called my Hard Drive manufacturer (OCZ) tech support and made each of these changes one at a time
... Updated firm ware with OCZ Toolbox
... Did Secure Erase – ... Ran S.M.A.R.T. and had OCZ tech support check results
... Swapped out SSD drives for IDE HDD drive
Called Video card manufacturer (ATI)
o Update Video card drivers with AMD Catalyst now at V12.3 (April 10, 2012)
Called my motherboard manufacturer (MSI) for help and performed each change with a 2 week test time in between
o They assured me that the BSOD and the system lockup were the same issue.
o Updated all Mother board Drivers – done with LiveUpdate
o Disconnect all USB devices including front panel USB ports
o Last thing I did was BIOS update due to MSI recommendation to leave to last – had to update from DOS
The BIOS update seems to have fixed my BSOD but
• Next step would be to return mother board
o Call the vendor (NCIX of Vancouver) who built my computer and ask them what to do about RMA on motherboard
o If NXIX will not help then return to MSI
Summary
------------
• This seems like a long time and a lot of work and it was – but I learned a lot and no damage was done.
• I had 11 BSOD events in October and it has been 2 weeks into November without a BSOD, so I feel pretty confident.
• Big Mike suggested that if I had of bought a system from a vendor like Dell then I could have had them fix it for me. Unless I had of bought a fix at home contract, this most likely would involve sending it back to Dell – may have involved Customs at border
• I could have taken it to a reputable computer shop in town and they could have done all of the updates in one go and returned it to me for testing.
