Blue screen when Steam clients tries to download games

buppus

Honorable
Jun 12, 2013
3
0
10,510
Minidump file: http://www.mediafire.com/download/8s8zaztwuw4kzn6/061113-25443-01.dmp


Event Viewer log:
- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2013-06-12T16:07:56.620005500Z

EventRecordID 120896

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Sig

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 209
BugcheckParameter1 0x331
BugcheckParameter2 0x2
BugcheckParameter3 0x1
BugcheckParameter4 0xfffff8800993676e
SleepInProgress false
PowerButtonTimestamp 0

_______________________________________________________

Description:

I have the whole Steam client including all games sandboxed using Sandboxie because IMO it bogs down the OS if installed normally. It has always worked fine (for the past year or more), until recently when I decided to download a new game through the Steam client (as usual) and halfway through the download it blue screened. After that point, every time I initiate a game download (through Steam client), it seems like as soon as it tries to write to the HDD the system immediately blue screens - every time.

I tried deleting the sandbox content and reinstalling everything, and the Steam client itself has no problem installing and updating, but as soon as I go to the games library and tell it to install one of my games from the Steam servers, the system crashes as soon as it's about to start writing to the disk. I also tried deleting the whole sandbox and starting a new one.

Can someone take a look at the dmp and let me know what's going on?
 

buppus

Honorable
Jun 12, 2013
3
0
10,510
UPDATE: I noticed this last time that it crashed that my wireless adapter (ENCORE ENUWI-2XN42 Wireless N300 Adapter) was not recognized upon reboot, so I went to adapter settings and had windows updated the driver and it seems to be working now - just redownloaded TF2 successfully. Will update further if the problem re-emerges.