One off Bluescreen in Win7 - preventative measures?

Tuffie

Tuffie

Active Member
I had a Bluescreen a moment ago, I'm not sure what this was caused by, I had a whole bunch of stuff open at the time 15+ chrome tabs, skype in a call, spotify, LoL (game), Vuze with open downloads. If you were wondering why so many I have two monitors.

The Bluescreen only showed for a few moments but had something about memory dump and a progress indicator which was displayed as an integer that seemed to be counting up in 5's to 100 when the Bluescreen went away and the machine rebooted to a windows boot screen something about 'configuring windows features' similar to what you'll see after installing updates as you shut down, after which it restarted and showed the same 'configuring windows features' for a few moments and it started up per usual.

Heres the report I was presented with after all of that finished:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\061113-21262-01.dmp
C:\Users\TANG\AppData\Local\Temp\WER-35303-0.sysdata.xml

<PRIVACY STATEMENT TEXT REMOVED TO BREVITY
Click to expand...

I tried looking at both of those files but the latter 'WER-35303-0.sysdata.xml' didn't seem to be in the location specified and I have found the .dmp but am not familliar with working with these files. Does anyone know where I start troubleshooting this?

I'm coming into exam period with uni and throughout this time I particularly need the machine to be reliable.
 
spirit said:
Can you download BlueScreen View, open it, and then save as a text file and copy the contents of the file into your next reply please?

You can download BlueScreen View here http://www.nirsoft.net/utils/blue_screen_view.html
Click to expand...

Sure!

There were two items shown I beleive the first one was the one I discuss above:

==================================================
Dump File : 061113-21262-01.dmp
Crash Time : 11/06/2013 2:41:27 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+36e5
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bd0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061113-21262-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 293,344
Dump File Time : 11/06/2013 2:42:35 PM
==================================================
Click to expand...

==================================================
Dump File : 060513-17986-01.dmp
Crash Time : 5/06/2013 7:28:12 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000406f8
Parameter 4 : fffff800`02c82d30
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060513-17986-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 293,272
Dump File Time : 5/06/2013 7:29:33 PM
==================================================
Click to expand...
 
Zip up the minidump file and attach it to your next post.

C:\Windows\Minidump\061113-21262-01.dmp
 
For some reason my debugger isn't working correctly with your dump file. But it seems its a driver issue, it just won't tell me what driver. Let me know if it does it again.
 
Yeah I had the same issue John did with my debugger, but it is definitely a driver issue. Since you had so many things going on it's hard to determine what the issue was, but I'd safely assume it was either a bad graphics driver or a webcam driver issue (you said you were doing a call on Skype).
 
You must log in or register to reply here.
Back
Top