BSOD Problem.

AndyBremner · 28 Jul 2010

Hello, I am new here on these forums and I registered solely to try and get this problem fixed.

Today I recieved my new headset - Creative Fatal1ty. All day there has been problems, I keep blue screening and I think it has something to do with the headset. I don't have any sound drivers installed or anything, everything is on default. The problem is it doesn't actually come up with a Blue Screen, the blue screen only happens when I'm in Call of Duty 4 and all the screen does is stop and I get a weird noise coming from the headphones.

Here is some information -

Log Name: Application
Source: Windows Error Reporting
Date: 29/07/2010 01:15:23
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: andydoc-PC
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\072910-16504-01.dmp
C:\Users\andydoc\AppData\Local\Temp\WER-24913-0.sysdata.xml
These files may be available here:
C:\Users\andydoc\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a428b5d
Analysis symbol:
Rechecking for solution: 0
Report Id: 072910-16504-01
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-07-29T00:15:23.000000000Z" />
<EventRecordID>2606</EventRecordID>
<Channel>Application</Channel>
<Computer>andydoc-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>BlueScreen</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Windows\Minidump\072910-16504-01.dmp
C:\Users\andydoc\AppData\Local\Temp\WER-24913-0.sysdata.xml</Data>
<Data>C:\Users\andydoc\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0a428b5d</Data>
<Data>
</Data>
<Data>0</Data>
<Data>072910-16504-01</Data>
<Data>0</Data>
</EventData>
</Event>

reventon · 28 Jul 2010

Hi,

Please follow these instructions: https://www.sevenforums.com/crashes-d...tructions.html

Attach the .zip file to your next post in this thread.

Regards,
Reventon

AndyBremner · 28 Jul 2010

Attachment 88055
Sorry, I'm new here, there it is above my post.

Jonathan_King · 28 Jul 2010

Looks like a hardware problem. See this thread: Stop 0x124 - what it means and what to try

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 6 for Windows7_BSOD_jcgriff2.zip\Windows7_BSOD_jcgriff2\072910-16504-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Wed Jul 28 20:08:21.927 2010 (GMT-4)
System Uptime: 0 days 0:00:07.581
Loading Kernel Symbols
...............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004e58038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

Download Memtest86 and burn it to a CD using ISO Recorder. Boot from it, and leave it running for at least 5 passes.

Memtest86+ - Advanced Memory Diagnostic Tool

ISO Recorder v3

reventon · 28 Jul 2010

Hi,

The dumps blame hardware, however given the system uptimes:

Code:


System Uptime: 0 days 0:00:07.581
System Uptime: 0 days 0:00:07.347
System Uptime: 0 days 0:00:07.363
System Uptime: 0 days 0:00:07.066
System Uptime: 0 days 0:00:06.879
System Uptime: 0 days 0:00:07.051
System Uptime: 0 days 0:00:06.864
System Uptime: 0 days 0:00:06.801

It could also be due to a faulty boot driver aswell.

What happens when you boot into Safe Mode?

Regards,
Reventon

BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 12:08:21.927 2010 (GMT+12)
System Uptime: 0 days 0:00:07.581
BugCheck 124, {0, fffffa8004e58038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 09:37:13.693 2010 (GMT+12)
System Uptime: 0 days 0:00:07.347
BugCheck 124, {0, fffffa8004e59038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 09:14:10.708 2010 (GMT+12)
System Uptime: 0 days 0:00:07.363
BugCheck 124, {0, fffffa8004eb6038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 06:17:28.412 2010 (GMT+12)
System Uptime: 0 days 0:00:07.066
BugCheck 124, {0, fffffa8004ed44b8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 06:12:59.225 2010 (GMT+12)
System Uptime: 0 days 0:00:06.879
BugCheck 124, {0, fffffa8004e24678, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 06:08:50.396 2010 (GMT+12)
System Uptime: 0 days 0:00:07.051
BugCheck 124, {0, fffffa8004e40038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 04:46:00.209 2010 (GMT+12)
System Uptime: 0 days 0:00:06.864
BugCheck 124, {0, fffffa8004ddf748, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 04:32:51.147 2010 (GMT+12)
System Uptime: 0 days 0:00:06.801
BugCheck 124, {0, fffffa8004df0038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

CarlTR6 · 28 Jul 2010

Your most recent dump has a stop error code of 124. This is a hardware/hardware reflated problem.

Please read this article on your bugcheck 124: [2-Int] Stop 0x124 - what it means and what to tryDownload a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Do a CPU stress test as well, using Prime95.

Test your temps with Speedfan.
****

It is a STOP 0x8E error that blames hardware
Please zip up the entire contents of the C:\Windows\Minidump folder and upload/attach it with your next post.

As it blames hardware, please do the following free tests:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current
protection hasn't been compromised: Malware (read the details at the link)

****
http://www.microsoft.com/security_essentials/

***
Check your temperatures as well, during heavy usage, with Speedfan.

Looks like three of us were posting at the same time.

AndyBremner · 28 Jul 2010

Hello CarlTR6 thanks for your response.

As I don't have a disc burner and I'm not aware there's another way to boot into a program without a CD I was unable to do your first solution.

Prime95 - I tested and It came back that there was no errors and no warnings.
Speedfan - I can't test it within the cause of my problem, because the cause of my problem is PC game and I wouldn't have enough time to test it before the crash.
Malware - I ran a free Malware test and a Full computer scan and it came back negative.

Remember this is only since today when I got my new headset, so It's obviously got something to do with that yes? or is it just coincidence that it's happened the day I got something new?

Thanks, and here's my minidump folder zipped up.

Attachment 88058

reventon · 28 Jul 2010

What happens when you go into Safe Mode?

AndyBremner · 28 Jul 2010

When I go into safe mode it's fine, because it's my PC game that triggers it, and you can't start games in safe mode.

AndyBremner · 28 Jul 2010

Bump.