You're stuck in a frustrating situation with Windows 10 and a tense agreement.

F5F Stay Refreshed Software Operating Systems You're stuck in a frustrating situation with Windows 10 and a tense agreement.

Pages (3): 1 2 3 Next

Cupcake_Rose
Posting Freak

844

07-29-2016, 01:08 PM

OS reinstalled because it kept crashing. BSOD appeared at the end of installation. Start menu stopped working. Another different BSOD happened. Any suggestions? What information should I provide?

Cupcake_Rose

07-29-2016, 01:08 PM #1

OS reinstalled because it kept crashing. BSOD appeared at the end of installation. Start menu stopped working. Another different BSOD happened. Any suggestions? What information should I provide?

Waran23
Junior Member

08-03-2016, 01:46 PM

Verify your system specs. No issues reported on four distinct machines using Windows 10.

Waran23

08-03-2016, 01:46 PM #2

Verify your system specs. No issues reported on four distinct machines using Windows 10.

juri1990
Senior Member

441

08-04-2016, 02:10 PM

Is it an old computer? The BSOD might not be linked to hardware issues. Check the error code it displays.

juri1990

08-04-2016, 02:10 PM #3

Is it an old computer? The BSOD might not be linked to hardware issues. Check the error code it displays.

W_O_L_F_R_A_M
Member

125

08-04-2016, 09:43 PM

Everything seems to be in working order. The motherboard has a faulty RAM slot, so I need to return it for replacement. All components like CPU, storage, GPU, and power supply are from an older build. What might be causing issues is the mismatch in RAM type or compatibility between the new and old parts.

W_O_L_F_R_A_M

08-04-2016, 09:43 PM #4

sherkan2712
Member

193

08-06-2016, 06:27 PM

The dead RAM slot looks questionable. Which components are involved and how are they looking?

sherkan2712

08-06-2016, 06:27 PM #5

The dead RAM slot looks questionable. Which components are involved and how are they looking?

Lanjs
Junior Member

08-12-2016, 08:28 PM

Initial result was an irql_not_less_or_equal and the most recent one triggered a KMODE_EXCEPTION_NOT_HANDLED error.

Lanjs

08-12-2016, 08:28 PM #6

Initial result was an irql_not_less_or_equal and the most recent one triggered a KMODE_EXCEPTION_NOT_HANDLED error.

Kuji
Member

133

08-12-2016, 09:44 PM

Here’s the detailed list from the signature:

- Log building process
- Signature inclusion
- Detailed steps involved
- Final output format

Kuji

08-12-2016, 09:44 PM #7

Here’s the detailed list from the signature:

- Log building process
- Signature inclusion
- Detailed steps involved
- Final output format

Luxray68
Junior Member

08-13-2016, 04:01 AM

On the start menu, you can run a PowerShell command to resolve issues.

Luxray68

08-13-2016, 04:01 AM #8

On the start menu, you can run a PowerShell command to resolve issues.

iwilldie2
Junior Member

08-13-2016, 05:27 AM

The issue appears to be related to hardware or drivers.

iwilldie2

08-13-2016, 05:27 AM #9

The issue appears to be related to hardware or drivers.

3Edge
Senior Member

718

09-02-2016, 08:07 AM

#10

irql typically indicates a driver-related issue leading to a crash. Ensure your system is properly formatted and hardware is verified. Common causes include dying RAM, loose connections, or network driver failures. If using Wi-Fi, consider switching to a wired connection.

3Edge

09-02-2016, 08:07 AM #10

Pages (3): 1 2 3 Next