Blue Screen/Hardware issue?

Hi Dawnvk,

It appears that the up or down arrow key on your keyboard is stuck. You may try pressing the arrow keys a few times to verify the same and check if it start working again. You may also try connecting the keyboard to an alternate USB port (if using a USB keyboard).

If the issue persists, try using an alternate keyboard as the old keyboard might have malfunctioned. We will need a functional keyboard for diagnosing blue-screen issue.

Also, I would suggest you to run the diagnostics on the system to check the hardware functionality. You may follow the steps below :

• Power on the computer
• Press F12 button when you see Dell logo on the screen
• Highlight the Diagnostics option and press Enter
• Note down error messages if any and reply with the outcome

Please reply with the findings. Will take it further from there.

I don't have another USB KB to test, but I did plug the one I have into a different USB Port (it was plugged into a USB expansion port so I plugged it directly into a USB port in the back of the CPU). I rebooted, hit F12, ran the diagnostics, everything came back as Pass, though I didn't see a KB test specifically run. Then I rebooted and hit F2 to set the CD as the boot preference in case it crashes again and I need to use a boot CD or something - this time it worked fine. I think moving the KB fixed the jumping around issue. I still don't know what caused the blue screen last week, but maybe it was just a fluke. I've been running for over a week now with no issues, so I guess I'll just back up nightly and keep my fingers crossed that it won't happen again - unless you have a suggestion for anything else I might test to see what caused it.

Thanks,

Dawnvk

If you get another blue screen, please record the error type, 0x??????????, and any other pertinent info. If the machine reboots after a few seconds and you can't get the code, go to the BIOS, F2, and find a setting to stop rebooting after an error.

May we ask the Dimension model?

Hi Dawnvk,

As the diagnostics passed successfully, the hardware seems to be working fine. You may continue to use the system normally. However, if you wish to diagnose the blue-screen error message, you may follow the steps below to capture and share the relevant details:

1. Crash Dump data:
- Click 'Computer'
- Navigate to C:\Windows\Minidump and tap
- Copy all the 'Minidump' folders and paste them to your desktop screen
- Please send these folders to me (I am sending my email address through a private message)

2. MSINFO32
- On the 'Start menu' (Windows), type 'MSINFO32' in the 'Search text box'
- In the 'System Information dialog box', on the File menu, click 'Save'
- In the 'Save As dialog box', make sure that the file type is 'System Information File (*.NFO)'
- Enter a name for the file > Click 'Save' and share the file with me

3. Event Viewer
- open the Event Viewer by going to start->run->eventvwr

- Click 'Save Log File As' (*.evtx)

4. Windows Update History logs:
- On the 'Start menu' (Windows), type 'windowsupdate.log' (without quotations) in the 'Search text box' > click OK > Save the file in text format (.txt)
- Share the log files 

5. DxDiag file:
- Tap key combination
- Type 'DxDiag' and tap 'Enter'
- In the 'DxDiag window', click 'Save All Information'
- Save this file to your 'Windows desktop' and name it 'dxdiag' and share it with me.

I am adding you as a friend. Please accept my friend request by clicking on my name highlighted in blue and then click on “Friends” tab at the top and then click on “Request to Review” and finally click on “Accept” button. I am sending you a private message with my 'Email address'. Click on “Inbox” to find my Email. Please attach the mini dump folder and email it to me directly. Do reply with the results. I would be glad to assist.

Hi Dawnvk,

Unfortunately we have not received feedback from you on this topic. If you need continued support, please write back. Other community members who need assistance please start your own topic in a new thread.

Sorry I have been slow to reply... my son graduated and it's been a bit crazy here. This next week I plan to try to get to some of this. Thank you for understanding.

Dawn

Thanks for the nice clear outline of the steps, I have completed them and have emailed the files to you.

Dawn

Hi Dawn,

Please find below the crash dump analysis.
BugCheck 50, {ffffffffffffffd0, 1, fffff800032d68c3, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+73 )
Followup: MachineOwner
---------
0: kd> !analyze -v
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.

The crash dumps do not point at any specific driver that may be responsible for the bluescreens. It produces the error message: PAGE_FAULT_IN_NONPAGED_AREA (50) 

Possible Causes:

• Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
• Another common cause is the installation of a faulty system service.
• Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolution:

• Run the System File Checker Tool to scan the integrity of protected system files from Here
• To isolate the issue, try removing AVG using the AVG removal tool from Here
• Install Microsoft Security Essentials from Here
• You may choose to install AVG later, if it does not impact the system stability.
• Run Check Disk from a Command Line to Check for and fix Disk Error. You may refer to article Here.
• Perform Windows updates and recheck results. 

Let me know the findings. I will be glad to assist you.